Permissions
To perform a given task in Dynamic Content, for example creating and editing content, or creating and scheduling editions, a user must have the appropriate permissions, as well as the required access to the organizations, hubs and repositories in which these tasks are performed.
You use roles to set Dynamic Content user permissions.
Dynamic Content permissions also provide the appropriate permissions for users with access to Amplience Studios.
Roles summaryLink copied!
Roles allow you to set user permissions on a per hub, per repository basis, with the ability to restrict access where necessary. For example, if a hub contains several repositories, you can assign a user access to just one of those repositories. In addition, users can have different roles on different repositories within the same hub. For example, a user could be an admin on one repository and a developer on another.
The following set of roles are provided for controlling user access to hubs and repositories:
- Admin - can do all actions for an organization, hub or repository
- Developer - can do actions that enable other users to create and manage content on a hub or repository
- Publisher - can manage editions and events to schedule content on the appropriate hubs, and publish content
- Author - can create, archive and delete content in the appropriate hubs and repositories, but not publish content
- Member - can view events, editions and content but not manage or publish anything
Read more about roles.