> 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/advanced-functions-and-tools/docbits-operator.md).

# DocBits Operator

DocBits Operator performs tasks from user instructions. An instruction describes the steps, while variables supply the data required for a particular run.

## Enable and open

1. Open **Settings → Module → Document Integration**.
2. Scroll to **DocBits Operator** and enable the feature if you have the required permissions.
3. Open **DocBits Operator** from the application's main navigation.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-35f6ec5d4f04d616379ee17325de744a086ff3e2%2Fsite-extra-modules-document-integration-en.png?alt=media" alt="Document-integration modules: scripts, document scanning, barcode extraction and custom master data."><figcaption><p>Document-integration modules: scripts, document scanning, barcode extraction and custom master data.</p></figcaption></figure>

## Enter an instruction

Use the input at the bottom of the screen to describe the expected result and the steps to take. Write variables in braces, such as `{invoice_number}` or `{url}`. The gear button opens the window for defining variable names and values.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-7574959c51de48e79bc02c2c9103813089122023%2Fsite-extra-docbits-operator-en.png?alt=media" alt="English DocBits Operator interface with an empty instruction field. No task was started."><figcaption><p>English DocBits Operator interface with an empty instruction field. No task was started.</p></figcaption></figure>

The arrow starts execution. The download icon opens the prompt-saving dialog, and the trash icon clears the conversation. Opening the save dialog does not save a template.

See the [prompt-writing guide](https://docs.docbits.com/advanced-functions-and-tools/docbits-operator/prompt-writing-guide.md) for examples.

## Save an instruction

Enter a **prompt name** in the save dialog. The public-sharing option controls sharing of the template. When preparing a shared template, use variable names in the instruction and supply the values required for each run before execution.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-27af3af2c0f5bbbe866823699faa3c946cbff786%2Fsite-extra-operator-prompt-dialog-en.png?alt=media" alt="Empty English prompt-saving dialog. No values were entered and the final Save button was not clicked."><figcaption><p>Empty English prompt-saving dialog. No values were entered and the final Save button was not clicked.</p></figcaption></figure>

When enabled, the variable-editing button opens the variable definitions. The save button saves the template. Use the cross in the upper-right corner to close the dialog without saving.

In the illustrated version, **Cancel** closes this dialog without saving. **Edit Variables** can be disabled for an empty prompt; enter the intended instruction and variables before using it.

## Saved instructions

The menu in the upper-right corner opens the saved-prompt sidebar. It has separate sections for organization and public prompts, together with search by name.

Organization prompts have run, edit and delete icons. In the public section, the arrow runs the selected template. Supply its variable values before running it.

## Execution controls

During execution you can pause, resume, cancel or take control. Pausing stops further steps while you inspect the current state. Resuming continues the work; cancelling ends the run. Taking control lets you interact manually with the browser view.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-037d8c794a9d656a01cd0ec2144a283f6a75ab5e%2Fimage%20(4).png?alt=media" alt="Example resume and stop icons."><figcaption><p>Example resume and stop icons.</p></figcaption></figure>

## Detail view

The expand button opens the execution detail view. Use it to follow the actions, current step and Operator messages, and to access the execution controls.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-f88fe211a693da415dd4a9e9ddb20e9a16e6b569%2FDetailed%20view%20.jpg?alt=media&amp;token=3c029715-ee39-4063-9a59-9d943aa86cca" alt="Expand icon for the detail view."><figcaption><p>Expand icon for the detail view.</p></figcaption></figure>


---

# 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/advanced-functions-and-tools/docbits-operator.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.
