> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/integrations/manage-credentials.md).

# Manage credentials

Manage credentials used by integrations.

Credentials simplify and compartmentalize administrative tasks, and enable you to save login information without exposing usernames, passwords, certificates, and SSH keys. You can reuse credentials across multiple systems, for example, when using the same administrator password across multiple endpoints.

{% hint style="warning" %}

### Prerequisite

To view the **Credentials** page and manage its content, your user role must have the following minimum permissions:

* **Integrations**: View
* **Data Sources**: View
* **External Issue Mapping**: View

Without these permissions, the **Credentials** page is hidden. Furthermore, if the **Credentials** permission itself is set to **None**, the page is hidden even if the above prerequisites are met.
{% endhint %}

After you set up a credential, you can configure integration instances to use it instead of entering the name and password manually.

**Add credentials to an integration instance**

1. Create the credential.
   1. Select **Settings → Configurations → Integrations → Credentials → New Credential**.
   2. Add the following parameters:

      | Parameters      | Description                                                                                                                             |
      | --------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
      | Credential Name | The name of the credential. You select this name when adding the credential to the integration instance.                                |
      | Username        | The username for the credential.                                                                                                        |
      | Workgroup       | The workgroup to associate this credential with. Relevant for third-party services, such as Active Directory, CyberArk, and HashiCorps. |
      | Password        | The password for the credential. For example, add the API Key when defining the API credential.                                         |
      | Certificate     | Certificate or SSH to use for the credential.                                                                                           |
   3. Save the credential.
2. Add the credential to the integration instance.
   1. Go to **Settings → Data Sources & Integrations** and select the integration.
   2. Click **Add Instance**.
   3. Locate the relevant section and click **Switch to credentials**.

      If there is more than one credential, select the relevant credential.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>If your user role has the <strong>Credentials</strong> permission set to <strong>None</strong>, the <strong>Switch to credentials</strong> option is hidden. Instead, the message <strong>Credentials are locked by admin</strong> is displayed, and you cannot reference stored secrets. This restriction applies to both data sources and unified connectors.</p></div>
   4. **Test** and **Save & Exit** the integration instance.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/integrations/manage-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.