> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/getting-started/fundamentals/investigate/saved-views.md).

# Saved Views

Save and reuse your personalized issue list configurations with Saved Views. Create views with specific filters, sorting, grouping, column arrangements, and search queries to quickly access the issues that matter most to your workflow.

{% @arcade/embed url="<https://app.arcade.software/share/boxB31I3fQYqfzLDDzKR/mXrMrqVy0isIIGd8naVC>" flowId="boxB31I3fQYqfzLDDzKR" %}

***

## Default Views

When your domain is first enrolled in Material, six default views available to help you get started. These domain-level views provide quick access to common issue categories and workflows.

<figure><img src="/files/uZXUKDRu43GvRhSx93S4" alt=""><figcaption></figcaption></figure>

Default views are created at the tenant level.

* All tenant admins can access them
* To create, edit, or delete, users need one of the roles highlighted in [admin roles here](/learn-more/administration/admin-roles/permissions-matrices.md#issues)
* Changes to default views affect all admins (any change you save to a default view is saved for everyone)

### Customizing Default Views

If a default view doesn't match your workflow, you have two options:

1\. Modify the default view directly (affects all admins in your tenant)

2\. Duplicate the view then customize your new copy as a [saved view](#saved-views)

{% hint style="success" %}
We recommend duplicating views for personal modifications to preserve the original defaults for your team.
{% endhint %}

***

## Saved Views

#### Visibility Types

There are two view visibility types:

* **Private View:** Only you can see and manage this view
* **Shared View**: All admins in your domain can see and manage this view

The visibility type is indicated on the top right:

<figure><img src="/files/uFeFpuu1VyoW7vWWnSeg" alt="" width="152"><figcaption></figcaption></figure>

You'll choose the view type when you create a new view. You can also convert the view type by editing it.

### Create a new Saved View

You have two options for creating a saved view: create from scratch or duplicate then edit an existing view.

<details>

<summary>How to to build a brand new view</summary>

1. From the left navigation, click **Issues**.
2. Configure your view with your desired settings:

   1. Apply **filters** using the filter panel
   2. **Sort** columns by clicking column headers
   3. **Group** issues using the group by dropdown
   4. **Show/hide** columns via the column visibility menu
   5. Enter **search** terms in the search bar

   Note: Currently, column order isn't saved in views. Stay tuned! Updates are announced regularly in [What's New](/whats-new.md).
3. Once your view is configured, from the top-right corner, click **Create View:**

   <figure><img src="/files/NBKhDBK7ucJyJlxyWpRu" alt="" width="375"><figcaption></figcaption></figure>
4. In the dialog that appears:

   1. Enter a descriptive name for your view
   2. Choose the visibility setting:
      1. **Private:** Only you can see and manage this view
      2. **Shared:** All admins in your domain can see and manage this view

   <div align="center"><figure><img src="/files/5kFFiVYeiQCt1Q0IZm70" alt="" width="375"><figcaption></figcaption></figure></div>
5. Click **Create View**.

</details>

<details>

<summary>How to build a view from an existing view</summary>

1. Open the **view** you want to duplicate.
2. Click the **ellipsis (three-dot menu ⋯)** on the top-right corner of the issues list.
3. Select **Duplicate View:**

   <div align="left"><figure><img src="/files/N6njUb7UNWa5wxPC4rG1" alt="" width="159"><figcaption></figcaption></figure></div>
4. A new dialog appears with the view's configuration:
   1. Enter a **new name** for the duplicated view
   2. Choose the **visibility** setting (private or shared)
5. Click **Create View**.

The new view is created with all the same settings as the original. You can then modify it independently without affecting the original view.

</details>

All your current settings are preserved and automatically applied when you select this view.

{% hint style="info" %}
**Saved View Location**

Once you create a new view, it's saved and appears in the left navigation **under** the default views. There's no maximum number, so create as many views as you need, but name wisely so you can find them easily.
{% endhint %}

### Update an Existing Saved View

{% hint style="warning" %}
**Updates affect all admins**

If you update a Shared view, your changes will affect all admins in your tenant who use this view. Exercise caution when modifying shared views.
{% endhint %}

When you modify settings while viewing a Saved View, Material tracks these changes as **unsaved changes.**

#### Update Customization (Filters, etc.)

1. Make any desired changes to your view settings (filters, sorting, etc.).
2. An indicator doc appears next to the view type indicating there are unsaved changes:

   <figure><img src="/files/mqEHLeHEGRlNjISJlp8c" alt="" width="236"><figcaption></figcaption></figure>
3. Click the **(ellipsis** **three-dot ⋯)** **menu** in the top-right corner of the issues list.
4. Click **Update View:**

   <figure><img src="/files/esG5ixNRxpYsvyTsVapI" alt="" width="169"><figcaption></figcaption></figure>
5. Confirm the update in the dialog that appears.

The view is immediately updated with your current settings. For shared views, other admins will see the changes the next time they open this saved view.

#### Update the title or change visibility

Need to update the view title or convert your view form private to shared or vice versa?

1. Navigate to the view you want to update.
2. Click the **(ellipsis** **three-dot ⋯)** **menu** in the top-right corner of the issues list.
3. Click **Edit:**

   <figure><img src="/files/zUN1paKGTphx00EQJ2T2" alt="" width="169"><figcaption></figcaption></figure>
4. Update the title and/or change the visibilty type.
5. Click **Save**.

### Delete a Saved View

{% hint style="warning" %}
**Deleting Shared Views**

If you delete a shared view, it's **removed for all admins** in your tenant. This action can't be undone.
{% endhint %}

When you delete a view, it's **permanently** removed from your Saved Views list.

1. Navigate to the view you want to update.
2. Click the **(ellipsis** **three-dot ⋯)** **menu** in the top-right corner of the issues list.
3. Click **Delete**.

***

#### Use Quick Commands

Quickly access Saved View actions using the All actions menu:

* First open a view, then use the keyboard shortcut `⌘K`

<figure><img src="/files/DtyNliJYrd1ruPugyPqi" alt="" width="375"><figcaption></figcaption></figure>

From this menu you can:

* **Update View**: Save current changes to the view (only appears when there are unsaved changes)
* **Edit View**: Open the settings dialog to change name or visibility
* **Duplicate View**: Create a copy of the current view
* **Delete View**: Permanently remove the view

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.material.security/getting-started/fundamentals/investigate/saved-views.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.