> ## 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 Re:amaze connector

> C1 provides identity governance for Re:amaze. Integrate your Re:amaze account with C1 for unified visibility and governance over staff access.

C1 provides identity governance for Re:amaze. Integrate your Re:amaze account
with C1 for unified visibility and governance over the staff who can access
your customer-support helpdesk.

## Capabilities

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

The connector syncs Re:amaze staff as users. Each staff member's role is
recorded as an informational attribute on the user. Re:amaze does not expose
roles as a separate, governable resource, so roles are not synced on their own.

## Gather Re:amaze credentials

<Warning>
  You need an administrator account on your Re:amaze brand to create an API
  token.
</Warning>

<Steps>
  <Step>
    Sign in to your Re:amaze brand at `https://<brand>.reamaze.io`, where
    `<brand>` is your brand subdomain.
  </Step>

  <Step>
    Open **Settings** and locate the **API token** for your account. The token
    is paired with the login email of the account that owns it.
  </Step>

  <Step>
    Copy three values: your **brand subdomain** (the `<brand>` part of your
    Re:amaze URL), your **login email**, and your **API token**.
  </Step>
</Steps>

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

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

        * **Brand subdomain**: your brand subdomain, e.g. `acme`.
        * **Login email**: the email of the account that owns the API token.
        * **API token**: the Re:amaze API 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 Re:amaze connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create a secret for the Re:amaze API token.
      </Step>

      <Step>
        Configure the connector with:

        * **Brand subdomain**: your brand subdomain, e.g. `acme`.
        * **Login email**: the email of the account that owns the API token.
        * **API token**: the Re:amaze API token (stored as a secret).
      </Step>

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

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