Save and reuse filtered Alert Management views to stay focused on the work that matters. A saved view in Alerts preserves the current configuration so you can return to common monitoring workflows without reapplying filters each time.

Alerts 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 saved view captures in Alerts

| Option                  | Description                                              |
| ----------------------- | -------------------------------------------------------- |
| **Query**               | The current search query and dataset.                    |
| **Filters**             | The applied filters.                                     |
| **Table settings**      | The column layout and formatting.                        |
| **Set as default view** | Makes this the default landing view in Alert Management. |

The **Time range**, **Fields**, and **Widget state** options, available in other products, do not apply in Alerts. Alert Management is time-range-insensitive: the table lists alert definitions and current status, not time-bound events.

## Create a saved view

1. Configure the Alert Management page using search, filters, 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) Enable **Set as default view** to make this the landing view in Alert Management.
1. Select **Save view**.

## Use saved views

- Saved views appear as tabs across the top of the Alert Management page, next to the page title.
- Open the **All views** panel from the left sidebar to browse all saved views.
- 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 a new view

When a loaded view has unsaved changes, the save menu provides two options:

- **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, and table settings.

## Product-specific notes

- Alerts saved views do not include **Time range**, **Fields**, or **Widget state**.
- Saved views appear as tabs across the top of the Alert Management page, with the active view name shown next to the page title.
- The save menu uses **Update current view** / **Save as new view**, the standard pattern shared with Cases and Infrastructure Explorer.

## Set the team default view

Admins can set a team-level default view so every team member lands on the same Alert Management 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 Alerts 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 enable **Set as default view** when saving — your personal default takes precedence over the team default.

This feature requires the `ALERTS-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, 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.
1. Select an access level from the action dropdown. Available options differ by resource type — for example, **Read**, **No Access**, or **Manage** for saved views.
1. Select **Apply** to commit the rule.
1. 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](https://coralogix.com/docs/user-guides/aaa/access-control/policies/index.md).

## Permissions

The following permissions govern saved views in Alerts.

| Resource                                | Required for                                                   |
| --------------------------------------- | -------------------------------------------------------------- |
| `ALERTS-SAVED-VIEWS:READ`               | Loading shared saved views in Alert Management.                |
| `ALERTS-SAVED-VIEWS:MANAGE`             | Creating, editing, and deleting shared saved views.            |
| `ALERTS-SAVED-VIEWS:READACCESSPOLICY`   | Viewing the access policy on a saved view.                     |
| `ALERTS-SAVED-VIEWS:UPDATEACCESSPOLICY` | Creating, editing, or deleting access policies on saved views. |
| `ALERTS-TEAM-DEFAULT-VIEWS:READ`        | Seeing the configured team default view in settings.           |
| `ALERTS-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-alerts) for the role assignments per key.

## Next steps

Learn how to silence noisy or expected alerts: [Alert suppression rules](https://coralogix.com/docs/user-guides/alerting/alert-suppression-rules/index.md).