Community Role

A user's community role indicates the level of permission to access your community - member experience-only or member experience and Studio. Studio-level roles have different levels of access within the Studio.

Users can have one role in one community and a different role in another community within the same organization. For example, a user can be a Member of one community and a Brand Super Admin in another community within the same organization.

For more granular control of your community, check out this article on how to create custom roles!

Note: If your community is still using Classic roles, only Community Managers and Administrators will be able to sign in to Studio. Once your community has upgraded to Advanced Permissions, check out this article for a comparison of Classic Roles and Advanced Permissions.

Member

Not able to access Studio, only allowed to access the member experience (mobile app or web experience). Experience status indicates if the Member can access the full feed or must still complete registration. The error message "The user does not have a sufficient role to access this application" will appear if a member tries to access Studio.

Content Creator

Content Creators are able to create and edit content but are restricted from publishing content. This use is restricted to specific topics and audiences. They will only have access to analytics on individual campaigns via the Calendar page.

Users assigned this role are able to see pages under Campaigns and Calendar in Studio for a specific community. And the campaigns listed under Campaigns and Calendar will be limited to those that are assigned to one of the topics or audiences that the user has access to.

Check out this video on how to use Studio as a Content Creator!

Content Publisher

Content Publishers can create and publish content that is targeted to their assigned topics and audiences. See more details in our guide to leveraging Content Creators and Content Publishers.

Users assigned this role are able to see pages under Campaigns, Calendar, and Insights. The campaigns listed under Campaigns and Calendar will be limited to those that are assigned to one of the topics or audiences that the user has access to. And the selection of reports under Insights will be limited to their own campaigns. The Content Publisher scoped-content reports include:

• Landing MV
• Content Overview
• Article Performance
• Video Performance
• Delivery Details
• Campaign Performance
• Post Performance
• Poll Performance

This role does have some limitations, such as the inability to set campaigns as critical priority. When a function is not available, it will be excluded from the options.

Check out this video on how to use Studio as a Content Publisher!

Community Admin

Community Admins can manage content, users, and some configurations for their community. 

Able to see all sections (Campaigns, Calendar, Insights, People, Library, and some Configure) of Studio for a specific community. They are able to view all reports for a community within Insights, but within Campaigns and Calendar, they are restricted by their assigned topics and audiences. Can create email aliases and topics, but cannot assign them to other users or to themselves.

Check out this video on how to use Studio as a Community Admin!

Brand Super Admin

Brand Super Admin is the system role with the highest level of access. Brand Super Admins can communicate with all members of the community (no topic or audience restrictions) and change all community settings. Brand Super Admins are able to see every part of every section (Campaigns, Calendar, Insights, People, Library, and Configure) of Studio for their community. Brand Super Admins are able to see all campaigns, regardless of topic/audience assignation. Brand Super Admins are the only system role that can edit the role of other users.

Note: It may be appropriate to limit assigning Brand Super Admin to a small handful of users per community.

Check out this video on how to use Studio as a Brand Super Admin!

Roles Permission Table

	Action	Brand Super Admin	Community Admin	Content Publisher	Content  Creator	Member
CAMPAIGNS	Create, edit, and archive campaigns from Studio
	Publish campaigns
	Schedule campaign publish date and time
	Set campaign duration
	Configure campaign features: Commentable Translatable Shareable Featured Resources Acknowledge
	Assign another Studio user as the author
	Target audiences and topics
	Assign initiatives
	Set campaign as Critical in Deliver
	Send email, push, and/or Assistant notifications)
	Moderate Comments
	Approve or reject user-generated content
	Hide drafted campaigns
	Create temporary audiences
PEOPLE	Create, edit, and export audiences
	Manage members - edit details, deactivate, forget
	Manage roles and restrictions
INSIGHTS	Review campaign metrics and other community data via Insights
	Review campaign metrics via Calendar
LIBRARY (template, image, font, and block)	Can use templates, images, fonts, and blocks from all libraries
	Create, edit, and archive campaign templates
	Manage campaign template permissions
	Customize and manage image library
	Customize and manage font library
	Create and manage custom blocks
CONFIGURE	Administration:  Account Activity Feed Advocacy Capabilities Roles
	Content: Email Aliases Feeds Initiatives Topics User Exports User Imports
	Connect: Workflows Workflow Templates
	Experience: Branding Custom Feed Shortcuts Microapps
	Security: Legal Session Options and User Access
MEMBER EXPERIENCE	Access Member Experience
	Direct publishing from web or mobile
	Save as Draft
	Set as Shareable
	Configure post: Commentable Translatable Archive

Restrictions 

Topics and Audiences

For most roles, access to campaigns is restricted based on assigned topics and audiences. The only exception to these restrictions are Brand Super Admins and custom roles with "No Restrictions" enabled. 

Community Admins, Content Publishers, Content Creators, and most custom roles:

• Always see their own untargeted drafts.
• Only see campaigns created by others that include at least one assigned topic or audience.
• Only edit or archive campaigns that are exclusively published to their assigned topics or audiences. For example, this means that most roles cannot edit items that are targeted to both their topic and an unassigned topic.
• When configuring Deliver settings, only target users within the assigned audience.
• There are no restrictions regarding who creates the campaigns. For example, if a Community Admin publishes to a topic that a Content Creator is assigned, then the Content Creator could modify the campaign.

People

The only roles with access to the People page are Community Admins, Brand Super Admins, and applicable custom roles. Brand Super Admins and custom roles with "No Restrictions" are able to see all the users for their community on the People page. And Community Admins are restricted to viewing and editing users who are a part of their assigned audiences. However, only Brand Super Admins can assign roles, topics, and audiences to users. 

Templates, Email Aliases, and Author Aliases

Only Brand Super Admins and applicable custom roles are able to select from and use any template, email alias, and author alias. All other users must be assigned email aliases and author aliases via their user profile in order to use them. Users can use any public template, but custom templates must be assigned if the template permissions are set to "Specific Users".

Insights

Only Community Admins, Brand Super Admins, and applicable custom roles will have access to all reports within Insights, with no restrictions, across all communities. Users with a restricted publisher role (i.e. Content Publishers and relevant custom roles) will have access to a subset of reports containing data that will be scoped to the content they've created and published and is restricted to the topics and audiences they are assigned.

Workflows

Only Community Admins, Brand Super Admins, and applicable custom roles will have access to workflows. Workflows, like campaigns, are visible depending on each individual user’s access to audiences.

A restricted user should only be able to view/manage a workflow if they:

• Are assigned a role that has access to workflows.
• Have access to one or more of the audiences the workflow is targeted to.