Workflow States

When workflow is enabled on a project, submissions follow a state machine with defined transitions and permission gates.

States

Status	Description
`draft`	Initial state. Fields are editable.
`submitted`	Submitted for review. Fields locked (read-only).
`under_review`	Being reviewed by a manager. Fields locked.
`approved`	Approved. Fields locked.
`rejected`	Rejected. Fields locked.

Transition Diagram

draft ──────► submitted ──────► under_review
  ▲               │                  │
  │               │                  │
  │               ▼                  ▼
  │◄──── rejected     approved ────►│
  │                                  │
  └──────────────────────────────────┘

Allowed Transitions

From	To	Required Permission
`draft`	`submitted`	`can_edit` (own) or `can_edit_all`
`submitted`	`under_review`	`can_manage`
`submitted`	`approved`	`can_manage`
`submitted`	`rejected`	`can_manage`
`submitted`	`draft`	`can_edit` (own) or `can_edit_all`
`under_review`	`approved`	`can_manage`
`under_review`	`rejected`	`can_manage`
`under_review`	`submitted`	`can_manage`
`approved`	`draft`	`can_manage`
`rejected`	`draft`	`can_manage`

Field Editing

When workflow is enabled, fields can only be edited in draft status. Transitioning back to draft from any other state re-enables editing.

Notifications

When enabled on the project, workflow transitions trigger email notifications:

Submission → under_review/approved/rejected: notifies the submission creator
Draft → submitted: notifies all partition managers (can_manage = true)