> 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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/dashboards/share-a-dashboard.md).

# Share a Dashboard

Share dashboards with users by role in Cortex XSOAR 6.12.

Dashboards can be shared for all users or for users in specific roles. While system dashboards cannot be shared, you can duplicate a system dashboard and share the copy.

To share a dashboard, select the specific roles and decide whether the dashboard has the following permissions:

* **Read & Edit**: Edit, copy, share, export import, and remove the dashboard. For example, analysts may want to enable and encourage team-based dashboards, so that dashboards can be edited and maintained by more than a single user.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Only dashboard owners can delete their dashboards.</p></div>
* **Read only**: Copy, export, import and remove the dashboard (cannot share or edit).

  Once shared, regardless of who creates the dashboard, any user who has read and write permissions can change the sharing options including to stop sharing. If an analyst who has created and shared the dashboard, deletes the shared dashboard, it is removed from all users.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Default Administrators can read and edit shared dashboards regardless whether an analyst selects read only.</p></div>

If you are using a remote repository, all dashboards are automatically shared in the development environment. As a result, the **Share** option cannot be selected from the settings menu.

To add a shared dashboard, the user can add the shared dashboard or the user who wants to share the dashboard, can send the URL.

1. Go to the dashboard to share.
2. Select ![cog-wheel.png](https://4128117757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9gZ0C5CI8Bl5Aulkp4dZ%2Fuploads%2Fgit-blob-09c2343bd43f6353aa3f4511e45ee48849ea22c6%2F125be4c4fbd2cd5ff856e7dd65741f8d3f75aa6526a8ed9dbc7e4410a7a4596f.png?alt=media) **Share**.
3. In the **Share dashboard** dialog box, select the required permissions to share.
4. Click **Save**.

   The dashboard is now shared among other analysts in the same role.
5. (Users) To add a shared dashboard, from the home page, select DASHBOARD → **Add dashboard** and select the shared dashboard.

   Instead of a user adding the dashboard, you can send the URL to the user.
6. To stop sharing a dashboard, do the following:
   1. Select ![cog-wheel.png](https://4128117757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9gZ0C5CI8Bl5Aulkp4dZ%2Fuploads%2Fgit-blob-09c2343bd43f6353aa3f4511e45ee48849ea22c6%2F125be4c4fbd2cd5ff856e7dd65741f8d3f75aa6526a8ed9dbc7e4410a7a4596f.png?alt=media) **Share**.
   2. In the **Share dashboard** dialog box, remove all the roles.
   3. Click **Save**.


---

# 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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/dashboards/share-a-dashboard.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.