> 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/working-with-inforiver/3.-basic-interactions/actions.md).

# Actions

In this section, we'll look at the following:

**1. Rails** - You can enable the horizontal and vertical ruler and adjust the column width and row height of the visual. To learn more, refer to [rails](/working-with-inforiver/3.-basic-interactions/actions/rails.md).

**2. Toolbar options** - Inforiver toolbar can be minimized in the edit/read modes and customized for the reading view. To learn more, refer to [toolbar options](/working-with-inforiver/3.-basic-interactions/actions/toolbar-options.md).

**3. Keyboard shortcuts** - For a list of keyboard shortcuts that you can use to work efficiently with Inforiver, refer to [keyboard shortcuts](/working-with-inforiver/3.-basic-interactions/actions/keyboard-shortcuts.md).

**4. Reset** - Inforiver provides various reset options such as Reset formats, Reset value, Reset notes and Reset all. To learn more, refer to [reset](/working-with-inforiver/3.-basic-interactions/actions/reset.md).

**5. Context menus -** Inforiver offers a host of single-click options that can be accessed from the row and column grippers. To learn more refer to [context menus](/working-with-inforiver/3.-basic-interactions/context-menus.md).


---

# 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/working-with-inforiver/3.-basic-interactions/actions.md?ask=<question>&goal=<user_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.