> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/package-reference/components-library/grids.md).

# Grids

Grid components for record, app and home pages, from related lists, list views, field sets, User Grids, Apex or reports.

| Component                                                                                                                         | Description                                                         |
| --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| [GM - RelatedList Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-relatedlist-grid.md)               | Display and edit the records of a related list on a record page.    |
| [GM - FieldSet Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-fieldset-grid.md)                     | Display and edit records using a field set to define the columns.   |
| [GM - ListView Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-listview-grid.md)                     | Display and edit the records of a list view.                        |
| [GM - User Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-user-grid.md)                             | Display a grid configured by the end user from the grid wizard.     |
| [GM - Mobile Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-mobile-grid.md)                         | Touch-first grid for the Salesforce mobile app, records as cards.   |
| [GM - Parent RelatedList Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-parent-relatedlist-grid.md) | Display a related list of a parent record on the child record page. |
| [GM - Apex Data Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-apex-data-grid.md)                   | Display the rows returned by your own Apex class.                   |
| [GM - Report Table](https://docs.gridmate.io/package-reference/components-library/grids/gm-report-table.md)                       | Display a Salesforce report as a table.                             |
| [GM - User Grid Split View](https://docs.gridmate.io/package-reference/components-library/grids/gm-user-grid-split-view.md)       | Browse and open User Grids from a split view list.                  |
| [GM - Grid Dashboard](https://docs.gridmate.io/package-reference/components-library/grids/gm-grid-dashboard.md)                   | List of KPI tiles, one per User Grid, showing the record count.     |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gridmate.io/package-reference/components-library/grids.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
