Site access
Choose which of your app's user roles can use each collection, your files and each app.
Site access decides what your app's users can reach, by role. You grant a role access to a Data Vault collection, to your files, or to an app. It doesn't affect your team or your M2M tokens.
What you can grant
| Resource | Grant covers | Grants |
|---|---|---|
| Data Vault | One collection | read, write (includes read), delete (includes write) |
| Files | Every file in the workspace | read, write |
| Apps | One app | launch |
Roles come from App authentication: viewer, user, admin and any you create. The built-in admin role works like any other role: it reaches only what it's granted, and you can remove its grants.
New collections start open only to admin, and new workspaces give admin read and write on Files. An app that every role, admin included, can launch is open to the whole workspace; remove a role and it becomes restricted. If you remove admin from something, admins lose access to it.
Set grants
Open Site access
In the Client Portal, go to Administer → Access and pick the workspace.
Pick a role
On the right, choose the role you're granting to.
Add access
On the left, choose Data Vault, Files or Apps, then the collection or app, and the grant. Click Add, then save.
You can also grant collection access from Data Vault: open the collection and click Access. It's the same setting. You need the Admin or Owner role in the workspace.
Next steps
- Data Vault — collection access.
- Access API — manage grants from code.