> 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-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/configuration-permissions/credentials-permissions.md).

# Credentials permissions

Controls access to stored credential sets (reusable authentication objects that integrations and systems reference for connecting to external services). Credential sets centralize sensitive authentication data (usernames, passwords, certificates) so they can be managed in one place rather than being embedded in each integration configuration.

Users can access Credentials on the **Credentials** page by going to **Settings** → **Configurations** → **Integrations** → **Credentials**.

{% hint style="info" %}

### Note

To view the **Credentials** page, users require the following view permissions:

* Integrations
* Data Sources

Without these permissions, users can't view the Credentials page.
{% endhint %}

For more information, see [Manage credentials](/cortex-agentix/configure-cortex-agentix/cortex-agentix-data-sources/administration-and-troubleshooting/integrations/manage-credentials.md).

| Permission | Description                                                                                                                                                                                                                                                                                          | Role Example                                                                                                                                                               |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| View       | <p>Enables backend API read access to credential sets (e.g., for automation or API-based workflows).</p><p>If users have access to the <strong>Credentials</strong> page, they can view a list of stored credential sets and their names. Users can't create, modify, or delete credential sets.</p> | <ul><li>SOC Tier-1, 2, and 3 Analysts: May need to verify credential status/credential configurations.</li><li>Threat Hunter: Verify integration authentication.</li></ul> |
| View/Edit  | If users have access to the **Credentials** page, they can manage credential sets, including creating, deleting, and editing credentials.                                                                                                                                                            | Security Engineer: Manage integration credentials.                                                                                                                         |

**Required and recommended permissions**

Credentials often serve as dependencies for other automation and integration tasks. Consider adding these permissions:

| Permission   | Permission Level  | Reason                                                                                                                                                                                                                                                          |
| ------------ | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Integrations | View or View/Edit | <ul><li>View: Core permission to access the <strong>Credentials</strong> page. Required.</li><li>View/Edit: Highly Recommended. Users who manage credentials typically also need to configure integration instances that reference those credentials.</li></ul> |
| Data Sources | View              | View: Core permission to access the **Credentials** page. Required.                                                                                                                                                                                             |
| Playbooks    | Enabled           | Strongly recommended to view integrations that use the stored credentials.                                                                                                                                                                                      |
| Scripts      | Enabled           | Strongly recommended to view scripts that may use credentials for external API calls.                                                                                                                                                                           |
| Marketplace  | View              | Recommended. Allows browsing and installing integration content packs from the Marketplace, which may include integrations that use credential sets.                                                                                                            |
| Audit        | View              | Recommended to track credential creation, modification, and usage for security compliance.                                                                                                                                                                      |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/configuration-permissions/credentials-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.