> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fabricgateway.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fabricgateway.ai/_mcp/server.

# Manage credentials and vaults

> Manage the credentials that the gateway uses, and understand where secrets are stored on cloud and enterprise tenants.

**Credentials** holds the gateway keys that callers use and the upstream credentials that the gateway uses for your connections. For example, an upstream credential lets the gateway authenticate to an imported REST API instead of passing each caller's own credentials through. **Vaults** are the credential backends that hold your secrets. This topic explains both, and how they differ between cloud and enterprise tenants.

## Prerequisites

Before you begin, make sure you have the following:

* Access to a Fabric AI Gateway organization. Members can see **Credentials**, and Super admins can see everything in **Admin**. For details, see [Manage users and invitations](/configure/organization/users).
* A connection that needs a credential. For the import workflow that this supports, see [Connect a REST API](/configure/connections/rest-apis).

## Understand credentials

Several kinds of credentials are involved when traffic passes through the gateway:

* **Gateway keys** authenticate callers to a route. Callers send the gateway key with each request. Creating a connection doesn't create a gateway key. You create one with **Create key** on the create-connection page, or on the **Credentials** page. For setup and request examples, see [Authenticate requests with Key Auth](/configure/authentication/key-auth).
* **Upstream credentials** authenticate the gateway to a connection, such as an Anthropic API key. You usually enter the key when you create the connection, and the gateway adds it when it proxies a request. For setup steps, see [Connect an LLM provider](/configure/connections/llm-providers).

To manage credentials, select **Credentials** in the sidebar. The table lists each credential with its **Type**, **Owner**, and **Connection**. Use **Search credentials**, the **All types** filter, and the **All owner types** filter to narrow the list. Select a credential to open its details. For more information, see [Review a credential](#review-a-credential).

To add a credential, do the following:

1. On the **Credentials** page, select **Create credential**.
2. For **Type**, select one of the following:
   * **Gateway key**, used by apps and agents to authenticate with Fabric. Choose an **Owner**, and then select **Create gateway key**. Copy the key when the console shows it, because it appears only once.
   * **Upstream credential**, used by Fabric to authenticate with a connection. Choose the **Connection**, and optionally enter a **Name**. If the connection offers more than one auth requirement, choose one. Under **Managed secret**, enter the API key or other secret, and then select **Create upstream credential**. On a hosted organization, the form says the secret is stored in Fabric's managed vault. If you run your own data plane and keep your own vault, you enter a reference to the secret instead.

Connections that use AWS SigV4, Google OAuth, or Azure AD don't take a credential here. Set those up in the provider's **Connect** flow. A connection that uses OAuth connects when someone first authorizes it, so there's no credential to add.

## Review a credential

To review a credential, select it in the **Credentials** table. A panel opens with its details:

| Item                        | What it shows                                                                |
| --------------------------- | ---------------------------------------------------------------------------- |
| **Credential ID**           | The credential's unique ID, with a copy button.                              |
| **Owner**                   | Who the credential belongs to, such as your organization or a user.          |
| **Connection**              | The connection that an upstream credential is for.                           |
| **Auth type**               | How the credential authenticates, for example **Bearer token**.              |
| **Created** and **Updated** | When the credential was created and last changed.                            |
| **Managed secret**          | The secret's **Name** and a masked **Secret**. Select **Edit** to change it. |

To rotate a gateway key, select **Rotate** in the key's panel, and then confirm. Copy the new key from the **Gateway key rotated** dialog, because it appears only once. To remove a credential, select **Delete gateway key** or **Delete upstream credential** at the bottom of the panel.

## Understand vaults

A vault is a credential backend that the gateway uses to look up secrets. On an enterprise tenant, sensitive fields stay in your own vault and the control plane stores only references to them. On a cloud tenant, Postman stores them in a Postman-managed vault. For more on vaults and other gateway terms, see [Key concepts](/concepts/key-concepts).

How you use vaults depends on your tenant:

| Tenant         | Vaults                                                                                                                                                            |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cloud**      | You don't configure a vault. Fabric uses a Postman-managed vault in the background, and **Vaults** doesn't appear in the sidebar.                                 |
| **Enterprise** | You bring your own vault. The data plane runs in your cloud, so you can use the vault that already holds your secrets, and your secrets stay in your environment. |

For more about the two deployment models, see [Choose a deployment model](/evaluate/deployment-models).

## Review vaults

On an enterprise tenant, select **Vaults** under **Admin** to review your vaults. The table includes the following columns:

| Column          | What it shows                                                                                    |
| --------------- | ------------------------------------------------------------------------------------------------ |
| **Name**        | The vault's name, for example `aws-production-v2`.                                               |
| **Provider**    | The secret store that the vault uses, for example **AWS Secrets Manager**.                       |
| **Prefix**      | The path prefix under which the vault looks up secrets.                                          |
| **Cache TTL**   | How long the gateway caches values from the vault. The column shows a dash when no value is set. |
| **Auth fields** | The authentication fields that the vault requires, for example `region`.                         |
| **Actions**     | **Edit** and a trash icon for removing the vault.                                                |

Use **Search vaults** to find a vault, and select **Add** to add one.

## Next steps

* To connect a provider whose key the gateway stores, see [Connect an LLM provider](/configure/connections/llm-providers).
* To review who has access to your organization, see [Manage users and invitations](/configure/organization/users).