> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iru.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Doppler

> Connect Doppler to Iru Compliance with a service or personal API token to collect project, environment, and secret-metadata evidence.

### About Doppler

Iru calls the Doppler API with a **Bearer** token (**Service Token** or **Personal Token**). Evidence includes **projects**, **environments**, **secret metadata** (names, versions, change history), and **team** structure. Iru does **not** retrieve or store **plaintext secret values** - only metadata needed for compliance visibility.

### How It Works

```http theme={null}
Authorization: Bearer YOUR_TOKEN
```

| Detail             | Value                              |
| ------------------ | ---------------------------------- |
| **Category**       | Secrets management                 |
| **Authentication** | Bearer token (Service or Personal) |

* **Service Token**: Scoped to a **specific project and config**; use for narrow audits.
* **Personal Token**: Follows your user’s access across projects; use for org-wide visibility.

Official references: [Authentication](https://docs.doppler.com/reference/auth), [API reference](https://docs.doppler.com/reference/api), and [API tokens](https://docs.doppler.com/docs/api-tokens).

### Prerequisites

* Doppler access to the projects and environments your program covers.

### Connect Doppler to Iru

<Tabs>
  <Tab title="Doppler">
    <Note>
      Complete this tab before you connect the source in Compliance.
    </Note>

    <Steps>
      <Step title="Sign in to Doppler">
        Open the [Doppler dashboard](https://dashboard.doppler.com) and sign in with a user who can create **API** tokens for the workplace or project Iru will read.
      </Step>

      <Step title="Open the API tokens screen">
        Navigate to **API** for your workplace (URL pattern similar to `https://dashboard.doppler.com/workplace/api`).
      </Step>

      <Step title="Generate a token">
        Select **Generate Token** (or **Create token**) to open the creation form.
      </Step>

      <Step title="Name the token">
        Enter a label such as **Iru Compliance** so you can revoke the correct credential during audits.
      </Step>

      <Step title="Choose Service vs Personal token">
        Pick **Service Token** when you want a narrow, project/config-scoped secret, or **Personal Token** when the integration should inherit **your** user access. Align the choice with least-privilege policy.
      </Step>

      <Step title="Generate, copy, and store the value">
        Generate the token and **copy** it once. Doppler shows it only at creation. Tokens do not expire unless revoked; keep them in a secrets manager until you paste into **Iru Compliance**.
      </Step>
    </Steps>

    <Note>
      Continue on the [**Iru Compliance**](#iru-compliance) tab.
    </Note>
  </Tab>

  <Tab title="Iru Compliance">
    <Note>
      Finish the [**Doppler**](#doppler) tab first.
    </Note>

    <Steps>
      <Step title="Open Sources">
        In Iru Compliance, on the left navigation bar, expand **Compliance** and select **Sources**.

        <Frame>
          <img src="https://mintcdn.com/iru/7HsGH7lnQ8GpVmI0/assets/media/images/iru-navigation-compliance-sources.png?fit=max&auto=format&n=7HsGH7lnQ8GpVmI0&q=85&s=595982441fd777b333b3ecfea24adc24" alt="Left navigation: Compliance expanded, Sources selected" width="424" height="1056" data-path="assets/media/images/iru-navigation-compliance-sources.png" />
        </Frame>
      </Step>

      <Step title="Turn on Doppler">
        Find **Doppler** (use **Category** or **Search by name or description**). On that card, turn on the **toggle**. A browser tab or window may open for the connector wizard.
      </Step>

      <Step title="Paste the Bearer token">
        Paste the token into the **Bearer token** field.
      </Step>

      <Step title="Finish the connection">
        Click **Submit Bearer Token**. When the connection succeeds, the wizard shows **Connection Configured**.
      </Step>

      <Step title="Confirm the source is Active">
        Close the **Iru is requesting access to external services** browser tab, then return to **Compliance** → **Sources** and confirm the **Doppler** card is **Active**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

### Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing opens when you turn the source on">
    Check **pop-up blocker** settings for the Iru site and try again.
  </Accordion>

  <Accordion title="401 Unauthorized">
    No extra spaces; confirm the token was not revoked in Doppler.
  </Accordion>

  <Accordion title="Missing projects">
    **Service Tokens** are single-project - use a **Personal Token** or additional scoped tokens per project.
  </Accordion>

  <Accordion title="Exposure">
    Revoke in Doppler, issue a new token, update Iru.
  </Accordion>
</AccordionGroup>

### Considerations

<CardGroup cols={2}>
  <Card title="If a Personal Token’s user loses workspace access,…" icon="circle-info">
    If a **Personal Token**’s user loses workspace access, the token stops working - reconnect with an active account.
  </Card>
</CardGroup>

### Related Articles

<CardGroup cols={2}>
  <Card title="Sources Management" icon="plug" href="/en/compliance/sources-management">
    Browse and manage every Compliance source.
  </Card>

  <Card title="Getting Started With Compliance" icon="rocket" href="/en/compliance/getting-started-with-compliance">
    Frameworks, actions, and **Artifacts**.
  </Card>

  <Card title="Iru Overview" icon="layer-group" href="/en/iru/platform-overview/iru-overview">
    How Endpoint, Compliance, and Identity fit together.
  </Card>

  <Card title="Artifacts Management" icon="folder-open" href="/en/compliance/artifacts-management">
    Upload, review, and organize evidence from sources and actions.
  </Card>
</CardGroup>