> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insight.nobly.dk/llms.txt
> Use this file to discover all available pages before exploring further.
# Configure a contract review workflow
> Build a document workflow with two decisions, restrict task access, publish it, and verify the resulting instance.
## What you will build
A contract enters **Review contract**. A member of **Contract reviewers** chooses **Approve** or **Return for correction**. Each choice reaches a different terminal node. Approve requires a review note, which becomes an instance variable.
This first version records a decision; it does not change a document keyword. Add that side effect only after the task flow works.
## Prepare the configuration
You need `workflow-engine.manage`, an available **Contract** document type, and a **Contract reviewers** user group. Use a test document and two accounts: one in the review group and one outside it. The workflow's service identity must have the content access required by any actions you later add.
## Create the definition and nodes
1. Open **Settings → Admin → Workflow → Workflow Designer**.
2. Set **Name** to `Contract review`, choose **Document**, and select the Contract document type. Keep the generated identifier stable after the first save.
3. Add three nodes named **Review contract**, **Approved**, and **Needs correction**.
4. Set Review contract as the **Initial node**. Turn on **Terminal** for Approved and Needs correction.
5. Leave event triggers empty for the first test. This keeps the definition available for a deliberate manual start instead of starting it for every new contract.
## Configure the two decisions
Draw a transition from Review contract to each terminal node. Select each edge and configure:
| Setting | Approve transition | Return transition |
| ----------------- | ------------------ | --------------------- |
| Kind | Task | Task |
| Label | Approve | Return for correction |
| Style | Primary | Critical |
| Visible to groups | Contract reviewers | Contract reviewers |
| Target | Approved | Needs correction |
For Approve, add an input named `reviewNote`, with label **Review note**, type **Text**, and **Required** enabled. The input name identifies the instance variable; the label is what the person completing the task reads.
Do not leave **Visible to groups** empty unless all otherwise eligible users should be able to act. A task group assignment does not grant document access by itself.
## Validate, save, and publish
Choose **Validate**, resolve errors, then **Save draft**. Check that there are no unsaved changes before choosing **Publish**. Add a release note describing the initial manual review process.
Publishing makes this version available to callers. It does not start an instance by itself. Start it for the test document from the instance administration controls, or expose it through a [document workflow action](/client-administration/defaults-and-actions#configure-document-actions).
## Verify the whole path
| Test | Expected outcome |
| -------------------------------------------- | ------------------------------------------------------------------------ |
| Start the workflow for the test contract | One instance waits at Review contract |
| Sign in outside Contract reviewers | The review task is unavailable |
| Choose Approve without a note | Required-input validation prevents completion |
| Enter a note and approve | Instance completes at Approved; `reviewNote` is present in its variables |
| Start a separate test instance and return it | Instance completes at Needs correction |
Use [instance history](/workflows/monitoring) to check the transition and final state. A terminal node means this workflow run is finished; the node's name alone does not update the document's business status.
## Add automation in a second version
After verifying the manual path, choose what should change:
* To write the decision into metadata, add a keyword action to the transition or terminal node. Confirm the keyword belongs to Contract and verify the stored value after completion.
* To start automatically on upload, add a `document.created` trigger. Check the document-type scope and optional event filter before publishing; an unrestricted trigger applies to every matching event in scope.
* To escalate overdue work, add a Timer transition to a **different** escalation node. Use an ISO-8601 duration such as `P2D`, and decide whether the escalation creates another task, sends a message, or both.
Existing running instances do not become a test of the newly published version. Start a fresh representative instance and confirm its version in history.
## Where to read next
Create, edit, validate, and publish workflow definitions in the visual designer — nodes, transitions, triggers, and versioning.