Cases saved views

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

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.
2. Select Save view.
3. In View name, enter a descriptive name.
4. 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.
5. (Optional) Set the Time range. Enable Lock time to fix the time range so it does not auto-update when the view is reopened.
6. (Optional) Enable Set as default view to make this the landing view for the product.
7. 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.
2. Locate the view.
3. Open the more actions menu next to the view.
4. 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.
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

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.

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. Select an access mode

Use the Who can access this <resource> dropdown to pick a mode:

• Private — only you can view and edit the resource. No further configuration is needed; skip to Step 5 to save.
• Public — anyone in the team with role-based access to this resource type can view and edit it. No further configuration is needed; skip to Step 5 to save.
• Advanced — opens the full policy editor for target group rules and general access. Continue with Steps 3–4 below.

Step 3. Apply to target groups (Advanced, optional)

In the Apply to target groups section, define per-group access. Rules target groups only — to grant access to an individual user, create a single-member group.

1. Search for and select a group in the group field.
2. Select an access level from the action dropdown. Available options differ by resource type — for example, Read, No Access, or Manage for saved views.
3. Select Apply to commit the rule.
4. Repeat to add more rules. To remove a rule, select the remove icon next to it.

Step 4. Set general access (Advanced)

In General access, select the default access level for everyone on your team who isn't covered by a target group rule. Available options differ by resource type.

Step 5. Save your changes

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

For the cross-product model, examples, and FAQs, see the access policies overview.

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 for the role assignments per key.

Related resources