> 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/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/access-and-visibility-for-dashboards-and-reports/access-and-sharing-cheat-sheet.md).

# Access and sharing cheat sheet

Use this Cortex XSIAM reference to manage dashboard and report access and sharing.

For detailed information on managing access to Dashboards and reports see [Manage access to objects](/cortex-xsiam/onboard-cortex-xsiam/post-deployment/manage-user-roles-and-access-management/manage-access-to-objects.md).

<table><thead><tr><th width="120.0001220703125">Object</th><th>RBAC permissions</th><th width="115">Visibility settings</th><th>Sharing and duplicating</th></tr></thead><tbody><tr><td><strong>Command centers</strong></td><td><p>• <strong>Dashboards &#x26; Reports > Dashboards > Enabled</strong></p><p>and</p><p>• <strong>Command Center Dashboards > View</strong></p></td><td><strong>Public</strong> and visible to all authorized users.</td><td>Cannot be duplicated, edited, or deleted.</td></tr><tr><td><strong>System dashboards</strong></td><td><strong>Dashboards &#x26; Reports > Dashboards > Enabled</strong></td><td><strong>Public</strong> and visible to all authorized users.</td><td><p>• Cannot be edited or deleted.</p><p>• Users with access to a dashboard can duplicate it or create report templates from it.</p></td></tr><tr><td><strong>Custom dashboards</strong></td><td><strong>Dashboards &#x26; Reports > Dashboards > Enabled</strong></td><td><strong>Restricted</strong> by default.</td><td><p>• <strong>Owner</strong> can grant <strong>Editor</strong> or <strong>Viewer</strong> permissions to specific users, groups, or API keys, or change the access level to <strong>Public</strong>.</p><p>• If <strong>Restricted</strong>, users with <strong>Editor</strong> permission can take actions on the dashboard.</p><p>• Users with <strong>Viewer</strong> permission can view, duplicate, or generate reports.</p></td></tr><tr><td><strong>System report templates</strong></td><td><strong>Dashboards &#x26; Reports> Reports > Enabled</strong></td><td><strong>Public</strong> and visible to all authorized users.</td><td><p>• Cannot be edited or deleted.</p><p>• Users with access to a template can generate reports or duplicate it.</p></td></tr><tr><td><strong>Custom report templates</strong></td><td><strong>Dashboards &#x26; Reports> Reports > Enabled</strong></td><td><strong>Restricted</strong> by default.</td><td><p>• <strong>Owner</strong> can grant <strong>Editor</strong> or <strong>Viewer</strong> permissions to specific users, groups, or API keys, or change the access level to <strong>Public</strong>.</p><p>• If <strong>Restricted</strong>, users with <strong>Editor</strong> permission can take actions on the report.</p><p>• Users with <strong>Viewer</strong> permission can view, duplicate, or generate reports.</p></td></tr><tr><td><strong>Custom widgets</strong></td><td><strong>Dashboards &#x26; Reports> Reports > Enabled</strong></td><td><strong>Restricted</strong> by default</td><td><p>• Owner can change the access level to <strong>Public</strong>.</p><p>• If a widget (Public or Restricted) is included on a shared dashboard, users with access to dashboard can view the widget.</p></td></tr></tbody></table>

c


---

# 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/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/access-and-visibility-for-dashboards-and-reports/access-and-sharing-cheat-sheet.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.
