Skip to content
be-human.ai
← Back to the journal

Human oversight

Offboarding Staff From AI Agent Access: Tools, Memory and Approvals

Remove a departing employee's agent permissions, shared memory access and approval rights, then verify the change and keep a record of it.

Be Human typographic cover with the title: Offboarding Staff From AI Agent Access: Tools, Memory and Approvals
Conceptual illustration created with AI · Be Human

To offboard a departing employee from AI agent access, revoke their personal credentials and agent sessions, remove them from shared memory spaces and agent workspaces, and move any approval rights they held to a named backup. Then rotate the shared secrets they could reach and confirm each change in the logs on the same day. The steps below apply whether your agents run on your own infrastructure or through a managed service.

Key takeaways

  • Treat agent access as a separate list from software accounts. Agents hold tool grants, memory scopes and approval rights that a standard account review often misses.
  • Revoke in order: sessions and tokens first, then tool grants, then memory scopes, then approval rights, then shared secrets.
  • Reassign approvals before the last working day so that no pending action waits on someone who has left.
  • Keep the company's operating knowledge in shared memory, and handle only the departing person's personal data under your deletion policy.
  • Verify the removal from the outside, by trying the access and reading the logs, and file the evidence with the change ticket.

Start with an inventory of what the person could reach

Before you change anything, write down everything the person could reach through an agent. Most offboarding gaps come from access that nobody listed, not from access that was forgotten on purpose. Check four places: the agent platform's user list, the tool connections each agent uses, the memory spaces shared with the team, and the approval queues where the person was a named approver.

Ask for a short export from each system rather than relying on memory. The export should show who granted each permission, when it was granted, and whether it runs under the person's own identity or under a shared service identity. Permissions granted through a personal login are the ones that stop working cleanly when the account is disabled, so they need the closest attention.

An agent that acts with a departed person's delegated permission is still acting for that person until the grant is removed.

Illustrative scenario: a sales operations lead connected the team's agent to the company mailbox and the shared pipeline spreadsheet using her own login, and she was also the only approver for discount requests above the standard threshold. The agent kept drafting follow-ups for three weeks after her departure because nobody had listed the mailbox connection as hers. The inventory would have caught it on day one.

Revoke access in the right order

The order matters because each layer depends on the one before it. If you remove shared secrets first, active sessions may keep running on cached tokens. If you remove approval rights first, the agent may queue work that no one can release. Use this sequence:

  • Disable the person's login to the agent platform and end all active sessions, including any API keys created under their identity.
  • Revoke OAuth grants and tokens that link agent tools to their account. Revoking the grant is stronger than only changing the password, because tokens can outlive a password change.
  • Remove the person from each tool connection the agents use, and reconnect those tools under a team or service identity that someone currently owns.
  • Remove their access to shared memory spaces, including read and write scopes, and check whether any agent holds a copy of their personal notes.
  • Reassign approval rights to a named backup, then remove the departing person from the approver list.
  • Rotate any shared secrets, API keys or service credentials they had seen or stored, even if you believe they never copied them.
  • Record the time of each step in the change ticket.

For the principle behind this sequence, the OWASP authorization guidance describes checking access on every request and granting only what a role needs. A removed grant should not be able to act again, even if a cached session still exists somewhere in the stack.

Move shared memory access without erasing company knowledge

Shared memory is the hardest part of offboarding because it mixes two kinds of content. Some of it is company knowledge: process notes, customer context agreed with the team, decisions and their reasons. Some of it is personal: notes about the person's own health, private messages, or details they stored for their own convenience. These need different handling.

Remove the departing person's access first, and leave the content in place unless a deletion request or your retention policy says otherwise. Deleting shared company knowledge because one employee left removes context that the remaining team still needs. Then review the entries the person created and sort them into three groups: company knowledge to keep, personal data to delete or minimize, and material that must be preserved for a dispute or audit. Where personal data is involved, follow your legal basis and the deletion process you already use, and confirm that the deletion reaches any copies the agent may have stored in its working context.

