> 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-types/text.md).
# Text
You can use the text variables to pass custom text to the visual.
### 1. Configuration
This section outlines configurations specific to text variables.
**1.1. Value:** Assign a default value for the text variable.
Text variable configuration
### 2. Examples
**2.1. Set custom text in the header/footer**
**STEP 1:** Create a text variable with the configuration shown below.
Text variable configuration
**STEP 2:** Insert the text variable in the header - navigate to the Header\&Footer ribbon > Insert > Variables > select the variable to use.
Inserting a text variable in the header
**STEP 3:** Notice how the summary in the header changes as we update the text in the variable.
Using text variables in headers
---
# 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-types/text.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.
