# User Grid - Split View

GridMate provides the **Grid - User Grid Split View** component to assist users in achieving a clearer view of the User Grids and facilitating easier grids management.

In this tutorial, we will configure **Grid - User Grid Split View** component by showing how to Create a new Lightning page, and add the component to a lightning page.&#x20;

1. Create new Lightning pages in the Lightning App Builder.
2. From components list, drag and drop the component **Grid - User Grid Split View**.
3. The grid component is now ready for configuration in the Lightning App Builder.
4. The property values can be configured to tailor the data grid to the needs of the end-user.
5. To perform a quick configuration, populate the properties below:&#x20;
   * Target Object : **Opportunity**
   * Default Grid : **Pipeline\_Opportunity Grid\_9cv0w**
   * List Label : **User Grid**
   * Grid Filter : `{ "Name": { "operator": "in", "value": "('GM Opportunity Grid','Pipeline Opportunity Grid')" } }`
   * View Height : **9999**

{% hint style="info" %}
Specifying the **Target Object** is optional.
{% endhint %}

{% hint style="info" %}
The **Grid Filter** adds a second layer of filtering, applied after the initial **Target Object** filter.
{% endhint %}

## Grid - User Grid Split View Setup

Below is a step by step tutorial to configure the **Grid - User Grid Split View** component.

{% embed url="<https://youtu.be/OS5A2PAIIkc>" %}
Grid - User Grid Split View
{% endembed %}


---

# Agent Instructions: 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://docs.gridmate.io/advanced-guides/user-grid-split-view.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.
