> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/hierarchyfilter/configuration/state-persistence.md).
# State Persistence
State Persistence allows you to keep the current selection active after reloading or publishing the workbook. This makes it easy to share workbooks that are already zoomed in on aspects of the hierarchy.
To use state persistence, we first need to set up a parameter. The parameter type needs to be String.
After which you need to enable the "persist state" option in the general tab in the options page in the configuration. Here, you can select the parameter. Make sure the state persist parameter is not used elsewhere.
Click on submit to save the changes, after which your selections and open items should stay the same after reloading the extension, dashboard or workbook.
---
# 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.infotopics.com/hierarchyfilter/configuration/state-persistence.md?ask=&goal=
```
`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.