> 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/master.md).

# What is GridMate

Grids, Kanban boards, calendars, maps and file explorers for your Salesforce Lightning pages, set up without code.

<a href="/getting-started/quickstart.md" class="button primary" data-icon="rocket">Quickstart</a> <a href="/getting-started/installation-procedure.md" class="button secondary" data-icon="box-open">Package Setup</a>

GridMate components can be tailored to suit the requirements of the end-user to enhance and improve their user experience and productivity. We provide a set of components and quick actions for the end-user to manipulate and process the data, these include CRUD operations, inline editing, filtering, sorting, data import/export, flows...

Please check out the video below to have an overall idea👇🏻

{% embed url="<https://youtu.be/O-aqEKx7rxM>" %}

GridMate leverages org. metadata to display data from **related lists**, **list views,** **field sets** and **quick actions** from both standard and custom objects.

GridMate components can be added to your lightning pages(**Home**, **App**, **Record**) using the Lightning App Builder.

## How do you want to work?

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-table-columns" style="color:$primary;">:table-columns:</i></h3></td><td><strong>In the Lightning App Builder</strong></td><td>Drop a GM component on a Home, App or Record page and set its properties.</td><td><a href="/product-tour/grids/related-list-grid.md">Related List Grid</a></td></tr><tr><td><h3><i class="fa-wand-magic-sparkles" style="color:$primary;">:wand-magic-sparkles:</i></h3></td><td><strong>With Config Wiz</strong></td><td>Build User Grids, User Kanban Boards and calendars from records.</td><td><a href="/product-tour/grids/user-grid.md">User Grid</a></td></tr><tr><td><h3><i class="fa-terminal" style="color:$primary;">:terminal:</i></h3></td><td><strong>With the CLI and Chrome extension</strong></td><td>Move grid configurations between orgs and inspect them in the browser.</td><td><a href="/tools/sf-cli-plugin.md">SF Cli Plugin</a></td></tr></tbody></table>

## Explore the components

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-table" style="color:$primary;">:table:</i></h3></td><td><strong>Grids</strong></td><td>Related list, list view, field set, user, mobile and Apex grids.</td><td><a href="/product-tour/grids/related-list-grid.md">Related List Grid</a></td></tr><tr><td><h3><i class="fa-columns" style="color:$primary;">:columns:</i></h3></td><td><strong>Kanban</strong></td><td>Drag-and-drop boards by stage.</td><td><a href="/product-tour/kanban/kanban-board.md">Kanban Board</a></td></tr><tr><td><h3><i class="fa-calendar" style="color:$primary;">:calendar:</i></h3></td><td><strong>Calendars &#x26; timelines</strong></td><td>Multi, single, compact and end-user calendars, and the Gantt Chart.</td><td><a href="/product-tour/calendars-and-timelines/multi-calendar-in-action.md">Multi Calendar</a></td></tr><tr><td><h3><i class="fa-map" style="color:$primary;">:map:</i></h3></td><td><strong>Maps</strong></td><td>Show one record or a whole list on a map.</td><td><a href="/product-tour/maps/map-list.md">Map List</a></td></tr><tr><td><h3><i class="fa-folder-open" style="color:$primary;">:folder-open:</i></h3></td><td><strong>Files</strong></td><td>Browse, upload and connect files and folders.</td><td><a href="/product-tour/file-explorer.md">File Explorer</a></td></tr><tr><td><h3><i class="fa-book" style="color:$primary;">:book:</i></h3></td><td><strong>Components Library</strong></td><td>Every GM component and its properties.</td><td><a href="/package-reference/components-library.md">Components Library</a></td></tr></tbody></table>

## Keep going

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-newspaper" style="color:$primary;">:newspaper:</i></h3></td><td><strong>Release Notes</strong></td><td>What changed in each GridMate release.</td><td><a href="/release-notes.md">Release Notes</a></td></tr><tr><td><h3><i class="fa-circle-question" style="color:$primary;">:circle-question:</i></h3></td><td><strong>FAQ</strong></td><td>Answers to the questions admins ask most.</td><td><a href="/troubleshooting/faq.md">FAQ</a></td></tr><tr><td><h3><i class="fa-code" style="color:$primary;">:code:</i></h3></td><td><strong>Config Snippets</strong></td><td>Copy-paste JSON for layouts and inline components.</td><td><a href="/package-reference/config-samples.md">Config Snippets</a></td></tr></tbody></table>


---

# 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/master.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.