Manage roles

|

View as Markdown

Use roles to control what users can see and do in the web interface. Assign default roles, or create custom roles.



Roles and permissions

A role is a set of permissions. The roles assigned to a user decide which features they can use in the web interface, and whether they can view or change them. A role can have only some of the permissions for a feature. For example, the Analyze manager role can view Accounts and Users, because you can filter reports by account and user, but it cannot edit them.



Default roles

Default roles cover common tasks and can be assigned to users as they are. You cannot change their permissions, but you can duplicate a default role to create a custom role.

The tables group roles by product. General roles apply across the platform. Some accounts still use role names from before a product was renamed, so the tables for those products show the earlier names.


General roles

The following roles apply across the platform:

RoleDescription
Account adminManages account access, security, two-factor authentication, password policies, and API keys
Analyze managerTracks message and channel metrics, creates reports, and finds delivery issues in logs
Campaign managerSends messages in Broadcast, and creates, designs, and launches journeys
Channel setup and integrationsSets up channels and third-party integrations, including buying numbers, configuring email domains, connecting databases, and other setup needed to send or receive messages and calls
Customer profile managerManages profiles in Customer Profiles, the customer data platform
Finance managerAdds funds to the account balance, and tracks messaging cost with financial analytics.

AI Agents roles

The following roles control access to AI agents:

RoleDescription
AI Agents managerCreates, edits, deletes, tests, and activates AI agents
AI Agents viewerViews AI agents and their settings

Broadcast roles

To separate who prepares from who launches, a user cannot have both of these roles.

The following roles control Broadcast:

RoleDescription
Campaign approval managerReviews prepared campaigns and launches them in Broadcast. Cannot create or edit campaigns
Campaign content creatorCreates draft campaigns and prepares the audience in Broadcast. Cannot launch campaigns or send messages

Chatbots roles

Chatbots was previously called Answers. The following roles control Chatbots:

RoleEarlier nameDescription
Chatbot designerUnchangedCreates and edits chatbots. Can view all chatbots, their status, and analytics
Chatbot managerChatbot publisherActivates chatbots, so they become available to their audience
Chatbots viewerChatbots (view only)Monitors chatbots and analytics, with view-only access

Inbox roles

Inbox was previously called Conversations. The following roles control Inbox:

RoleEarlier nameDescription
Agent for InboxAgent for ConversationsReplies to conversations assigned to them
Analytics for InboxAnalytics for ConversationsTracks conversation efficiency on dashboards, schedules reports, and exchanges data with other systems
Inbox setupConversations setupSets up the queues, routes, automations, and other settings that Inbox needs
Supervisor for InboxSupervisor for ConversationsManages all conversations, assigned or not
Viewer for InboxViewer for ConversationsViews conversations in assigned queues, for monitoring or compliance. Does not use a seat, does not affect capacity or analytics, and cannot reply to conversations

Journeys roles

Journeys was previously called Flow. The following roles control Journeys:

RoleEarlier nameDescription
Content managerUnchangedCreates, edits, and deletes message content in Messages, a journey feature
Journey managerUnchangedSame as Campaign manager in General roles: sends messages in Broadcast, and creates, designs, and launches journeys
Journey publisherFlow controllerLaunches, stops, and cancels journeys

Knowledge base roles

The following roles control access to the knowledge base:

RoleDescription
Knowledge base managerCreates, edits, and publishes the knowledge base
Knowledge base userViews published content in the knowledge base


View and manage roles

To open roles, select the Account settings icon (gear) in the web interface header, and go to Roles. The page has two tabs:

  • Default: Default roles.
  • Custom: Roles created for your organization.

Manage default roles

You cannot change the permissions of a default role. On the Default tab, select the three-dot menu next to the role:

  • Edit: Assign users to the role.
  • Duplicate: Create a copy of the role. The copy is a custom role, which you can change and assign to users.

Create a custom role

Create a custom role when the default roles do not fit your needs. The platform updates default roles automatically when it adds features. It does not update custom roles: users with the Account admin role update them in the web interface.

To create a custom role:

  1. On the Custom tab, select Create role.
  2. Enter a role name, and optionally a description of up to 500 characters.
  3. On the Permissions tab, select the permissions. The web interface groups permissions in sections, such as Analyze, Broadcast, and Channels and numbers. To find a permission, search for it. To select every permission in a section, select Select all.
  4. On the Users tab, select Select users.
  5. From All users, select one or more users.
  6. Select Create role.

Import permissions from default roles

In step 3, instead of selecting each permission, you can import the permissions of one or more default roles:

  1. On the Permissions tab, select Import permissions.
  2. In the Import permissions window, select each default role you want to import, and then select Import.
  3. Add or remove permissions as needed, and continue with step 4.

The import adds the permissions to the ones you already selected. It does not replace them. Your custom role gets the permissions the default roles have when you import them. Later updates to the default roles do not apply to your custom role.


Manage custom roles

On the Custom tab, you can search for custom roles, view their details, and edit, duplicate, or delete them.

IMPORTANTWhen you delete a custom role, all users with that role lose its permissions. You cannot undo this.


Assign roles securely

When you assign roles:

  • Give each user only the roles they need for their work.
  • Keep administrative roles separate from roles that can send traffic, and give permissions to send traffic only to the users who need them.
  • Keep the phone number and email address of each user verified and up to date.
  • Require two-factor authentication (2FA) on every login, if the option is enabled for your account. 2FA does not affect API connections.

Separate who prepares from who launches

You can let some users prepare campaigns, journeys, or chatbots, and only other users launch them. These roles control who can launch. They do not add an approval step or notify anyone, so agree within your team how you review work before you launch it.

The following roles split the work in each product:

  • Broadcast: Campaign content creator prepares campaigns, and Campaign approval manager reviews and launches them, but cannot edit them. A user cannot have both roles.
  • Journeys: Content manager prepares messages. To launch or stop journeys, a user needs Journey publisher, Campaign manager, or Journey manager. Roles can be combined, and their permissions add up, so give these three roles only to the users who launch.
  • Chatbots: Chatbot designer builds chatbots but cannot activate them. Chatbot manager can activate them.


Related pages

Manage users
Assign roles to users.

Security settings
Set SSO and 2FA for all users.

Audit log
See which user performed an action in the web interface.


Was this page helpful?