Overview

How different user permissions affect voice access (can’t enable voice trace, geo permissions, CPS changes, enable Pay connectors, cannot see log details).

In this article we will be discussing how user permission/roles affect the various voice access scenario’s.

Environment

Twilio Console

What You Need To Know

Twilio provides its client with a Role Based Access Control (RBAC) feature to limit each end user's access and its  capabilities in Twilio Console. Clients can use this feature to secure their Twilio investments as well as what users can access  by limiting Console access for their accounts. This guide covers each of the available user roles, and their access levels.

There are 5 types of user roles that have varied levels of access to Twilio Console for voice.

• "Owner" role: Each Twilio account will only have one user in the Owner role. The owner email account is used to set up the account, and has access to every aspect of Twilio console as far as programmable voice is concerned.

Additional user roles which can be setup in the Twilio console are mentioned below. These roles have varying  levels of permissions. Each new user must be assigned one of the following roles:

• Administrator: Full access to invite and revoke access for new users, see billing history and make changes, and update project settings for programmable voice.
• Developer: Access to only the required project details for developing with Twilio - API credentials, phone numbers, development tools, logs, and usage.
• Billing Manager: Access to only the required project details for handling billing requests - logs, usage, and billing history and settings.
• Support: Access to only logs and usage.

User roles permissions matrix

Below is a table of the the permissions each user may have access to based on their role: