Engage permissions and states

Engage combines a seller-workspace feature gate, organization capabilities, separation-of-duties checks, and record state. Counterparty access uses separate personal links or authenticated journeys and does not grant access to the seller workspace.

Seller-workspace capabilities

Capability	Typical organization access	What it permits
View engagements	Member	View the Pipeline and accessible engagement state.
Manage engagements	Member	Compose drafts, create and edit counter-revisions after send, refresh an initial draft from CRM, change email, and withdraw when allowed.
Send engagements	Administrator	Send, resend, remind, open signing, and perform administrator-controlled offer delivery.
Review engagement KYB	Administrator	View protected intake evidence and approve or request changes. Separation of duties applies to approval; the audited sole-operator exception is available only when no other eligible conflict-free human exists.

The seller workspace must be enabled for the organization or user. The public offer route and signed-in counterparty list are distinct journeys and do not imply seller access.

Engagement states

State	Allowed progression	Meaning
Draft	Sent or Withdrawn	Unsent reviewed offer. CRM data and email can change, but the original offer terms are not editable from seller detail.
Sent	Declined, Withdrawn, Expired, or Signed	A frozen revision is out under a personal link.
Expired	Sent by resend, or Withdrawn	Dormant but recoverable; it still holds the opportunity slot.
Signed	Activated or Withdrawn	Both signatures completed; gates remain before activation.
Declined	None	Terminal counterparty decision.
Withdrawn	None	Terminal seller decision.
Activated	None	Terminal success; the opportunity slot is free.

Revision states

An engagement can have multiple offer revisions.

Revision state	Progression	Mutability
Draft	Sent	Editable in the composer before initial creation, or in the counter-revision panel after a sent offer. The saved initial draft detail has no offer-term editor.
Sent	Superseded, Signed, or Declined	Frozen; later negotiation creates another revision.
Superseded	None	Historical prior offer.
Signed	None	The signed commercial basis.
Declined	None	Terminal for that revision.

The engagement status governs the overall lifecycle; a revision does not mirror every engagement terminal state.

Derived pipeline stages

Pipeline stages are Opportunity, Sent, Viewed, Negotiating, Partially signed, Signed, KYB pending, Activated, Expired, and Declined / withdrawn. Viewing, negotiation, signature progress, KYB, and Billing state contribute to the derived stage without adding ad hoc engagement statuses.

Signing and approval controls

• The counterparty signs before the selected seller signatory countersigns.
• The seller signatory should differ from the sender; a sole-operator exception is recorded.
• KYB answers and files are visible only to the signer account and authorized reviewers.
• KYB approval requires independence from the engagement creator, sender, and term grantors while another eligible conflict-free human exists. If none exists, Engage permits and audit-logs the sole-operator exception. Viewing evidence and requesting changes use the review capability but do not apply that approval-only conflict check.
• Activation requires Signed, any applicable KYB approval, a linked Billing contract, approved Billing discounts, and an eligible Draft or Active contract.

Offer links expire after 60 days. Sending, resending, or sending a reminder mints a new link and supersedes the prior URL for future loads.

Entity Browser saved state and mutations

The Pipeline’s search, filters, progress-stage selection, sorting, and shareable query are URL-backed. Table or kanban layout, visible table fields, column widths, visible card fields, and whether empty card fields appear are personal preferences for the Pipeline browser.

The kanban is read-only. Moving a card cannot mutate an engagement because columns are derived from authoritative records. Resend, Remind, and Withdraw are explicit, capability-checked commands. After an action, Engage recomputes canonical stage data; a saved view or shared URL never carries someone else’s authority or lifecycle decision.

For procedures, see Create and send an engagement and Manage negotiation, signing, KYB, and activation.