Setting Up a Custom View

LAST UPDATED: MAY 7, 2025

PREREQUISITE

The Enable Custom View role token must be selected.

Procedures

Creating a Simple Custom View

Drag the table's column headers into the Saved Searches field to define groupings.
Observe the number of groupings reflected in a hierarchical structure, aligned with the order in which the attributes are positioned within the Saved Searches field.
Click on the button next to the Incidents accordion.
Create the custom view.
1. Input a unique custom view name.
2. (Optional) Grants access to this custom view for other users, groups, or roles.
3. Click on the Create button.
Click the newly created the custom view to view it.

RESULT

Users can now return to this custom view from any other view.

Creating a Custom View with Predefined Sort Orders and Filters

Users can further customize their views by sorting data in ascending or descending order by table headers and applying filters.

Sorting Using Table Headers

To sort the table by a different column, click the Incident No. header until no arrow appears, then click another attribute.

If users drag a header into the Saved Searches field while sorting is applied, a Column Sorting section will appear in the Edit View popup, reflecting the applied sorting in either ascending or descending order.

Ordering Headers in the Saved Searches Field

The order of headers in the Saved Searches field determines how incidents are grouped and sorted in the table.

The leftmost header serves as the primary grouping.
Each subsequent header to the right creates nested subgroups.
The rightmost header defines the most specific sorting level within the final subgroup.

change header sorting.gif — Rearranging the sorting structure by dragging the **Status** field to the first position.

Users can modify the sorting structure by dragging headers into different positions within the Saved Searches field, ensuring the data is displayed in a way that best supports their triaging needs.

If a table header can contain repeatable values—such as Incident Type or Status (i.e., there can be many phishing-type and “Open” incidents)—users can change the sorting direction of incidents within each group (accordion) by clicking its attribute in the Saved Searches field.

showing how sorting order works with grouping hierarchy.gif — Arranging incidents in the largest accordion by Status in descending order, and then within each Status, sort the incidents by Incident Type in descending order.

Applying a Filter

Users can click the Group 42.png button on any table header to apply filters and display data matching specific incident attributes. Multiple filters can be applied across one or more table headers.

Group 58.png — A filter on the **Incident No.** table header that displays only incidents where the incident number begins with **2025**.

Group 59.png — A filter on the **Status** table header that displays only incidents with the **Open** status.

Use Case: Creating a Custom View Filtered by Data Breach Incident Type and Sorted by Incident Number

Users can save a custom view with a predefined table header sorting order and filters in the following steps:

Click an incident attribute in the table header to modify its sorting order (e.g., Incident No.).
In this example, the Incident No. column is currently sorted in descending order, with numbers decreasing sequentially.
Drag the Incident No. column header, sorted in descending order, into the Saved Searches field.
Filter a column by a specified value.
1. Click the button on the desired column header to apply a filter to it.
2. Select a value to filter by.
3. Click the Filter button.
Drag the filtered column header (e.g., Incident Type) into the Saved Searches field.
Click on the button next to the Incidents accordion to create a custom view based on the current view.
Create the custom view.
1. Input a unique custom view name.
2. (Optional) Grants access to this custom view for other users, groups, or roles.
3. Review the view details.
4. Click on the Create button.
Click the newly created the custom view to view it.

RESULT

The table data is organized by grouping Incident No. first in descending order, then by Incident Type in descending order, with a filter applied to show only Data Breach incidents.