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

# Set up a Railway connector

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

C1 provides identity governance for Railway. Integrate your Railway workspaces
with C1 for unified visibility and governance over who can access your projects
and at what role.

## Capabilities

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

Railway project access is modeled as three entitlements per project — **Admin**,
**Member**, and **Viewer** — matching Railway's project roles. Each workspace is
synced as a group with a **Member** entitlement.

## Gather Railway credentials

<Warning>
  To configure the Railway connector you need a Railway API token that can read
  the workspaces, projects, and project members you want to govern. A team token
  provides the broadest visibility.
</Warning>

<Steps>
  <Step>
    Sign in to Railway and open your [account tokens page](https://railway.com/account/tokens).
  </Step>

  <Step>
    Create a new token. For full visibility across a team, create a token scoped
    to the team (workspace) rather than to a single project.
  </Step>

  <Step>
    Copy the token value. Railway shows it only once.
  </Step>
</Steps>

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

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

        * **API token**: The Railway API token you created above.
      </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 Railway connector is now pulling access data into C1.
  </Tab>

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

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

      <Step>
        Configure the connector environment variables:

        * **BATON\_RAILWAY\_API\_TOKEN**: The Railway API token you created above.
      </Step>

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

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