Controlled actions
How approved connections can create or change work without removing the firm’s ownership of consequential actions.
On this page
Before you start
- Explicit approval for every creation or update capability.
Typical workflow
- 1
Define the exact allowed action.
- 2
Preserve review or confirmation for consequential work.
- 3
Test repeated events and retries.
- 4
Monitor duplicates and unexpected changes.
Narrowly approved changes
A connection can perform only the creation or update behavior approved for its use case and enabled for the participating firm.
Confirmation boundaries
Sensitive sends, signatures, financial activity, file saves, and other consequential actions may remain staged for review or require an explicit person-driven confirmation.
Repeat-safe design
Approved workflows are planned so a retry or repeated source event does not quietly create duplicate or contradictory work.
Keep in mind
- Sends, signatures, financial activity, file saves, and other consequential actions may require an explicit confirmation path.
Still need help with this guide?Contact PlaintiffDesk