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

# Doppler

> Sync environment variables from Doppler into workspaces.

Replicas integrates with [Doppler](https://doppler.com) to sync secrets from your Doppler configs directly into workspace environment variables. Connections are configured per [environment](/features/environments), so you can connect different Doppler projects or configs to your Global environment and to any named environment.

## Setup

<Note>Only organization admins can connect Doppler.</Note>

1. In Doppler, open the project and config you want to sync from
2. Go to **Access → Tokens** (or the **Tokens** tab on the config) and [generate a Service Token](https://docs.doppler.com/docs/service-tokens) with read access. The token starts with `dp.st.`
3. Go to [Environments](https://tryreplicas.com/dashboard/environment) in the Replicas sidebar
4. Pick the environment you want to connect (Global or any named environment)
5. Open the **Variables** tab, scroll to the **Integrations** section, and click **Connect Doppler**, then fill in:
   * **Service Token**: the `dp.st.*` token from Doppler
   * **Project**: the Doppler project slug
   * **Config**: the config name (e.g., `dev`, `stg`, `prd`)
   * **API Host**: only needed for self-hosted Doppler instances (defaults to `https://api.doppler.com`)
6. Click **Save & Connect**. Replicas validates the credentials before saving

You can connect Doppler independently in each environment. For example, you might sync a staging config in Global and a production config in an environment bound to a specific repository.

## How It Works

When a workspace is created, Replicas authenticates with Doppler using the stored Service Token for the workspace's environment (and Global, if configured), fetches all secrets via the `/v3/configs/config/secrets/download` endpoint, and injects them as environment variables into the workspace.

### Priority

Doppler secrets follow the same priority ordering as manual environment variables, but within each environment, manual variables always override Doppler secrets:

1. Global Doppler secrets (lowest)
2. Global manual environment variables
3. Target environment Doppler secrets
4. Target environment manual environment variables (highest)

If you define a variable manually in the same environment with the same key as a Doppler secret, the manual value wins. A target-environment Doppler secret overrides a Global manual variable.

### Test Sync

After connecting, use the **Test Sync** button to verify that Replicas can reach your Doppler config and see which secret keys are available. Secret values are never displayed; only the key names are shown.

## Reconfiguring

Click **Reconfigure** to update the Service Token, change the project, or switch the config. The new credentials are validated before saving.

## Copying or Moving Between Environments

Once a Doppler connection is configured in any environment, admins can copy or move it to another environment without re-entering credentials. From the connected environment, open the **Copy to** or **Move to** menu next to the connection to choose a target environment.

* **Copy to** duplicates the connection to the target environment. Both environments end up with the same Service Token, project, and config. The source environment keeps its connection.
* **Move to** copies to the target and then removes the connection from the source environment.

Credentials are re-encrypted server-side when cloned; the Service Token is never exposed to the browser during this operation. Only organization admins can copy or move connections.

## Disconnecting

Click **Disconnect** to remove the Doppler connection from that environment. Existing workspaces are not affected, but new workspaces in that environment will no longer receive Doppler secrets.