Virtual assistant access removal

Key takeaways

• Use a written brief and definition of done.
• Keep approvals and escalation rules visible.
• Review quality before expanding the workflow.

# Virtual assistant access removal

Inventory systems, shared folders, delegated mailboxes, recovery methods, and service accounts. Confirm identity and end date, revoke each item, and recheck critical systems after propagation.

Applying virtual assistant access removal

Treat offboarding as an inventory problem with a verification step. Start from the account list, then check delegated access, shared credentials, recovery channels, and integrations that do not appear in the main directory. Record the revocation time and the person who confirmed each high-risk system.

Role boundary and review

An assistant can reconcile the inventory and prepare a revocation checklist, but an authorized owner must approve removal where another person or service could be affected. Keep an exception queue for accounts that cannot be removed immediately, with a compensating control and a follow-up date. the [services library](/services) to clarify which support lane owned the account, and the [[provider vetting guide](/provider-vetting)](/provider-vetting) to ask about offboarding. [NIST small-business cybersecurity guidance](https://www.nist.gov/itl/smallbusinesscyber) provides a useful access-control reference. ### Offboarding record Keep the account inventory, revocation evidence, exceptions, compensating controls, and final reviewer.