> 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/configuration-permissions/object-setup-permissions/layout-permissions.md).

# Layout permissions

Controls access within Object Setup (**Settings** → **Configurations** → **Object Setup**) to the following:

* Case layouts (**Cases** → **Layouts**): Visual layout definitions that determine how case data is presented when viewing a case. Layouts define which fields are shown, their arrangement in sections/tabs:
* Case layout rules (**Cases** → **Layout Rules**): Rules that determine which layout is applied to a given case based on conditions (e.g., case type, source, severity).
* Issue layouts (**Issues** → **Layouts**): Visual layout definitions that determine how alert data is presented when viewing an issue. Layouts define which fields are shown, their arrangement in sections/tabs, and widget configurations.
* Issue layout rules (**Issues** → **Layout Rules**): Rules that determine which layout is applied to a given issue based on conditions (e.g., issue type, source, severity).

| Permission | Description                                                                                                                                            | Roles Example                                                                                                                                                              |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | Users have no access to layout configurations or rules. They can see data rendered in assigned layouts, but cannot modify the definitions              | <ul><li>SOC Tier-1 Analyst: Layout configuration is an administrative function.</li><li>Threat Hunter: Layout configuration is outside the threat hunting scope.</li></ul> |
| View       | Read-only access to all layout definitions and rules. The user can browse the layouts table (cases and issues) and browse layout rules and conditions. | SOC Tier-2 and 3 Analysts: May need to understand the layout structure for reporting purposes and to know what data is available in different views.                       |
| View/Edit  | Full read/write access to create, edit, copy, and delete custom layouts and layout rules.                                                              | Security Engineer: Designs and implements custom layouts for alerts and incidents; builds the visual experience.                                                           |

### Required and recommended permissions

Consider adding the following permissions:

| Permission       | Permission level | Reasons                                                                                            |
| ---------------- | ---------------- | -------------------------------------------------------------------------------------------------- |
| Cases & Issues   | View             | Required to edit layout rules and need to see case/issue data when creating/editing a layout rule. |
| Fields and Types | View             | Required to see available fields when building layouts; essential for layout design.               |
| Case Properties  | View             | Strongly recommended to understand the case structure (statuses, domains) for layout design.       |
| Marketplace      | View/Edit        | Recommended to install content packs that include layout definitions.                              |
| Audit            | View             | Recommended to track layout changes.                                                               |


---

# 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/configuration-permissions/object-setup-permissions/layout-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.