Removing an employee from the dashboard may leave active sessions, recording links, API credentials, and exported files outside that change. Review every access path tied to the person’s actual responsibilities.
Departure access review covers direct and delegated paths
An employee departure review identifies and removes access according to the organisation’s established process. It includes accounts, roles, groups, sessions, shared credentials, integrations, and ownership of unresolved operational work.
For a proposed checklist, map the person to application roles, provider consoles, recording stores, export permissions, notification groups, and configuration authority. Use trusted personnel and access records to trigger the process, not an AI inference from conversational content.
Previously downloaded content cannot be revoked through the application. Handle that limitation through the actual organisational requirements and process. This article describes technical verification, not a universal legal rule for employee records or offboarding.
Test a fictional departing manager
A manager leaves after owning several callback items and holding routing-configuration permission. The access workflow removes the relevant roles, invalidates supported sessions, rotates shared secrets where policy requires, and reassigns the open callbacks.
A still-open browser tab should not allow new protected actions after revocation under the defined session policy. A temporary recording URL may have a separate lifetime that must be considered rather than assumed to follow dashboard logout.
| Access path | Verification |
|---|---|
| Dashboard account | Current login and protected requests denied |
| Provider console | Relevant membership removed |
| Shared integration secret | Rotated or otherwise handled under policy |
| Recording or export links | Supported revocation and expiry reviewed |
| Open follow-up work | New accountable owner assigned |
Test through supported interfaces with an appropriate controlled account. Do not treat the absence of a user in one list as proof that every access route is closed.
Preserve accountability without retaining privileges
Audit the actions taken and any unresolved exception. Transfer ownership of scheduled checks, configuration proposals, and incident responsibilities so the service does not depend on an inactive employee’s account.
Central identity management can simplify revocation, but service-specific accounts and external exports may still remain. Maintain the inventory and review exceptions. Temporary continued access, if authorised by policy, needs a clear scope and expiry rather than an informal promise.
This review design is proposed. The voice platform case study provides related full-stack context. See dashboard role design for the permissions being removed.
Departure access FAQ
Is disabling the main login enough?
Not necessarily. Review provider accounts, sessions, links, keys, and shared resources.
What happens to callbacks owned by the employee?
Reassign them explicitly and retain the relevant work history.
How should completion be recorded?
Keep a scoped checklist of verified actions, responsible actors, timestamps, and approved unresolved exceptions.