The Role Object
string
Unique identifier
string
Role name (e.g., “editor”, “developer”)
string
Role description
object
Permission settings for each resource type
string
Creation timestamp (ISO 8601 format)
string
Last update timestamp (ISO 8601 format)
Permission Categories
Roles control access to 11 resource types, each with specific actions:Administrative Resources
Development Resources
Content Resources
Content and content types have a separate
publish permission, allowing editorial workflows where users can create and update drafts but not publish.Inherited Permissions
Certain organizational features inherit permissions from related core resources:- Collections: Creating, updating, and deleting require
content.create,content.update, andcontent.delete; listing and getting have no role requirement - Folders: Inherit from the resources they organize
- Saved Searches: Creating, updating, deleting, favoriting, and executing require an organization admin role
- Tags: Creating, updating, and deleting require
content.create,content.update, andcontent.delete; listing and getting have no role requirement - Preview Links: Inherit from source resource permissions
Example Role Object
Permission Computation
When checking a user’s permissions:- All roles assigned to the user are retrieved
- Permissions from all roles are merged using OR logic
- If any role grants a permission, the user has that permission