A deal draft saves unfinished editor work without creating a deal. Drafts belong to the original staff member and selected workspace; they are not shared deals, public notes or a new permission grant.
Watch the lesson
Save and resume
- Open the deal creation form and choose an available pipeline and stage.
- Enter the customer or organization, owner, value and other permitted details.
- Use Save draft and wait for the saved acknowledgement. The editor also attempts autosave after changes where enabled; typing or leaving a page does not guarantee the latest change reached the server.
- Choose Recover draft from the same authorized account and company. If required, use Review current context before changes are unlocked. Review restored stage, owner and relationships.
- Complete the final create action. A draft acknowledgement is not a deal creation receipt: verify the resulting deal before creating another.
The web editor retains drafts for seven days after the last change, up to thirty days total, as shown in its draft notice. An unchanged autosave can acknowledge existing work without changing the business record. Expired drafts can be pruned without deleting customer or deal records. Use discard only for unfinished editor work you no longer need.
Changed access or data
Draft submission rechecks the current subscription, capacity, field permissions, related records and original workspace. Losing permission while an editor is open can prevent a save or creation. A stored owner or stage cannot authorize a now-inaccessible relationship. Refresh the form and correct the issue; do not switch workspaces to bypass it.
Version and source checks protect against stale publication and duplicate creation. If the connection fails after a submit, check the existing draft/deal outcome before submitting a new create request. The UI should retain recoverable input after a capacity denial; an over-limit denial is not successful creation.
Performance expectations
Request-scoped permission reuse and repeated parent-proof reduction remove redundant database work while retaining fresh write checks. Work is queued through Redis where configured. These optimizations do not establish a universal response-time guarantee. The accepted local web sample was approximately 309 ms draft save, 343 ms unchanged autosave and 594 ms create, including application work; cumulative timed SQL was about 113, 131 and 279 ms respectively. These are instrumented small-fixture observations, not production p95 or a sub-100 ms SLA.
Native mobile draft behavior is documented separately in Native mobile workspace.