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

| 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

1. Configure the page using search, filters, grouping, and table settings.
1. Select **Save view**.
1. In **View name**, enter a descriptive name.
1. Under **Configuration options**, toggle which settings to save:
   - **Query:** Save the current search query and dataset.
   - **Filters:** Save the applied filters.
   - **Table settings:** Save the column layout and formatting.
1. (Optional) Set the **Time range**. Enable **Lock time** to fix the time range so it does not auto-update when the view is reopened.
1. (Optional) Enable **Set as default view** to make this the landing view for the product.
1. Select **Save view**.

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

## 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

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

Manage existing saved views from the more actions menu:

1. Open **All views**.
1. Locate the view.
1. Open the more actions menu next to the view.
1. Select one action:
   - **Edit:** Update the view name or saved configuration.
   - **Clone:** Create a copy you can modify without changing the original.
   - **Delete:** Permanently remove the view.

## 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

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

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.
1. Under **Team default view**, select an existing saved view from the dropdown.
1. 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

By default, a new saved view is **private** — only you can see it. To share a view, configure an access policy on the view. The available access levels for saved views are:

- **No access** — team members cannot see the view unless they have an explicit group rule.
- **View** — everyone on your team can see and load the view.
- **Edit** — everyone on your team can see, load, and modify the view.

Follow these steps from the resource settings panel.

### Step 1. Open the resource settings

Navigate to the resource (for example, a Custom Dashboard). Open its settings from the settings icon or more actions menu, then scroll to the **Access policy** section.

### Step 2. Set general access

**General access** controls the default access level for everyone in your team. Select an access level from the dropdown — for example, **Dashboard: No access** or **Dashboard: View**. Available options differ by resource type.

### Step 3. Add target group rules (optional)

Override the default for specific groups:

1. In the **Add groups to define a rule** field, search for and select one or more groups.
1. Set the access level for those groups using the action dropdown.
1. To add another rule, select **+ Add**.
1. To remove a rule, select the remove icon next to it.

### Step 4. Configure policy access (optional)

To control who can view or edit the policy configuration itself, toggle on **Show advanced**. This reveals a **Policy** column next to each rule, including the general access row. Set the policy access level for each row as needed.

### Step 5. Save your changes

Select **Save** to activate the policy. To restore the default policy configuration, select **Reset**.

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

## 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://coralogix.com/docs/user-guides/aaa/access-control/permissions/permissions-list/#permissions-cases) for the role assignments per key.

## Related resources

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