> 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/administration-and-setup/settings/document-processing/module/workflow-builder.md).

# Workflow Builder

### Overview

The **Workflow Builder** setting activates **DocFlow** for your organization. DocFlow is the workflow engine that automates what happens to your documents — routing, approval steps, conditions and follow-up actions. When this setting is enabled, the DocFlow workflow designer becomes available and documents start flowing through the workflows you build.

This is a **subscription-based** feature and is **disabled by default**.

### What Does It Do?

Turning the toggle on does not just flip a switch — it starts a **DocFlow subscription**. A dialog appears where you choose your DocFlow plan (DocFlow Standard, and optionally DocFlow Advanced). The setting is only activated after the subscription is confirmed.

* **Enabled** — DocFlow is activated for the organization. Documents are routed through your workflows and the Workflow Builder designer is available to create and edit them.
* **Disabled** — DocFlow is switched off and the related subscription is cancelled. Documents no longer run through workflows.

{% hint style="info" %}
**Workflow Builder is the master switch that turns DocFlow on or off for the whole organization.** Because it manages a subscription, enabling it opens a plan-selection dialog, and disabling it cancels the active DocFlow subscription.
{% endhint %}

### Benefits

* **Automation**: Replace manual handovers with automated steps (routing, approvals, conditions).
* **Consistency**: Every document follows the same defined process.
* **Visibility**: Workflows are designed and managed in one place.

### How to Use

1. Go to **Settings**.
2. Select **Document Processing**.
3. Select **Module**.
4. Open the **Document Type** section.
5. Find **Workflow Builder** and switch the toggle on.
6. In the dialog, choose your DocFlow plan (Standard, optionally Advanced) and confirm. DocFlow is activated once the subscription is created.
7. Afterwards, design your document workflows in DocFlow — see the [Workflow](/administration-and-setup/workflow.md) section for how to build them.

### When to Use This Feature

* **Automated document processes**: When documents need to move through defined steps such as review, approval or routing.
* **Team workflows**: When several people or roles are involved in handling a document.
* **Leave it off** if your organization does not use DocFlow / document workflows (turning it off also cancels the DocFlow subscription).


---

# 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/administration-and-setup/settings/document-processing/module/workflow-builder.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.