> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/validation-screen/keyboard-shortcuts.md). # Keyboard Shortcuts ### Field Validation Shortcuts When working within the field validation section, users can utilize these shortcuts: * **Enter** – Moves the cursor to the next field in the validation sequence. * **Tab** – Validates the current field and automatically jumps to the next field that requires validation, skipping already validated fields. * **ESC** - Takes you back to the Dashboard. * **Control + K** – Opens the keyboard shortcut menu specific to the field validation section. * **Control + H** – Opens the documentation page for more information and assistance. * **Space** – Toggles a checkbox selection, allowing users to quickly mark or unmark options. * **Control + G / Alt + G** – Moves the focus to the next group of related fields, helping navigate structured input sections efficiently. * **Control + F** – Moves the cursor to the first field in the first group, allowing users to quickly return to the beginning of a form. * **Control + S / Alt + S** – Saves the document, ensuring all entered data is stored. * **Options + R / Alt + R** – Rejects the document, marking it as invalid or requiring further review. * **Control + T / Alt + T** – Jumps directly to the table section of the document. * **Control + plus (+) / Alt + plus (+)** Creates a new Table Line. --- # 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.docbits.com/end-user-and-partner-section/end-user-section/validation-screen/keyboard-shortcuts.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.