# Cases saved views

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Fcases%2Fsaved-views.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Fcases%2Fsaved-views.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

Save and reuse filtered Cases views to stay focused on the work that matters. A Cases saved view preserves the current configuration so you can return to common triage workflows without reapplying settings each time.

Cases saved views are part of the **Saved Views** shared component used across Coralogix products. The core experience is the same in each product; the options that get saved differ.

## What a Cases saved view captures[​](#what-a-cases-saved-view-captures "Direct link to What a Cases saved view captures")

| Option                  | Description                                                           |
| ----------------------- | --------------------------------------------------------------------- |
| **Query**               | The current search query and dataset                                  |
| **Filters**             | The applied filters                                                   |
| **Table settings**      | The column layout and formatting                                      |
| **Fields**              | The favorite fields shown in the sidebar                              |
| **Time range**          | The selected time range, with optional **Lock time** to fix the range |
| **Set as default view** | Makes this the default landing view in Cases                          |

The **Widget state** option, available in Infrastructure Explorer, does not apply in Cases.

## Create a saved view[​](#create-a-saved-view "Direct link to Create a saved view")

<!--$?-->

<!--/$-->

In Cases, the saved view also captures the **Fields** option: the favorite fields shown in the sidebar.

## Use saved views[​](#use-saved-views "Direct link to Use saved views")

Saved views in Cases appear in a sidebar panel with **Recent**, **Favorite**, and **All views** sections. The active view name appears next to **Case list** at the top of the page.

<!--$-->

* Select **All views** to open the saved views panel.
* Find views under **Recent** or **All views**.
* Use **Search saved views** to locate a view by name.
* Select a saved view to apply it.

<!--/$-->

## Update or save as new view[​](#update-or-save-as-new-view "Direct link to Update or save as new view")

<!--$-->

When a loaded view has unsaved changes, the **Save view** menu provides:

* **Update current view:** Save the changes to the loaded view.
* **Save as new view:** Save the changes as a new view, leaving the original unchanged.

<!--/$-->

## Edit, clone, or delete a saved view[​](#edit-clone-or-delete-a-saved-view "Direct link to Edit, clone, or delete a saved view")

<!--$?-->

<!--/$-->

## Share a saved view[​](#share-a-saved-view "Direct link to Share a saved view")

<!--$-->

To share a saved view with a teammate, copy the page URL after the saved view is loaded. Opening the URL applies the same query, filters, table settings, and time range.

<!--/$-->

## Manage saved views[​](#manage-saved-views "Direct link to Manage saved views")

Use saved views to standardize how teams work:

* Set a default view to speed up daily triage.
* Clone views to create variations for different workflows.
* Share common views by copying the page URL so a teammate lands on the same query, filters, table settings, and time range.

## Set the team default view[​](#set-the-team-default-view "Direct link to Set the team default view")

Admins can set a team-level default view so every team member lands on the same Cases configuration by default. Individual users can still override the team default for themselves.

To set the team default:

1. Open **Settings** and navigate to the Cases section.
2. Under **Team default view**, select an existing saved view from the dropdown.
3. Select **Save**.

To override the team default for your own account, load any saved view and select **Set as default view** in the **Save view** panel: your personal default takes precedence over the team default.

This feature requires the `CASES-TEAM-DEFAULT-VIEWS:MANAGE` permission, included only in the Platform Admin system role by default.

## Access policy[​](#access-policy "Direct link to Access policy")

By default, a new saved view is **Private** (only you can see it). To share it with everyone on your team, switch the mode to **Public**. To configure per-group access rules, switch to **Advanced**. The access levels available in **Advanced** mode are:

* **No Access**: team members cannot see the view unless they have an explicit group rule.
* **Read**: everyone on your team can see and load the view.
* **Manage**: everyone on your team can see, load, and modify the view.

<!--$?-->

<!--/$-->

For the cross-product model, examples, and FAQs, see the [access policies overview](https://docs-docusaurus.kinsta.page/user-guides/aaa/access-control/policies/.md).

## Permissions[​](#permissions "Direct link to Permissions")

The following permissions govern saved views in Cases.

| Resource                               | Required for                                                   |
| -------------------------------------- | -------------------------------------------------------------- |
| `CASES-SAVED-VIEWS:READ`               | Loading shared saved views in Cases.                           |
| `CASES-SAVED-VIEWS:MANAGE`             | Creating, editing, and deleting shared saved views.            |
| `CASES-SAVED-VIEWS:READACCESSPOLICY`   | Viewing the access policy on a saved view.                     |
| `CASES-SAVED-VIEWS:UPDATEACCESSPOLICY` | Creating, editing, or deleting access policies on saved views. |
| `CASES-TEAM-DEFAULT-VIEWS:READ`        | Seeing the configured team default view in settings.           |
| `CASES-TEAM-DEFAULT-VIEWS:MANAGE`      | Setting the team default view in settings.                     |

Building a policy also requires `TEAM-GROUPS:READSUMMARY` and `TEAM-GROUPS:READCONFIG` to select target groups. See the [permissions list](https://docs-docusaurus.kinsta.page/user-guides/aaa/access-control/permissions/permissions-list/.md#permissions-cases) for the role assignments per key.

## Related resources[​](#related-resources "Direct link to Related resources")

[Working with Cases](https://docs-docusaurus.kinsta.page/user-guides/cases/working-with-cases/.md)[Cases overview](https://docs-docusaurus.kinsta.page/user-guides/cases/overview/.md)[Saved views in Infrastructure Explorer](https://docs-docusaurus.kinsta.page/user-guides/infrastructure/infrastructure-explorer/saved-views/.md)[Saved views in Explore](https://docs-docusaurus.kinsta.page/user-guides/monitoring-and-insights/explore-screen/create-and-manage-saved-views/.md)