> ## 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 Zammad connector

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

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

## Capabilities

| Resource | Sync                                                          | Provision |
| -------- | ------------------------------------------------------------- | --------- |
| Users    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Groups   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Roles    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

The connector reads one Zammad instance. It syncs that instance's users,
groups, and roles, along with each group's membership and each user's role
assignments. Users sync as enabled or disabled based on their active state
in Zammad.

A user's per-group access levels (such as read, create, or full) and a
role's group access map are carried on the user and role profiles for
visibility, but the individual access levels are not modeled as separate
access.

## Gather Zammad credentials

<Warning>
  You need an admin agent account on your Zammad instance to create the API
  token. Tokens created by customer accounts cannot list other users and do
  not work with this connector.
</Warning>

<Steps>
  <Step>
    Sign in to your Zammad instance with an admin agent account.
  </Step>

  <Step>
    Make sure API token access is enabled on the instance: in the admin
    area, check **Settings** > **System** > **API** and turn on **API
    Token Access** if it is off.
  </Step>

  <Step>
    Open your avatar menu and go to **Profile** > **Token Access**. Create
    a new personal access token with permission to read users, groups, and
    roles (the **admin** or **admin.user**, **admin.group**, and
    **admin.role** permissions cover this).
  </Step>

  <Step>
    Copy the token when it is shown — Zammad displays it only once — and
    note your instance's API base URL. It is your Zammad address with the
    `/api/v1` path appended, for example
    `https://mycompany.zammad.com/api/v1`.
  </Step>
</Steps>

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

      <Step>
        Choose how to set up the new Zammad 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 Zammad credentials:

        * **Zammad API base URL**: your instance's full API address,
          including the `/api/v1` path, with no trailing slash. For
          example, `https://mycompany.zammad.com/api/v1`.
        * **API token**: the access token created from your admin agent
          profile.
      </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 Zammad connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create secrets for the Zammad credentials.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_ZAMMAD\_BASE\_URL**: your instance's full API address,
          including the `/api/v1` path, with no trailing slash. For
          example, `https://mycompany.zammad.com/api/v1`.
        * **BATON\_ZAMMAD\_API\_TOKEN**: the access token created from your
          admin agent profile.
      </Step>

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

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