> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-mcp-bridge-private-server.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Gladly connector

> C1 provides identity governance for Gladly. Integrate your Gladly instance with C1 for unified visibility and governance over user access.

C1 provides identity governance for Gladly. Integrate your Gladly
instance with C1 for unified visibility and governance over agent access.

## Capabilities

| Resource       | Sync                                                          | Provision |
| -------------- | ------------------------------------------------------------- | --------- |
| Users (agents) | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Teams          | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Inboxes        | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

The connector syncs your Gladly agents as users, your teams and inboxes, and
each team's agent membership as grants. It is read-only and does not provision
access.

## Gather Gladly credentials

<Warning>
  To configure the Gladly connector, you need a Gladly Administrator to create an
  API User and grant it API permission.
</Warning>

<Steps>
  <Step>
    In Gladly, a Gladly Administrator designates an agent as an **API User** and
    grants it API permission. API permissions are set on an agent-by-agent
    basis.
  </Step>

  <Step>
    Generate an **API token** for that API User. The connector reads agents,
    teams, and inboxes, so the API User must be able to read those resources.
  </Step>

  <Step>
    Note the API User's login **email**, its **API token**, and your Gladly API
    base URL, which is `https://<your-organization>.gladly.com/api/v1`.
  </Step>
</Steps>

## Configure the Gladly 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 **Gladly** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Gladly connector.
      </Step>

      <Step>
        Set the owner for this connector.
      </Step>

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

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

      <Step>
        Enter the Gladly credentials:

        * **Gladly API base URL**: Your full Gladly API URL including the
          `/api/v1` suffix, for example
          `https://yourcompany.gladly.com/api/v1`.
        * **Gladly API user email**: The login email of the API User.
        * **Gladly API token**: The API token for that API User.
      </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 Gladly connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    Follow these instructions to run the Gladly connector in your own
    environment.

    <Steps>
      <Step>
        Create a secret for the Gladly API token.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_GLADLY\_BASE\_URL**: Your full Gladly API URL including the
          `/api/v1` suffix, for example
          `https://yourcompany.gladly.com/api/v1`.
        * **BATON\_GLADLY\_AGENT\_EMAIL**: The login email of the API User.
        * **BATON\_GLADLY\_API\_TOKEN**: The API token for that API User.
      </Step>

      <Step>
        Deploy the connector using your standard self-hosted connector process.
      </Step>
    </Steps>

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