For the complete documentation index, see llms.txt. This page is also available as Markdown.
Assignment and stage actions
Control who can claim, start, save, submit, reject, or move work.
Workflow actions are permissioned state transitions. Operators should see only the actions valid for their role, stage, assignment, and current task state.
Task Queue with assignment controls
Queue assignment and Workbench stage actions should express the same operating rules so users do not need side-channel coordination.
Saving and moving through the workflow are separate actions. Saving appends annotation history inside the current stage. A stage action changes the item’s route.
The Workbench header builds available actions from the current item and can show:
Send to Review or Send to <stage>;
Mark as Complete;
Reject as a danger action;
Restart Workflow for a manager viewing a Complete item;
item timeline.
Automated-stage items open read-only while the model or automation owns them. After a successful stage action, Unitlab saves dirty work, advances to the next item in the current queue/filter context, and returns to the project Datasets page with a Queue complete message when no work remains.
Use this in production
Define whether work is manually assigned, self-claimed, or automatically allocated.
Separate the ability to annotate, review, move tasks, change priority, and administer the project.
Make save, submit, reject, skip, invalid, and escalate behavior distinct.
Test unassigned, assigned-to-self, assigned-to-other, completed, and reopened states for every role.
