Setup checklist: preserve commitments before removing access
Identify open tasks, active relationships and configuration responsibilities before a colleague leaves. Assign receiving owners and make the context recoverable. Capsule’s task documentation describes reassignment behavior, but do not assume every record type or connected service follows the same rule. Verify the actual scope. Removing access is important, yet it should not leave customer promises orphaned or make the team depend on the departing person’s private memory to understand current work.
Use a bounded handover list
For each important relationship, record the next action, new owner and unresolved question. Include automations or integrations the person maintained, even when those are not customer records. Do not ask for or share personal passwords. Use supported account administration and organizational credential procedures where applicable. This page does not perform account changes or authorize access to another person’s mailbox. Keep protected information within the appropriate responsible team.
Verify the transfer
Ask receiving colleagues to recover the work from the records. Check representative tasks and any deadlines that fall near the departure. Confirm that the new owner can see the necessary context without receiving broader access than needed. If an account removal procedure offers reassignment, inspect its result rather than assuming the prompt covers all commitments. Preserve original identifiers and history so later questions can be traced to the actual handoff instead of a newly created replacement record.
Review connected services afterward
Check which authorized mailbox connections, exports or integrations require a separate change under the organization’s process. Avoid indiscriminate deletion that destroys useful evidence or breaks unrelated work. Record what was changed and which items remain with a named owner. The departure is complete operationally when important commitments continue safely and access matches current responsibilities. Continue to owner handoff for the relationship details and access review for the demonstrated permission boundary.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Capsule team-task management — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20
- Capsule exporting and deleting contacts — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20