Note: This article only applies to Brand Super Admins or applicable custom roles. For more details on Studio access, please refer to the Defining Roles and Restrictions article.
Brand Super Admins can grant access to Studio by modifying the role assigned to the users in their community.
Once your community updates to the new Studio and updates from Classic Roles to Advanced Permissions, you will be able to utilize a set of standard system roles and have the ability to create custom roles. We believe that the majority of your users should fit within a system role, but for exceptions, you can always create a custom role.
When upgrading from Classic Roles to Advanced Permissions, the roles do not correspond directly to each other because the two systems organize access in different ways. Below, we have outlined the closest comparison as a starting point for considering whether your current users can be mapped to one of the Advanced Permission system roles. Again, if the system roles do not fit your needs then you can explore custom roles as well.
This article focuses on the comparison between Classic Studio roles and Advanced Permissions - for details on how the Advanced Permission roles work, please refer to Defining Roles and Restrictions.
|Advanced Permission Role||Closest Comparison
|Brand Super Admin||
Brand Super Admin should be assigned to individuals who need unrestricted access to all topics, all audiences, and all parts of Studio, including the security settings. Brand Super Admin is the only system role that can manage the roles of other people in your community. It may be appropriate to limit assigning Brand Super Admin to a small handful of users (say 2-3).
Brand Super Admin is community-specific and must be assigned (or demoted) within each community. This stands in contrast to the Administrator in Classic Studio, which had access to multiple communities.
|Community Admin||N/A - no comparable role in Classic Studio||
Community Admin is for individuals who help manage the community at a configuration and report level, but should only be able to publish to specific topics/audiences and manage members within their assigned audience.
Compared to Classic Studio, a Community Admin has more access than a Topic Manager (access to People, Configure), but less access than a Program Manager (restricted by assigned topics/audiences, cannot manage roles for other users, cannot configure branding).
|Content Publisher||Topic Manager
(Channel Contributor) or Publisher
Content Publisher is a great role for content managers who are purely focused on creating and publishing content, not managing the community.
Note that Topic Managers in Classic Studio did not have the ability to create polls and had no access to the Measure pages. Content Publishers can use poll blocks and access reports under Insights which are scoped to content that they created.
Please also note that in the new Studio Content Publishers can choose any other Studio user as an Author.
|Content Creator||N/A - no comparable role in Classic Studio||
Content Creator is a great role for those who draft communications but should not be publishing their own content. Other roles would publish their drafts. Think of a communication specialist, editor, or intern.
There was no role in Classic Studio that could create content without then being able to publish. However, you may have Topic Managers that are better suited to the Content Creator role than Content Publisher.
|N/A - no comparable role in Advanced Permissions||Analyst||There is no system role that is comparable to the Classic Role for Analyst. If you would like a role with access to Insights and no other areas of Studio, you can create a Custom Role.|
We encourage reviewing the above with your Customer Success Manager - we want to work with you to make sure the Advanced Permission roles that are assigned to your users fit your needs, whether that means the use of a system role or creating a custom role.