> 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/advanced-guides/grid-setup.md).

# Grid setup

Configure grids with the Config Wiz, check them, secure and track them in the Cockpit, explore data, or run them on Classic.

These guides cover the admin tools around your grids: generating property values, checking a configuration, managing access and User Grids, and letting users explore data.

## What's in this section?

| Guide                                                                                                            | Use it to…                                                                                                                                 | Good to know                                                                                    |
| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- |
| [Grid - Advanced Configuration](https://docs.gridmate.io/advanced-guides/grid-setup/grid-configuration.md)       | Generate smart grid property values step by step with the Config Wiz, from filters to formulas.                                            | Available only from the component's quick actions, and only to a GridMate administrator.        |
| [Grid - Config Checker](https://docs.gridmate.io/advanced-guides/grid-setup/grid-config-checker.md)              | Check GM - FieldSet Grid, GM - RelatedList Grid, GM - ListView Grid and GM - Kanban Grid configurations for missing or incorrect settings. | Enabled with **Enable Config Checker** on the grid in the App Builder.                          |
| [Grid - Admin Cockpit](https://docs.gridmate.io/advanced-guides/grid-setup/grid-admin-cockpit.md)                | Secure field and action access, maintain User Grids and filters, and track adoption in the GridMate Cockpit.                               | Requires the **GridMate Cockpit User** Permission Set. Action Access applies only to User Grid. |
| [Grid - Grid Explorer](https://docs.gridmate.io/advanced-guides/grid-setup/grid-grid-explorer.md)                | Let users filter, pick columns, sort and group grid data, and save the setup as templates.                                                 | Added to a grid with the Enable explorer option.                                                |
| [Salesforce Classic Setup](https://docs.gridmate.io/advanced-guides/grid-setup/salesforce-classic-deployment.md) | Run RelatedList and ListView grids on Salesforce Classic.                                                                                  | Only RelatedList and ListView grids are supported. Uses Lightning Out and a Visualforce page.   |

## Go further

* [User Grid](https://docs.gridmate.io/product-tour/grids/user-grid.md): create and configure your own grids from the Config Wiz.
* [Grids](https://docs.gridmate.io/product-tour/grids.md): pick the grid that matches where your data comes from.


---

# 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/advanced-guides/grid-setup.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.
