> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/premium-table/working-with-premium-table/10.-variables/variable-bookmarks.md).
# Variable bookmarks
You can save the options chosen/set for the variables in a report and assign a name - similar to a bookmark. This feature enables you to switch between different configurations without having to setup each variable repeatedly.
Let's look at how to bookmark variable settings.
**STEP 1:** Assign values to each of the variables.
Assign variable values
**STEP 2:** Click the **Save Current as New View** option.
Save variable config option
**STEP 3:** Enter a name to identify the bookmark. Click the tick button to save the bookmark.
Add bookmark name
**STEP 4:** You'll see the bookmark name in the dropdown.
Bookmark saved
**STEP 5**: Let's create another bookmark for the 'South' region with a different set of variable configurations.
Creating a new variable bookmark
---
# 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.inforiver.com/premium-table/working-with-premium-table/10.-variables/variable-bookmarks.md?ask=&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.
