Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

Access Control


(new)

Public Beta Notice

Role Based Access Control (RBAC) is available as a public beta release. Twilio might add or change features before declaring RBAC Generally Available. Beta products aren't covered by a Twilio SLA.

Learn more about beta product support(link takes you to an external page).

With Twilio's role-based access control (RBAC) platform, you can grant access to Twilio resources in a granular way and prevent access to other resources. Twilio RBAC lets you adopt the security principle of "least privilege access" for users in your Twilio accounts.

Here are the key features of the Access Control product:

  • Control access to Twilio resources with built-in roles that range in scope from your whole organization down to viewing only a specific product for a specific subaccount.
  • Manage role assignments across multiple accounts and subaccounts in one place using the self-serve RBAC management interface in Twilio Admin.

View role assignments

view-role-assignments page anchor
Twilio ConsoleLegacy Console
  1. Log in to Twilio Console(link takes you to an external page) and navigate to Settings > Organization settings > Users(link takes you to an external page).
    The User management page lists all the users in your organization and their role assignments. You can search by user's name, email, SID, role name or scope name. Scope specifies the boundary within which a role assignment will apply. It can be a managed account, subaccount, or even your organization.
  2. To view a user's role assignment details, click the user's name, then click the Role Assignments tab.
  3. All the user's role assignments, grouped by scope name, will be listed as separate rows. Resource-based role assignments are at the organization scope level but will be listed as separate rows.

Add a new role assignment

add-a-new-role-assignment page anchor

When you assign roles to a user, you start by selecting the scope: organization, account, or subaccount. Then you can assign one or more roles to the user for the specified scope. Depending on the scope, you can select from General or Built-in roles. Learn more about role types.

Users can have multiple roles in multiple scopes. You can assign up to 25 built-in roles per user across all scopes.

Twilio ConsoleLegacy Console
  1. Log in to Twilio Console(link takes you to an external page) and navigate to Settings > Organization settings > Users(link takes you to an external page).
  2. Click the user's name, then click the Role Assignments tab.
  3. Click Create role assignment.
  4. On the Create role assignment page, select the scope type, scopes, and roles. If the role selected is resource-based then addtional fields resource and resource values have to be selected.
  5. Click Save changes.

Delete a user's role assignments

delete-a-users-role-assignments page anchor
Twilio ConsoleLegacy Console
  1. Log in to Twilio Console(link takes you to an external page) and navigate to Settings > Organization settings > Users(link takes you to an external page).

  2. Click the user's name, then click the Role Assignments tab.

    • To remove the role assignment for the scope, click Delete.
    • To remove a specific role from the assignment, click Edit, remove the role, and click Save changes.

View roles & permissions

view-roles--permissions page anchor
Twilio ConsoleLegacy Console
  1. Log in to Twilio Console(link takes you to an external page) and navigate to Organization settings > Users(link takes you to an external page).
  2. Click the Roles tab.
  3. To view a role's details, click View details. Resource-based roles will be displayed with a tag below the role name.
(information)

Note

  • Only users with the Organization Owner or Organization Admin role can access the Access Control pages.
  • In the legacy console, organization roles cannot be deleted from the Access control pages. Go to the User detail page from the Managed users page(link takes you to an external page) to delete organization roles.
  • Owner role for an Account cannot be deleted from the Access Control pages.