Roles
Roles are used for setting user permissions for Dynamic Content users. We provide a standard set of roles that can be assigned for hubs and repositories.
Dynamic Content permissions also provide the appropriate permissions for users with access to Amplience Studios.
During initial set up an organization administrator is assigned, who can use roles to set permissions.
Organization administratorLink copied!
Organizations have at least one organization admin user. This user can:
- Invite users to an organization
- Manage repositories
- Manage user permissions for hubs and repositories in that organization
- Assign other users to be organization admins
To ensure users have only the permissions they require, and to help delegate account management tasks, organization admins can assign users the hub admin role.
Hub and repository rolesLink copied!
Hub and repository roles are packaged sets of permissions that control user access levels for hubs and repositories. The roles are: member, author, publisher, developer and admin.
MemberLink copied!
Assigning a user the role of member on hubs and repositories allows them to do the following in Dynamic Content:
| Hub member | Repository member |
|---|---|
| View events and editions | View content items |
AuthorLink copied!
Assigning a user the role of author on hubs and repositories allows them to create, edit, and delete content in Dynamic Content. Note that authors do not have permission to publish content.
| Hub author | Repository author |
|---|---|
| Create snapshots | Create, edit and archive content items |
| Add, update and delete snapshots from editions | Manage folders |
PublisherLink copied!
Assigning a user the role of publisher on hubs or repositories allows them to do Dynamic Content publishing tasks.
| Hub publisher | Repository publisher |
|---|---|
| Publish content from the hub for which this role is assigned | Publish content from the repository for which this role is assigned |
| Create, edit and delete events and editions | |
| Perform hub author actions | Perform repository author actions |
DeveloperLink copied!
Assigning a user the role of developer on hubs or repositories allows them access to the Dynamic Content Developer tab to model content and define your environment.
| Hub developer | Repository developer |
|---|---|
| Manage webhooks | Create edit and archive slots |
| Manage content types and content type schemas | Enable content types on the repository for which this role is assigned |
| View integrations | |
| View, create and edit Salesforce Commerce Cloud (SFCC) integrations | |
| Register and manage extensions | |
| Update hub and repository settings | |
| Manage search indexes (on hubs that have Dynamic Content search enabled) | |
| Perform hub author and publisher actions | Perform repository author and publisher actions |
AdminLink copied!
A user with the admin role on a hub or repository, has permission to perform actions allowed by the developer, publisher, author and member roles.
Assigning a user the admin role on hubs and repositories allows them to perform the actions below.
| Hub admin | Repository admin |
|---|---|
| Manage repositories for *relevant hubs | |
| Manage user permissions for relevant hubs | |
| Edit workflow states for relevant hubs | |
| Perform hub developer, publisher, author actions | Perform repository developer, publisher and author actions |
* Relevant hubs are the hubs for which a user has been assigned the hub admin role.
Roles and Content StudioLink copied!
Content Studio uses roles and permissions to govern and safeguard who within an organization is allowed to adjust brand parameters, use credits, and perform other actions in the system. If you are also using Dynamic Content for content management, your role in Dynamic Content will determine what actions you can perform in Content Studio.
MemberLink copied!
Members have read-only access and cannot use credits to generate content or adjust any brand parameters or examples.
AuthorLink copied!
In Content Studio, users with the hub author role can perform the same actions as members and use credits to:
- Generate content
- Update sessions for which they are the author and have hub author permissions
- Delete sessions for which they are the author and have hub author permissions
DeveloperLink copied!
In Content Studio, users with the hub developer role can perform the same actions as authors and:
- Create/Read/Update/Delete commerce connections
AdminLink copied!
In Content Studio, users with the hub admin role can perform the same actions as developers and:
- Create/Read/Update/Delete brand voices
- Create/Read/Update/Delete audiences
- Create/Read/Update/Delete tones
- Create/Read/Update/Delete examples
- Create/Read/Update/Delete example folders
- Create/Read/Update/Delete models
- Update any sessions on the hub
- Delete any sessions on the hub