The erasure requests for agent memory guide covers the verification steps in more detail, and it is the right reference when the departing person asks for their data to be removed.

Reassign approval rights before the last working day

Approval rights are the piece most often left behind, because they do not show up as a technical permission. An agent may stop at an approval step and wait, and the business may not notice until a customer or supplier asks why an action is pending. Before the last working day, list every approval the person held, including standing approvals for recurring actions, approvals with dollar or contract limits, and approvals used during holidays or absences.

Assign each one to a named backup who has the authority to make the decision and who can see the context the agent provides. Do not assign approval to a shared inbox that nobody watches. Clear the pending queue with the departing person if possible, so that open decisions are either made or explicitly handed over. The human approval gates guide describes where people should sign and why that record matters after a handover.

If the departing person was the only one who could approve a class of action, treat that as a finding. Either add a second approver before they leave, or reduce what the agent is allowed to do in that class until a replacement is in place.

Verify the removal and keep the evidence

A removal is complete only when someone tests it from the outside. Ask a team member who has the current role to run the checks below, and do not let the departing person's former manager sign off alone. Keep the results with the change ticket.

  • Attempt a request with the departed person's old credential and confirm it is refused.
  • Confirm that no agent tool connection still lists their account as the owner.
  • Check the memory spaces and confirm their identity no longer appears in access lists.
  • Confirm that pending approvals now route to the named backup and that none are waiting on the departed person.
  • Review the agent logs for the period after the departure and look for any action taken under their identity.
  • Confirm the rotated secrets were replaced in every system that used them.
  • Store the export, the change ticket and the verification results in the same place.

If the log review finds an action taken after the departure, treat it as an incident. Record what the agent did, who it affected, and what must be corrected, and do not delete the logs to tidy the record. The access review guide explains how to fold this check into a regular permission audit, so that the next departure is a routine step rather than an emergency.

How Be Human handles offboarding in managed operations

Be Human designs agents so that each permission, memory scope and approval right is recorded against a named role and a named owner from the start. In managed operations, that record is what makes offboarding a bounded task: the team can see which grants belong to a person, which belong to a shared service identity, and which approvals need a new owner. Monitoring and permission review run on a schedule, so stale grants are caught before a departure exposes them. When a departure happens, the change is made under the same controls as any other permission change, and the evidence is kept with the agent's operating record.

If you are not sure which agent work in your company depends on one person's access today, that is a useful question to answer before the next handover. The free Be Human AI diagnostic can help you find the first task worth handing to an agent, and the same review shows which access that task would need.

Frequently asked questions

How quickly should agent access be removed after an employee leaves? Remove personal sessions, tokens and tool grants on the last working day, ideally before the employee's final session ends. Reassign approvals and rotate shared secrets the same day, and record the time of each step. Waiting for a routine review leaves a window in which delegated permissions still work.

Should we delete the departing employee's agent memory? Not automatically, because shared memory often holds company knowledge that the team still uses. Remove the person's access, then sort their entries into company knowledge to keep, personal data to delete or minimize, and material to preserve. Apply your deletion policy and legal basis to the personal data, and verify that copies in agent working context are also removed.

What if the departing employee was the only approver for an agent action? Treat it as a gap to close before the handover. Name a backup with real authority and the context to decide, and clear or hand over any pending approvals. If no replacement is ready, narrow what the agent may do in that category until a second approver is in place.

Do contractors and temporary staff need the same offboarding steps? Yes, and they often need more attention because their access is more likely to sit on personal logins or outside accounts. Include them in the inventory, end their contract access on the agreed date, and run the same verification checks. Keep the evidence in the same place as the rest of your access records.

Your next step

See where an AI agent fits in your company first.

Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.

Less busywork. More room for you.

Bring us the work you wish you had time for.

Book a call to try a personalized AI agent free for 7 days ↗Or take the free AI diagnostic →