A2P 10DLC Campaign Vetting Delays: Twilio cannot approve 10DLC Campaigns ourselves, and must rely on third parties who control our connections to carriers to sign off. These external processes are creating several week delays for our customers. We continue to escalate these issues and are working to reduce delays wherever possible. Further details will be shared in the Campaign Vetting Changes article as they become available.

Manage Flex Users

Twilio allows Flex admins to manage users in multiple ways. This guide explains the available methods for creating or adding a Flex user, and how to remove them. 

Create a Flex user

Each Flex user is represented as a TaskRouter Worker - this is described in our Flex user roles documentation. Flex users can be created in two ways:

  • Twilio Console: Twilio Console users in the role of Owner, Administrator or Developer can access Flex via Console. When doing so, a TaskRouter Worker with admin privileges is created for this user. This is the recommended method for creating Administrator workers for Flex. To manage the Console users associated with your Flex project, see Adding, Removing, or Modifying Users with Your Twilio Project.
  • Single Sign-On (SSO): Once SSO authentication is integrated for your Flex instance, users access Flex via SSO authentication using your identity provider (IdP). In this situation, the attributes passed by your IdP when a user logs in will determine the role for the created TaskRouter worker. This is the recommended method for creating non-Administrator workers (i.e., agents and supervisors). Please note that if you want your Administrators to have access to the Twilio Console, you should create them in the Console and not via SSO.

Remove a Flex User

After a Flex User and associated TaskRouter Worker has been created, removing the user requires two steps.

  1. Remove the TaskRouter Worker from you Workspace.
  2. Remove access to Flex from the original source:
Have more questions? Submit a request
Powered by Zendesk