> 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/reference-and-developer-docs/role-based-access-control/investigation-and-response-permissions/automation-permissions/playground-permissions.md).

# Playground permissions

Controls Playground **Investigation & Response** → **Automation** → **Playground**, which is a testing environment for commands and scripts that is not connected to a live (active) investigation.

| Permission | Description                                                                                      | Roles Example                                                                                                                |
| ---------- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| None       | Users cannot access the **Playground** page and cannot test commands, scripts, and integrations. | SOC Tier-1 analysts: Do not need Playground access for basic triage.                                                         |
| View/Edit  | Users can access the **Playground** page and can test commands, scripts, and integrations.       | SOC Tier 2 and 3 Analysts, Security Engineers, and Security Admins: Benefit from playground access for testing and learning. |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission     | Permission Level | Reason                                                     |
| -------------- | ---------------- | ---------------------------------------------------------- |
| Scripts        | Enabled          | Strongly recommended to see the scripts being tested.      |
| Playbooks      | Enabled          | Strongly recommended to test playbook commands in context. |
| Cases & Issues | View             | Recommended, as commands reference case data.              |
| Query Center   | View             | Recommended for XQL query testing.                         |


---

# 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-xsiam/reference-and-developer-docs/role-based-access-control/investigation-and-response-permissions/automation-permissions/playground-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.