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.
We've introduced roles for you to grant Dynamic Content user permissions. Roles provide you with significant benefits and a more flexible approach for granting permissions than our original persona permissions.
Why do we have roles and personas?Link copied!
Personas are the original method for granting Dynamic Content user permissions, and they have certain limitations. Roles are our next generation method for setting user permissions and have significant advantages over personas. Using roles, administrators can grant permissions themselves and set permissions at a more granular level than personas.
Roles are replacing personas as the method for granting Dynamic Content user permissions. If you are currently using personas, please contact your Customer Success Manager or Amplience Support about migrating to roles.
The summaries below help you to compare the capabilities of roles and personas.
Roles summaryLink copied!
Roles allow you to grant 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.
Personas summaryLink copied!
With personas, if a user has a persona on a hub they also have a persona on all of that hub's child repositories.
The following set of personas are provided for controlling user access to Dynamic content hubs and repositories:
- Customer Admin - can do all actions for hubs or repositories
- Developer - can do actions that enable other users to create and manage content on a hub or repository
- Planner - can manage editions and events to schedule content on the appropriate hubs, and publish content
- Content producer - can create, archive and delete content in the appropriate hubs and repositories, but not publish content
- Read only - can view events, editions and content but not manage or publish anything
Read more about personas.
How personas map to rolesLink copied!
When you migrate from using personas to roles, existing persona permissions are mapped to roles as shown below:
| Persona | Hub and repository role |
|---|---|
| Customer admin | Admin |
| Developer | Developer |
| Planner | Publisher |
| Content producer | Author |
| Read only | Member |
