Environmental knowledge, tools & collaborationFree to explore. Useful from the first question.

Governance

Manage staff departure without losing organisation records

Remove departing staff access while preserving authorised organisational records and a usable project handover.

Leaf Accord editorial2 min readReviewed 2026-10-04

Define the decision

Identify the departing person’s roles, active projects, approval responsibilities and access methods. List organisation-owned records separately from personal working notes and devices. Decide which tasks and customer relationships need a new responsible owner before the departure date. Record who authorises the transition and any unresolved ownership questions.

Build a usable record

Reassign open actions, review deadlines and source-update responsibilities. Preserve accepted specifications, evidence and version history in the organisation’s approved records system. Check integrations and shared credentials as well as the ordinary account. Provide a bounded handover to the next responsible person without giving them access to unrelated private information.

Check the evidence boundary

Revoke the actual grants and sessions through the trusted system, then test the result. Removing a staff name from a directory does not necessarily remove file or integration access. Handle personal data and retention under the organisation’s actual applicable process. Do not delete project evidence simply because its original contributor is no longer employed.

Worked example — illustrative

In a fictional supplier team, a coordinator leaves with three open recovery enquiries. The team assigns each enquiry to a new owner, preserves the recipient correspondence and removes the former coordinator’s access. An integration credential owned by that account is replaced through an approved process, and the scheduled task is tested afterwards.

Put the method into practice

Use the access-review template to track resources, replacement owners, revocation evidence and outstanding actions. Leaf’s local drafts can help plan the handover; they do not revoke hosted sessions or establish organisational identity. Real account changes and preservation controls depend on the engine and the operator’s authority.

  • Inventory roles and access methods.
  • Reassign open responsibilities.
  • Preserve accepted records.
  • Verify actual revocation.