Share content collections
When you share content collections, four user roles determine access to the collections:
- Reader
- Developer
- Contributor
- Manager
The following table shows these roles and their associated permissions.
| Permissions | Reader | Developer | Contributor | Manager |
|---|---|---|---|---|
| Read | Yes | Yes | Yes | Yes |
| Update metadata | No | No | Yes | Yes |
| Add or remove items | No | No | Yes | Yes |
| Upload cover image | No | No | Yes | Yes |
| Delete | No | No | No | Yes |
| Manage roles | No | No | No | Yes |
Add users to a content collection
To add users to a content collection:
On the content collection detail page, click User access.
Click Add users.
In the User access dialog box, assign a role to each user.
Select the role required for each user.
Click Save.
API key permissions
It is the user role that determines permissions for the API keys. These keys authorize access to content collections through the Preview and Delivery APIs.
Only users assigned a Developer or Manager role can create API keys from a content collection page.
The following table shows the API keys permissions for each user role.
| Permissions | Reader | Developer | Contributor | Manager |
|---|---|---|---|---|
| Create token | No | No | Yes | Yes |
| Revoke own token | No | No | Yes | Yes |
| Delete own token | No | No | Yes | Yes |
| Revoke all tokens | No | No | No | Yes |
| Delete all tokens | No | No | No | Yes |
Can we improve this article ? Provide feedback