> 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-actions/grid-apply-and-save.md).

# Grid - Apply & Save

Let users choose to save grid column, sort, filter and group-by changes permanently.

## Apply & Save Setup

To allow users to permanently save their grid configurations, follow these steps:

{% stepper %}
{% step %}

### Open Custom Settings

Go to **Setup**, type **Custom Settings** in the Quick Find box.
{% endstep %}

{% step %}

### Manage DataGrid Settings

Click **Manage** next to **DataGrid Settings**.
{% endstep %}

{% step %}

### Configure the options

Check the following boxes:

* Apply & Save **Columns**
* Apply & Save **Sorting**
* Apply & Save **Filters**
* Apply & Save **GroupBy**
  {% endstep %}

{% step %}

### Save

Click **Save** to apply the changes.
{% endstep %}
{% endstepper %}

Once this configuration is activated, users will be able to use the **Apply & Save** feature.

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2FBHGXsvAt1jNy5r9cevlE%2FScreenshot%202026-02-13%20at%2009.56.07.png?alt=media&amp;token=34e9396e-8b79-403a-b101-b01dcc5bf523" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2F7uMgAh3KCHv6G7l6puxQ%2FScreenshot%202026-02-13%20at%2009.56.59.png?alt=media&amp;token=b9434de6-b173-47f2-a7e4-d803d88c86d4" alt=""><figcaption></figcaption></figure>

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Grid - Grid Explorer</strong></td><td>Filter, pick columns, sort and group grid data, and save templates.</td><td><a href="/advanced-guides/grid-setup/grid-grid-explorer.md">Grid - Grid Explorer</a></td></tr><tr><td><strong>DataGrid Settings</strong></td><td>Set org-wide grid behavior per profile or user.</td><td><a href="/package-reference/grids-settings.md">DataGrid Settings</a></td></tr><tr><td><strong>Grid - Advanced Configuration</strong></td><td>Generate smart grid property values step by step with the Config Wiz.</td><td><a href="/advanced-guides/grid-setup/grid-configuration.md">Grid - Advanced Configuration</a></td></tr></tbody></table>

## Apply & Save Demo

Once **Apply & Save** is enabled, users can choose whether their grid changes are temporary or permanently saved.

The video below provides a step-by-step tutorial on how to use **Apply & Save** 👇

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


---

# 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-actions/grid-apply-and-save.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.