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

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

C1 provides identity governance for Postman. Integrate your Postman team
with C1 for unified visibility and governance over who belongs to which
workspaces and which roles they hold.

## Capabilities

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

The connector reads the users in your Postman team, the workspaces in that
team, which users belong to which workspaces, and the role each user holds in
a workspace (Viewer, Editor, or Admin). A Postman Team-tier (or higher) plan is
required to read the team user list.

## Gather Postman credentials

<Warning>
  You need a Postman Team-tier (or higher) plan to read the team user list. Free
  and Solo accounts do not have a team user list and cannot be synced.
</Warning>

<Steps>
  <Step>
    In Postman, open your account settings and go to
    **[API keys](https://go.postman.co/settings/me/api-keys)**.
  </Step>

  <Step>
    Generate a new API key. The key scopes the connector to the team it was
    created in. The connector only reads users, workspaces, and workspace
    roles.
  </Step>

  <Step>
    Copy the key value. You enter it as the **API key** when configuring the
    connector.
  </Step>
</Steps>

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

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

        * **API key**: the API key you copied above.
        * **API base URL**: `https://api.getpostman.com`
      </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 Postman connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create a secret for the Postman API key.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_API\_TOKEN**: the Postman API key.
        * **BATON\_BASE\_URL**: `https://api.getpostman.com`
      </Step>

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

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