> 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/product-tour/grids.md).

# Grids

Pick the grid that matches where your data comes from, then add it to a Lightning page.

GridMate grids show Salesforce records in a table with search, sorting and, in most cases, inline editing. The related list, parent related list, list view and field set grids also go past the standard Salesforce limits on columns and rows.

The grids differ mainly in **where the records come from**, so start with the table below.

## Which grid should I use?

| Grid                                                                                                | Use it when you want…                                                                                            | Good to know                                                                                                                                    |
| --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| [User Grid](https://docs.gridmate.io/product-tour/grids/user-grid.md)                               | Users to build and save their own grids with the Config Wiz, with filters, grouping, charts and formulas.        | Users need the GridMate Advanced User permission set.                                                                                           |
| [Related List Grid](https://docs.gridmate.io/product-tour/grids/related-list-grid.md)               | A record's related list, for example the Opportunities of an Account, in an editable grid.                       | Added to a record page. Works with Lookup and Master-Detail relations. It may not work on Gov Cloud: use a Field Set Grid or a User Grid there. |
| [Parent Related List Grid](https://docs.gridmate.io/product-tour/grids/parent-related-list-grid.md) | The parent record's related list on the child record page, for example the Account's Contacts on an Opportunity. | Added to a record page.                                                                                                                         |
| [List View Grid](https://docs.gridmate.io/product-tour/grids/list-view-grid.md)                     | An existing Salesforce list view as a grid, with search and inline edit.                                         | Added to an app page.                                                                                                                           |
| [Field Set Grid](https://docs.gridmate.io/product-tour/grids/field-set-grid.md)                     | To choose the columns with a field set, including parent fields, without writing formulas.                       | Can be filtered to show only the records related to the page.                                                                                   |
| [Mobile Grid](https://docs.gridmate.io/product-tour/grids/mobile-grid.md)                           | Records as touch-friendly cards in the Salesforce mobile app.                                                    | Phone only: added to App, Record and Home pages set to Phone. On desktop, use a User Grid.                                                      |
| [Apex Data Grid](https://docs.gridmate.io/product-tour/grids/apex-data-grid.md)                     | Data that does not come from a query: an external system, a callout, computed rows or aggregates.                | A developer writes a global Apex class that implements `gmpkg.IApexDataGridProvider`.                                                           |
| [Report Table](https://docs.gridmate.io/product-tour/grids/report-table.md)                         | A Salesforce report, tabular, summary or matrix, as a table.                                                     | Can be added to any Lightning page: Home, App or Record.                                                                                        |
| [Flow Grids](https://docs.gridmate.io/product-tour/grids/smart-grids-in-flows.md)                   | Users to view, select or edit a collection of records on a flow screen.                                          | Two components: GM - Flow View Grid and GM - Flow Edit Grid.                                                                                    |
| [Pivot Grid](https://docs.gridmate.io/product-tour/grids/pivot-grid-in-action.md)                   | Time series records, for example a forecast per month, summarized and editable in the cells.                     | Configured in the Lightning App Builder and the Config Wiz.                                                                                     |

## Go further

Once a grid is on your page, these Advanced Guides show what you can add to it:

* [Grid actions](https://docs.gridmate.io/advanced-guides/grid-actions.md): record, mass and custom actions.
* [Filters & data](https://docs.gridmate.io/advanced-guides/filters-and-data.md): filters, import, export and charts.
* [Grid setup](https://docs.gridmate.io/advanced-guides/grid-setup.md): the Config Wiz, the Config Checker and the Admin Cockpit.


---

# 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/product-tour/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.
