> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-lee-google-cloud-project-mcp-setup.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Lokalise connector

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

C1 provides identity governance for Lokalise. Integrate your Lokalise
teams with C1 for unified visibility and governance over user access.

## Capabilities

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

The connector reads every team the configured API token can see, then each
team's users and user groups. Team membership carries the user's team role
(owner, admin, biller, or member) as a profile attribute, and group
membership comes from the member list on each group.

<Note>
  User groups are available on Lokalise Pro and Enterprise plans. On teams
  whose plan does not include groups, the connector simply syncs no groups
  for that team — users and team membership still sync normally.
</Note>

## Gather Lokalise credentials

<Warning>
  To configure the Lokalise connector, you need an API token from a team
  owner or admin. A read-only token is sufficient — the connector never
  writes.
</Warning>

<Steps>
  <Step>
    Sign in to Lokalise as a team owner or admin.
  </Step>

  <Step>
    Open your personal profile and go to the **API tokens** section.
  </Step>

  <Step>
    Generate a **read-only** API token and copy it.
  </Step>
</Steps>

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

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

        * **Lokalise API token**: the read-only API token you copied
          from your personal profile.
        * **Lokalise API base URL**: enter
          `https://api.lokalise.com/api2` — Lokalise's hosted service
          is always at this address.
      </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 Lokalise connector is now pulling access data into C1.
  </Tab>

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

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

      <Step>
        Configure the connector environment variables:

        * **BATON\_LOKALISE\_API\_TOKEN**: the read-only API token you
          copied from your personal profile.
        * **BATON\_BASE\_URL**: `https://api.lokalise.com/api2` —
          Lokalise's hosted service is always at this address.
      </Step>

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

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

<Note>
  Lokalise limits each API token to 6 requests per second. The connector
  stays inside this budget by syncing with low concurrency and retrying
  rate-limited requests, so large teams may take a little longer to sync.
</Note>