> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Twilio Segment connector

> C1 provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

<Tip>
  **This is an updated version of the Twilio Segment connector.** This version uses the [Segment Public API](https://docs.segmentapis.com/) and introduces role-based access modelling, session-cached role lookups, and support for Sources, Warehouses, Functions, and Spaces as first-class resources.
</Tip>

## Capabilities

| Resource   | Sync                                                          | Provision                                                     |
| :--------- | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Users      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Groups     | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Roles      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Invites    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Sources    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Warehouses | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Functions  | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Spaces     | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

**Additional functionality:**
The Twilio Segment connector supports [automatic account deprovisioning](/product/admin/account-provisioning) 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.
* Invites represent pending workspace invitations. Creating an invite sends an email to the specified address.
* Groups (User Groups) are a **Business plan** feature.

## Gather Twilio Segment credentials

<Warning>
  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.
</Warning>

<Steps>
  <Step>
    Log in to your Segment workspace at [app.segment.com](https://app.segment.com).
  </Step>

  <Step>
    Navigate to **Settings** > **Workspace Settings** > **Access Management**, then select the **Tokens** tab.
  </Step>

  <Step>
    Click **Create Token**
  </Step>

  <Step>
    Give the new token a name, such as "C1".
  </Step>

  <Step>
    Assign the token the **Workspace Owner** access level.

    This access level is required to read information about groups, resources, and roles in the workspace.
  </Step>

  <Step>
    Click **Create**.
  </Step>

  <Step>
    Carefully copy and save the new token.
  </Step>
</Steps>

**Done.** Next, move on to the connector configuration instructions.

For more information, see the [Segment Access Management documentation](https://segment.com/docs/segment-app/iam/).

## Configure the Twilio Segment connector

<Tabs>
  <Tab title="Cloud-hosted">
    Follow these instructions to use a built-in, no-code connector hosted by C1.

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Twilio Segment** and click **Add**.
      </Step>

      <Step>
        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 C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Paste your credentials into the relevant fields:

        * **Access Token** (required): Your Segment Personal Access Token
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Twilio Segment connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    Follow these instructions to use the [Twilio Segment](https://github.com/conductorone/baton-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 C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Step 1: Set up a new Twilio Segment connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        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 C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Twilio Segment connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-segment-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-segment-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>

      # Twilio Segment credentials
      BATON_TOKEN: <Your Segment Personal Access Token>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: true
    ```

    See the [connector README](https://github.com/conductorone/baton-segment) or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-segment.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-segment
      labels:
        app: baton-segment
    spec:
      selector:
        matchLabels:
          app: baton-segment
      template:
        metadata:
          labels:
            app: baton-segment
            baton: true
            baton-app: segment
        spec:
          containers:
          - name: baton-segment
            image: ghcr.io/conductorone/baton-segment:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-segment
            envFrom:
            - secretRef:
                name: baton-segment-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, 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.
      </Step>
    </Steps>

    **Done.** Your Twilio Segment connector is now pulling access data into C1.
  </Tab>
</Tabs>