Saved views

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

Explore 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 an Explore saved view captures

In Explore, filter conditions are part of the query, so the Filters option that appears in Cases and Alerts is not surfaced separately here. The Widget state option, unique to Infrastructure Explorer, also does not apply.

Create a saved view

1. Configure Explore using your query, fields, and table settings.
2. Select Save to open the Save View panel.
3. In View name, enter a descriptive name.
4. Set the Time range. Enable Lock time to fix the time range so it does not auto-update when the view is reopened.
5. Under Configuration options, toggle which settings to save:
   • Query: Save the current Lucene or DataPrime query and dataset.
   • Fields: Save the favorite fields shown in the sidebar.
   • Table settings: Save the column layout and formatting.
6. (Optional) Enable Set as default view to make this the landing view in Explore.
7. Select Save view.

Use saved views

• 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.

The active view appears as a tab next to Explore 1 at the top of the page.

Save changes to a loaded view

Explore uses a Save changes button instead of the Update current view / Save as new view menu used in Cases and Infrastructure Explorer. The button appears in the top-right of the page when the loaded view has unsaved changes.

To save the current state as a new view, open the All views panel and select Save to open the Save View panel, then enter a new view name.

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.

In Explore, you can also select Copy URL in the top-right action bar to share the current view.

Set the team default view

Admins can set a team-level default view so every team member lands on the same Explore 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 Explore 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 enable Set as default view in the Save View panel — your personal default takes precedence over the team default.

This feature requires the EXPLORE-TEAM-DEFAULT-VIEWS:MANAGE permission, included only in the Platform Admin system role by default. Team members need EXPLORE-TEAM-DEFAULT-VIEWS:READ to see the configured team default in their own settings page.

Access policy

By default, a new saved view is Private — only you can see it. To share a view, switch the mode to Advanced and 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.
• 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; save your changes and you're done.
• Advanced — opens the full policy editor for target group rules, general access, and policy permissions. Continue with the steps that follow.

Step 3. Apply to target groups (optional)

In the Apply to target groups section, define per-group access:

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

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. Configure policy permissions (optional)

To control who can view or edit the policy configuration itself, toggle on Policy permissions. 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 6. 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

To create, view, or share saved views in Explore, your role needs the right combination of role-based permissions and policy permissions. The full list lives on the Explore permissions page; the essentials:

• View and manage shared views: EXPLORE-SAVED-VIEWS:READ, EXPLORE-SAVED-VIEWS:MANAGE
• Create and edit access policies on saved views: EXPLORE-SAVED-VIEWS:READACCESSPOLICY, EXPLORE-SAVED-VIEWS:UPDATEACCESSPOLICY
• Manage the team default view: EXPLORE-TEAM-DEFAULT-VIEWS:READ, EXPLORE-TEAM-DEFAULT-VIEWS:MANAGE
• Select target groups when building a policy: TEAM-GROUPS:READSUMMARY, TEAM-GROUPS:READCONFIG

System-wide policy overrides (access-policies:UpdateAll and access-policies:ReadAll) are not included in any out-of-the-box system role.

Related resources