Setup checklist: inventory responsibilities before access changes
Identify the departing person’s active requests, pending approvals, recurring duties and client commitments. Assignment lists are a starting point, not a complete account of responsibility. A person may also own a file location or be the only teammate who understands a promised exception. Record those dependencies before the handoff where circumstances permit. Follow your organization’s security process if access must be removed immediately; operational convenience should not override a necessary protective action.
Transfer the next action
Give each active request a new accountable owner and a short handoff note. Include the current version, accepted scope, unresolved question and next promised update. Preserve the previous comments and decisions. Recreating every request under the new person’s name can lose context and confuse clients. ManyRequests documents assignments and role controls, but verify the actual supported change rather than assuming that deleting a staff account automatically transfers every relevant responsibility.
Review external dependencies separately
Portal access may be only one part of the person’s access to client material. Consider approved file storage, payment systems and communication tools through your normal process. Do not share the departing person’s password with a replacement or export secrets into a handoff document. Keep the review scoped to authorized systems. A change in one application does not prove that all access has been revoked elsewhere, so state the remaining checks honestly.
Confirm continuity from the client’s perspective
Check that the client knows who will respond and that the replacement can access the necessary work without excessive permissions. Send a concise operational update where appropriate, not private employment details. Keep historical author attribution intact. A successful handoff lets the client continue the same request with minimal repetition and gives the new owner enough evidence to act responsibly rather than guessing what their predecessor had agreed.
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.
- ManyRequests admin, client and team permissions — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests managing requests and exporting data — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19