Involvement Positions & Signatures
Involvement positions replace the old flat “assignees” list with a configurable, named set of roles for each decision—think RACI, DACI, or something fully custom to your team.
Presets
Team Settings → Involvement ships four common shapes you can instantiate with one click, or you can build your own from scratch:
| Preset | Positions |
|---|---|
| RACI | Responsible, Accountable, Consulted, Informed |
| RASCI | Responsible, Accountable, Support, Consulted, Informed |
| DACI | Driver, Approver, Contributor, Informed |
| RAPID | Recommend, Agree, Perform, Input, Decide |
Custom configurations use the same building blocks—you just name and configure the positions yourself.
Position settings
Each position independently controls:
- Min / max assignees — how many people must/can hold it
- Signature quorum — how many assigned holders must sign a gated transition (default: all of them)
- Gates — whether the position must sign off before a decision can move to Approved, Rejected, and/or Implemented
- Decision-scoped permissions — View, Comment, Edit Content, Sign Approve/Reject/Implement, Manage Positions, granted only to that position’s current holders and only on decisions using that configuration (see Permissions Reference)
- Eligibility filters — restrict who is assignable: only users with a given team role, only members of the space/page, an explicit allow-list, excluding the decision’s own owner, or requiring a minimum team plan
Assigning a decision
When creating or editing a decision, pick a configuration (or leave it unset for a configuration-free decision), then assign people to each position from the picker. If a position has a minimum headcount, Publish is blocked until it’s satisfied.
Signing
Decisions with at least one gating position show a Signatures panel: one row per gating position, with live signed/required counts and a checkmark at quorum. Once every gating position for a transition reaches quorum, the status advances automatically.
Positions that don’t gate anything behave like the old assignees list: informational, with no signature requirement.
Editing configurations later
- Archive a position instead of deleting it once decisions reference it—archived positions stop accepting new assignments but keep their history.
- Deleting a whole configuration is blocked while any decision still uses it.
- Renaming a configuration happens from Team Settings → Involvement; repointing a single decision to a different configuration happens from that decision’s edit form.
Backups
Full team data backups (Data, Pro+) include involvement configurations, positions, filters, and every decision’s position assignments and signatures—restoring a backup restores the whole workflow, not just the decision text.