> 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-xsiam/configure-cortex-xsiam/automations/ai-prompts/ai-prompts-role-based-access-control.md).

# AI prompts role-based access control

Manage Cortex XSIAM AI prompt permissions using role-based access control.

Instance and Account admins have full control over the permissions and access that users have to AI prompts. Cortex XSIAM uses role-based access control (RBAC) to manage access to the AI prompts library, as well as access to create, edit and delete prompts in the prompts library and in the playbook editor.

By default, Instance and Account admins have full view/edit permissions enabled. When editing or creating other roles, in the **CORTEX AGENTIC ASSISTANT** section, you can enable **AI Prompts**. If you enable the feature for a role, the user can view prompts in the AI prompts library. In addition, after enabling **AI Prompts**, you can select the following:

| Permission                        | Description                                                                                  |
| --------------------------------- | -------------------------------------------------------------------------------------------- |
| Manage prompts library            | When selected, the user role can create, edit, and delete prompts in the AI prompts library. |
| Manage prompts in playbook editor | When selected, the user role can create and edit AI prompts in the playbook editor.          |


---

# 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-xsiam/configure-cortex-xsiam/automations/ai-prompts/ai-prompts-role-based-access-control.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.