> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/generate-reports/reports-saving.md).

# Save reports

## Save (memorize) basic column layouts, settings, and record limits

If you change a report's basic column layout, settings, or record limits, you can save (memorize) these preferences by clicking the small **Memorize** button under **List Options**. When you are prompted to select what you want to memorize, select **Layout, Settings**, or **Rec. Limit** and click **Save**.

<div align="left"><img src="/files/ryix8GwlFFH78n3TYkBu" alt=""></div>

{% hint style="info" %}
If you want to save report filter selections or column groupings, you must save the report as a custom report by clicking the large **Memorize** button under **Memorize**.
{% endhint %}

## Save (memorize) reports as custom reports

If you want to save the filters that you selected when you generated a report, or more complex layouts like column groupings, you need to save (memorize) the report as a custom report.

You can save a report as a custom report by clicking the large **Memorize** button under **Memorize**. When you are prompted to enter a **File name**, enter a unique name for the report, e.g., Detailed Sales Report Grouped by Department. It is best practice to save the custom report to the **Memorized** folder, because reports saved under other folders may be overwritten when RMH is upgraded.

<div align="left"><img src="/files/gReMgRNpBaVOB7yOk425" alt=""></div>


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rmhpos.com/store-manager/generate-reports/reports-saving.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
