> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/administration/portal-settings/filtering-sorting-and-saving-views-in-equipme.md).

# Filtering, Sorting & Saving Views in Equipme

The grid view is a powerful feature across the equipme platform that helps you **filter**, **sort**, and **save custom views** of your data. This guide uses the **Service Portfolio** as an example, but the same principles apply in other areas like **Customers**, **Add-ons**, or **Basic Services**.

Once you understand how the grid works in one area, you can confidently use it anywhere in the system.

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

### What is the Grid View? <a href="#ispasted" id="ispasted"></a>

The grid shows records (like services, customers, or products) in a table format. Each **row** represents one item, and each **column** shows a specific data point (like Name, Type, Active Status, or Last Order Date).

You can customize what you see, filter for specific data, and even save these settings for later.

### How to Use Filters <a href="#ispasted" id="ispasted"></a>

Filters help you narrow down what you see in the grid. For example, you might want to only see services that are **System Products**.

#### Example: Filtering for System Products

1. Click the **three vertical dots** (⋮) in the "System product" column.
2. A menu will pop up with filtering options.
3. Under **Boolean filter**, you’ll see:
   * ☑️ **True** = This means the service *is* a System Product
   * ☑️ **False** = This means the service *is not* a System Product

Select **True** to see only System Products, then click **Apply**.

This method works the same way in the **Customers** grid or any other module where filtering is available.

<figure><img src="/files/8DCidS7NfKzWGhrf0QKT" alt=""><figcaption></figcaption></figure>

Select **True** to see only System Products, then click **Apply**.

This method works the same way in the **Customers** grid or any other module where filtering is available.

<br>

### Saving Custom Views <a href="#ispasted" id="ispasted"></a>

After applying filters (like System Product = True), you can save this setup as a **View** to quickly access it later.

#### How to Save a View

There are two ways to save a custom view:

**Option 1 – Top Right View Manager**

1. Click the **Views** icon:  (far right in the top corner next to the reload and visibility icons)
2. Click the **+ button** to create a new view.
3. Give your view a name (e.g., "Only System Products")
4. Click **Save**

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

**Option 2 – View Tabs Above the Grid**

1. After applying your filter(s), click the **+ icon** that appears above the grid, next to existing view tabs.
2. A new tab will appear; name it accordingly (e.g., "System Products").
3. This tab is now a saved view you can return to anytime.

   [![](https://media1-production-mightynetworks.imgix.net/asset/7384dd73-e5fc-40d5-87bc-ded52cddd787/1753850109898.png?ixlib=rails-4.3.1\&fm=jpg\&q=75\&auto=format)](https://media1-production-mightynetworks.imgix.net/asset/7384dd73-e5fc-40d5-87bc-ded52cddd787/1753850109898.png?ixlib=rails-4.3.1\&fm=jpg\&q=75\&auto=format)

This functionality is consistent across all grid-based modules (e.g., Customers, Services, Add-ons).

#### Deleting Views

To remove a view you no longer need:

* Click the **Views** icon&#x20;
* Hover over the view name and click the **trash can icon** 🗑️

<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:

```
GET https://hub.equipme.io/documentation/administration/portal-settings/filtering-sorting-and-saving-views-in-equipme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
