> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/concepts/providers/user-level-credentials.md).

# User-Level Credentials

A Scope's credential is normally shared by everyone who uses it — a team-level secret set on the Provider. **User-Level Credentials** let an individual user override that shared credential with their own, for a specific Scope, without affecting anyone else using the same Scope.

This is useful when different people need to act with their own identity against the same infrastructure — for example, each engineer using their own IAM role on a shared `aws-read-only` Scope instead of a single team credential.

## Adding a Personal Credential

Personal credentials are managed from your own **Profile**, not from the Providers admin pages.

### 1. Open Credential Overrides

Click your name at the bottom of the left-hand sidebar, then click **Profile**. Go to the **Credential Overrides** tab. It lists your personal credentials for the Scopes in your current workspace.

![Credential Overrides tab, empty state](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-824bde28fcff01c4e4849215d9725cacc49f41d3%2Fuser-level-credentials-step-01-empty.png?alt=media)

### 2. Select a scope

Click **Add Credential**. Choose the Scope you want to override from the list — it shows every Scope you have access to across your workspaces, grouped by provider, with the workspaces each Scope belongs to underneath its name. Scopes you've already overridden show a **Configured** badge.

![Select Scope modal](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-04af0a9a2284f7c4e51a6f2c63cb156c7e5351f3%2Fuser-level-credentials-step-02-select-scope.png?alt=media)

Click **Continue**.

### 3. Fill in your credential

Give it a **Display Name**, then fill in the fields for the Scope's provider type:

* **AWS** — choose **Access Key** (Access Key ID + Secret Access Key) or **IAM Role** (IAM Role ARN). For an IAM Role, an **External ID** is generated when you save; open the credential again afterwards to copy it into the role's trust policy as the `sts:ExternalId` condition.
* **Kubernetes** — choose **Kubernetes Token**, **Cloud Role**, or **Kubernetes Service Account Name**. On AKS, the choices are **Kubernetes Token**, **Service Principal**, **Managed Identity**, or **Kubernetes Service Account Name**.
* **Other providers** — the same credential fields the shared credential uses, plus any custom key/value pairs you need

![Add Personal Credential form](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-291dbe4d2e7cd0e9a283207e7a8dd5898454d843%2Fuser-level-credentials-step-03-add-form.png?alt=media)

Click **Create**.

### 4. It's active immediately

Your personal credential appears in the table and is used automatically whenever the agent acts on a message you send in a ticket that uses that Scope — no per-ticket toggle needed.

![Personal credential added, shown in the table](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-8d1c3e3b24c0159a4554b0c5ec8edd3357acc5ad%2Fuser-level-credentials-step-04-added.png?alt=media)

{% hint style="info" %}

* Your personal credential only affects **your own** ticket messages — other users on the same Scope keep using the shared credential (or their own override, if they've set one).
* Background work, such as Terraform state sync, dashboard refreshes and extension resource actions, always uses the shared credential.
* Use the **Enabled** toggle to fall back to the shared credential without losing your saved values — disabling doesn't delete the credential.
* Click **Edit** to change a credential. Stored values aren't shown; leave a field blank to keep its current value. Click **Delete** to remove it.
* Any user with access to a Scope can add their own override for it; there's no additional admin permission required.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/concepts/providers/user-level-credentials.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
