> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/administration/create-and-manage-saved-views.md).

# Create and Manage Saved Views

Prisma Cloud offers the ability to create **Saved Views** to prioritize and organize your data into categories that are meaningful to your organization. Saved views are available on the Governance, Alerts, Compliance, and Dashboards pages. For instance, on the Alerts page Prisma Cloud provides a set of default views — Overview, Misconfigurations, Incidents, Malware, and Highest Priority, but you can also create a custom view and share it with others in your organization or tenant. Review the Alerts page workflows below to create, manage, and share your Saved Views.

Default (**System**) views are initially the opinionated suggestion of what a view should be based upon the problem being solved. Views such as **High-Priority**, **Attack Paths**, and **Incidents** etc, include preset filters that display the most relevant alerts for each category. Changes to a Default view are saved and will persist the next time you view it. Default views do not reset to the initial System view and cannot be deleted or reordered. **Overview**, which is the first view, also cannot be hidden.

1. Add a view to your **Saved Views**.
   1. Navigate to **Home > Alerts**. Provide a unique identifier for your new View.
   2. Select **Menu > Add View** to create your custom view. Check the **Copy current view configuration** box to clone the your current Alerts view configuration.
   3. Select **Add New View** to save your custom view. Custom views are limited to a maximum of 20.
2. **Manage Views**
   1. Select **Menu > Manage Views** to reorder, hide/show, duplicate, and delete your saved views.
   2. Select **Done** to confirm your changes.
3. **Share Views: Update Access Setting**
   1. Select **Alerts > Menu** and navigate to the custom view that you’ve created that you wish to share.
   2. Choose the action menu on the right and select **Share**.
   3. Select **Public** from the **Access Settings** drop-down and click **Update**.
   4. Share the URL of your View with anyone in your organization to provide access.
4. Optionally, follow the steps below to help your users discover the View you’ve created:
   1. We recommend that you guide users to toggle on the the **Visibility** setting of the shared View under **Alerts > Menu > Manage Views**.
   2. Once the View is shared globally, it will appear by default at the bottom of the **Manage Views** list and can be reordered to the top by individual users for easy access. If the user you wish to share a view with, is currently on the Alerts page, they will also need to refresh the page to see the shared view.

If you are a user and you’ve received a URL for a shared View and you haven’t updated the View’s **Visibility** settings, the shared View will only show up temporarily on the Menu tab. To ensure it’s always accessible follow the steps listed above.


---

# 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://docs.prismacloud.io/content-collections/administration/create-and-manage-saved-views.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.