> 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/analytics+/storyboard/working-with-textboxes.md). # Working with textboxes You can use text boxes in Analytics+ either to set the title or to provide contextual details in your dashboards. The **Text** tab in the toolbar holds the options for text formatting and alignment. You can also double-click and use the on-object interaction menu for basic customizations. ### 1. Setting the style You can specify whether the text is a heading, paragraph, or bullet list from the **Text Format** dropdown.

### 2. Customizing the font Select the font and size from the dropdown menus. You can also set the font style (bold, italic, underlined) by selecting the text and clicking the icons.

### 3. Assigning the font and highlight color You can set a custom font and highlight color.

### 4. Setting the alignment Set the horizontal(left, center, right) and vertical(top, center, bottom) alignment for your text.

--- # 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/analytics+/storyboard/working-with-textboxes.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.