> ## 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 Rocket.Chat connector

> C1 provides identity governance for Rocket.Chat. Integrate your Rocket.Chat workspace with C1 for unified visibility and governance over user access.

C1 provides identity governance for Rocket.Chat. Integrate your Rocket.Chat
workspace with C1 for unified visibility and governance over user access.

## Capabilities

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

The connector reads one Rocket.Chat workspace. It syncs the workspace's
users, roles, and teams, along with each user's workspace-level role
assignments and each team's membership. Users sync as enabled or disabled
based on their active state in Rocket.Chat, and bot and app accounts are
labeled as service accounts. Users reached through Matrix federation are
marked with a federated attribute.

Roles cover both the built-in roles (admin, user, bot, and so on) and any
custom roles defined in the workspace. Role assignments reflect
workspace-level roles; roles scoped to individual channels (such as owner
or moderator of a single room) sync as role resources for visibility but
do not carry per-channel assignments.

## Rate limits

<Warning>
  Rocket.Chat's REST API limits each endpoint to **10 requests per 60
  seconds** by default. The connector backs off and retries automatically
  when it hits the limit, but on workspaces with many users or teams a sync
  can take noticeably longer under the default limit. Workspace
  administrators can raise the limit under **Admin** > **Settings** > **Rate
  Limiter** to speed up syncs.
</Warning>

## Gather Rocket.Chat credentials

<Warning>
  The token's account needs administrator access (or at minimum permission
  to view users, roles, and all teams — including the **view-all-teams**
  permission). A token created by a regular user cannot list other users or
  teams it is not a member of and does not work with this connector.
</Warning>

<Steps>
  <Step>
    Sign in to your Rocket.Chat workspace as an administrator, or use a
    dedicated service account with administrator access.
  </Step>

  <Step>
    Open your avatar menu and go to **My Account** > **Personal Access
    Tokens**. If personal access tokens are disabled, a workspace
    administrator can enable them under **Admin** > **Settings** >
    **Accounts** > **Personal Access Tokens**.
  </Step>

  <Step>
    Enter a token name and click **Add**. Rocket.Chat shows the new
    token and the matching **user ID** once — copy both. The connector
    needs the pair: the token is sent as the `X-Auth-Token` header and
    the user ID as the `X-User-Id` header.
  </Step>

  <Step>
    Note your workspace's base URL. For Rocket.Chat Cloud this is
    `https://<workspace>.rocket.chat`; for self-hosted servers it is your
    own address, with no trailing slash.
  </Step>
</Steps>

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

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

        * **Rocket.Chat base URL**: your workspace's address, with no
          trailing slash. For example, `https://mycompany.rocket.chat`.
        * **User ID**: the user ID shown when the personal access token
          was created.
        * **Auth token**: the 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 Rocket.Chat connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create secrets for the Rocket.Chat credentials.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_ROCKETCHAT\_BASE\_URL**: your workspace's address, with no
          trailing slash. For example, `https://mycompany.rocket.chat`.
        * **BATON\_ROCKETCHAT\_USER\_ID**: the user ID shown when the
          personal access token was created.
        * **BATON\_ROCKETCHAT\_AUTH\_TOKEN**: the personal access token.
      </Step>

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

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