> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/workflows/assignment-and-stage-actions.md).

# Assignment and stage actions

Control human ownership, Consensus assignments, saving, submission, review decisions, and manager handoffs.

Workflow assignments define who can perform human work. Stage actions define when an item leaves its current responsibility and where it goes next. Both depend on project access, eligible members, assignment, and the current task state.

## Configure ownership

1. Select the Annotate, Review, or Consensus node in the workflow editor.
2. Configure eligible members and the assignment options supported by that stage.
3. Decide whether eligible users may self-assign, whether managers may override assignment, and whether unassigned work is visible.
4. Apply the workflow and check assigned, unassigned, and assigned-to-another-user cases with the intended roles.

Separate permission to annotate, review, reassign work, and administer workflows. A stage display name alone does not enforce separation of duties.

## Save versus submit

**Save** records annotation changes within the current stage. A workflow action sends the work onward or records a review decision. Depending on the stage and route, the Workbench can offer actions such as **Send to Review**, **Send to a named stage**, **Mark as Complete**, **Approve**, or **Reject**.

Use the action actually offered for the current item. Automated-stage ownership and inspection-only comparisons may make the Workbench read-only. Successful transitions retain the queue or filter context for navigation where supported.

## Consensus assignments

A Consensus parent item has independent vote assignments rather than one shared annotation owner. Each eligible annotator works on their own branch and submits one vote. For grouped tasks, required panels belong to that vote. The stage waits for all required votes before evaluating agreement.

Disagreement creates assigned review work. Opening the QA report's frozen comparison is an inspection action; it does not claim the review assignment. Enter the active review route to correct and approve the result. See [Consensus](https://docs.unitlab.ai/documentation/qa/consensus).

Changing Consensus eligibility affects new claims and assignments. Existing assignments and submitted votes remain intact unless an authorized manager performs the relevant explicit reassignment or workflow operation.

## Quality Gate ownership

Quality Gate evaluates on entry and routes automatically. It does not need an annotator to claim a gate task. The destination of Pass, Fail, or Not evaluated determines who owns subsequent work. See [Quality Gate](https://docs.unitlab.ai/documentation/qa/quality-gate).

## Review and correction

Approve follows the configured forward route. Reject follows the configured correction route. Provide feedback that identifies the affected label, frame, field, interval, or rule, and confirm the next stage has an eligible owner. See [Review Stages](https://docs.unitlab.ai/documentation/qa/review-stages).

## Diagnose missing actions

| Symptom                              | Check                                                                            |
| ------------------------------------ | -------------------------------------------------------------------------------- |
| Cannot claim work                    | Stage eligibility, self-assignment policy, current owner, and task availability. |
| Can inspect but cannot edit          | Inspection mode, automated ownership, active assignment, and permissions.        |
| Save works but item remains in place | Use the appropriate submission or decision action after saving.                  |
| Consensus comparison opens read-only | Enter the active vote or review assignment instead of the report-only view.      |
| Rejected item has no visible owner   | Inspect the reject destination and its assignment configuration.                 |

Use item history to confirm transitions and preserve the current assignment context during recovery. Review [Change a live workflow](https://docs.unitlab.ai/documentation/workflows/change-a-live-workflow) before changing the graph to resolve an ownership problem.