ConductorOne provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.
This is version 2 of the Twilio Segment connector. This version uses the Segment Public API and introduces role-based access modelling, session-cached role lookups, and support for Sources, Warehouses, Functions, and Spaces as first-class resources.
Additional functionality:
The Twilio Segment connector supports automatic account deprovisioning by removing users from the workspace.Notes:
Roles are Segment’s built-in IAM roles (e.g., Workspace Owner, Source Admin, Function Admin). They are system-defined and cannot be created or deleted.
Warehouses and Spaces require a Business plan workspace. Warehouses do not support role provisioning via the Segment Public API.
Invites represent pending workspace invitations. Creating an invite sends an email to the specified address.
To configure the Twilio Segment connector, you need Workspace Owner or Workspace Admin permissions in Segment. The Personal Access Token inherits the permissions of the user who creates it.
Navigate to Settings > Workspace Settings > Access Management, then select the Tokens tab.
3
Click Create Token
4
Give the new token a name, such as “ConductorOne”.
5
Assign the token the Workspace Owner access level.This access level is required to read information about groups, resources, and roles in the workspace.
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
1
In ConductorOne, navigate to Integrations > Connectors and click Add connector.
2
Search for Twilio Segment and click Add.
3
Choose how to set up the new Twilio Segment connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Paste your credentials into the relevant fields:
Access Token: Your Segment Personal Access Token
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Twilio Segment connector is now pulling access data into ConductorOne.
Follow these instructions to use the Twilio Segment connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
In ConductorOne, navigate to Integrations > Connectors > Add connector.
2
Search for Baton and click Add.
3
Choose how to set up the new Twilio Segment connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
In the Settings area of the page, click Edit.
7
Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
2
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Twilio Segment connector to. Twilio Segment data should be found on the Entitlements and Accounts tabs.
That’s it! Your Twilio Segment connector is now pulling access data into ConductorOne.
