Skip to main content

Assigning roles

Roles determine which content Dynamic Content users may access, and the actions they are allowed to perform, providing you with a flexible approach for granting user permissions.

For each user in an organization, you can assign:

  • an organization role, to determine which users are admins and non-admins
  • hub and repository roles to control the actions users can perform for those resources
info

Roles are replacing personas for granting Dynamic Content user permissions. If you currently use personas, please contact your Customer Success Manager or Amplience Support about migrating to roles.

For more information about the differences between roles and personas, see User permissions.

Assigning organization roles
Link copied!

We provide two organization roles, member and admin, allowing non-admin and admin users within an organization. By default, members of an organization are assigned the member role.

Promoting to admin role
Link copied!

You can promote a user with the member role to have the admin role. To do this, select or hover over an active member in the member list. The selected member is highlighted in pale blue and the ellipsis (...) is displayed. Click the ellipsis to display the contextual menu, as shown below.

Promote to admin menu option

A confirmation dialog is displayed for you to confirm promoting to the admin role.

Promote to admin confirmation dialog

A notification is displayed, confirming the member has been promoted to admin. You can see the member's role is updated to admin in the list.

Member promoted to admin

tip

You can also promote a member to have the admin role, by changing the Organization role on the Edit member pane.

Demoting to member role
Link copied!

You can demote a user with the admin role back to being a non-admin member. To do this, select or hover over an active member in the member list. The selected member is highlighted in pale blue and the ellipsis (...) is displayed. Click the ellipsis to display the contextual menu, as shown below.

Demote to member menu option

A confirmation dialog is displayed for you to confirm demoting to the member role.

Demote from admin confirmation dialog

A notification is displayed, confirming the role has changed. You can see the member's role has changed to member in the list.

Member demoted from admin

tip

You can also demote a member from having the admin role, by changing the Organization role on the Edit member pane.

Assigning hub roles
Link copied!

For each organization member you can control the actions they can perform for Dynamic Content hubs by assigning hub roles. You can assign roles on a per hub basis.

note

If you have the Dynamic Content Assets tab provisioned, it may be configured so that users access to asset stores is determined by hub permissions. In this case, assigning hub roles of author (or above) allows users to view and upload assets to all of the asset stores to which the Dynamic Content hub has access. For more information, see Assets tab provisioning options.

To assign a hub role to a member, open the Edit member pane for the member, by choosing 'Edit member' from either the:

In the Edit member pane, navigate to the hub for which you want to assign the user permissions. In the example below the user has access to one hub.

The Edit member pane

note

Looking in Dynamic Content, you can see the user has access to just one hub.

Hub access for one hub in DC

From the Edit member pane, grant access to a hub by using the switch control. This automatically assigns the hub member role for the user and expands the hub to show its repositories.

Assigning a hub member role

To assign a different role for the user, choose from the dropdown list. For this example, we've assigned the author role. See the hub roles descriptions.

Assigning hub author role

When you've assigned the required hub roles and saved your changes, a notification message confirms the saved changes.

Looking in Dynamic Content, you can see the user now has permission to use two hubs. The hub they could already access and the hub for which they've been assigned the author role. Notice how in this example, the Development tab isn't shown in Dynamic Content. This is because we assigned the hub author role which doesn't allow any developer actions.

Hub access for two hubs in DC

Assigning repository roles
Link copied!

For each organization member you can control the actions they can perform on repositories by assigning repository roles. You can assign roles on a per repository basis.

To assign a repository role to a member, first open the Edit member pane, by choosing 'Edit member' from either the:

In the Edit Member pane, navigate to the repository for which you want to assign a role. You can navigate directly to repositories even if the user doesn't yet have access to the parent hub.

The Edit member pane with repositories

tip

Use the search and the filter to help find the repository you want.

In this example, we're following on from assigning a user the hub author role. Although the hub role is assigned, the user doesn't yet have permission to access any of its repositories. This means in Dynamic Content, the user will not see any content repositories for this organization.

From the Edit member pane, grant access to a repository by using the switch control. This automatically assigns the repository member role for the user. If the user doesn't already have an assigned role on the parent hub, the hub member role is automatically granted.

To grant the user permissions for a repository, choose a role from the dropdown list.

Assigning repository and hub roles

tip

Use the enable all option, to assign the member role for all repositories in a hub. If different roles have already been set on some repositories, they will remain the same. Using the disable all option, will disable all roles set for the hub.

When you've assigned the required roles and saved your changes, a notification message confirms the saved changes. Looking in Dynamic Content, you can see that the user now has access to the repositories for which you assigned roles.

Assigning repository and hub roles

Finding hubs and repositories
Link copied!

When assigning roles you can use the search and filters in the Edit member pane, to help you find specific hubs and repositories.

Searching for hubs and repositories
Link copied!

You can quickly find hubs and repositories in the Edit member pane if you know the all, or part of the name, using the search. The search finds all instances of your entered text, anywhere in the hub and repository names.

If the pane is filtered to show hubs or repositories only, the search is performed on the filtered list.

Filtering hubs and repositories
Link copied!

Use the view filter to show either hubs or repositories in the Edit member pane.

The Edit member pane shows all hubs and their repositories for an organization, by default. You can filter the pane to show either hubs or repositories. When filtered, the list shows hubs or repositories alphabetically in the order A-Z.

Finding assigned roles
Link copied!

Using the assigned roles pane you can see which roles have been assigned for a selected member. The assigned roles pane lists only the hubs and repositories for which a member has been assigned roles.

To find all the assigned roles for a member, click on the member in the member list. The assigned roles pane is displayed.

Finding assigned roles

From the pane, you can search to find the specific hub or role against which a role is set. In addition, you can filter the list, which also refines the search.