Dealflow permissions and states

Dealflow combines a rollout gate, organization membership, deal capabilities, and administrator-only settings.

Permission matrix

Action	Organization member	Organization admin
Open Deals	Yes, when dealflow_service is enabled	Yes, when dealflow_service is enabled
Search, create, and open deals	Yes	Yes
Change stage or move a Kanban card	Yes	Yes
Pass a deal and record its reason	Yes	Yes
Configure Pipeline settings	No	Yes
Configure Decision emails	No	Yes

A guest or user outside the organization is denied. The rollout can be enabled for the organization or as a per-user escape hatch; disabled routes return not found.

Stage kinds

Kind	Meaning
Active	A working pipeline stage such as New, Screening, or Diligence
Won	A successful terminal or outcome-oriented stage
Lost	An unsuccessful outcome distinct from the passed workflow
Passed	A declined opportunity; the dedicated Pass action targets the first stage of this kind

Stage names are editable and need not equal their kinds. Stage-transition history snapshots names so earlier activity remains readable after a rename or deletion.

Pass state

Pass deal requires a reason and accepts an optional revisit date. If a primary contact exists, the dialog can also offer Email the decline to name. The option is selected by default and sends an external message using the organization’s enabled decision-email template unless the user clears it.

Moving a deal out of a passed stage clears its pass reason and revisit date. The stage-transition history remains recorded.

Browser persistence

The signed-in Deals browser uses durable user preferences for:

• table or Kanban layout;
• visible table fields and column widths;
• visible Kanban card fields;
• whether empty card fields are shown.

Kanban card moves use persisted server mutations. The server validates the organization, deal, current source stage, and destination stage before writing, then reloads both table and board state. A rejected move must not be interpreted as saved.

Settings effects

Deleting a populated stage requires a Move deals to destination. Decision emails can be enabled or disabled and edited by an admin; changing Subject or body affects future sends, not earlier stage history.