Security & sovereignty

How to revoke AI agent access when an operator leaves

To revoke AI agent access when an operator leaves, identify the person who can instruct the agent, the account it uses to reach each tool and the person authorised to approve its work. All three roles can belong to different people. Trace one real job through them before deciding which connections to retire and which work to transfer.

padlock on laptop with light trails
Photo by FlyD on Unsplash

Part of our guide to Sovereign AI in Australia: a practical guide for operators

On this page · 7 sections
  1. Follow the job the departing person ran last Friday
  2. Decide what happens to each connection
  3. Transfer unfinished work by checking its destination
  4. Remove access at the systems that issued it
  5. Rehearse the first shift after the handover
  6. Leave a handover record the duty manager can use
  7. Frequently asked questions

Imagine a practice coordinator who prepares Friday’s appointment reminders. A schedule starts the job, an assistant reads the booking diary, and the coordinator approves a draft before it goes to the front desk. On Monday a replacement coordinator needs to find the draft, see its approval status and confirm who will send it. Removing a name from the staff directory answers none of those questions.

Follow the job the departing person ran last Friday

Find the most recent completed run. Record its start time, the calendar or mailbox it used, where the draft landed and the identity shown on the destination’s activity record. Ask who received the review request and who could change the schedule. Use ordinary reference numbers in the handover document. Credentials, customer details and message bodies belong in their existing controlled systems.

Check one unusual run as well. Perhaps the coordinator handled a public holiday from their phone or used a second calendar when the usual one was unavailable. That exception can reveal a personal connection missing from the standard instructions. Mark its purpose and whether the business still needs it. A replacement deserves to know which route the team actually used when a normal Friday became difficult.

Decide what happens to each connection

An assistant may use a person’s delegated permission to read a diary, while a separate business-owned integration writes approved notes to CRM. Removing the first permission can stop the lookup. Removing the second can interrupt colleagues across the practice. Assign a business owner to the work and ask the relevant system administrator to identify the grant behind each connection.

Item on the handoverDecision to recordEvidence after the change
Personal diary connectionRetire the outgoing operator’s grant and authorise the successor’s required calendarProvider records the change and a permitted test appointment appears for the successor
Shared CRM integrationKeep it for named workflows that still need it and remove the former operator’s controlCurrent administrators and the destination activity show the intended identity
Scheduled reminder draftPause or transfer the next run and nominate one approverA single review request reaches the current coordinator
Personal notification channelRemove it from recipients, escalation rules and recovery contactsA test alert reaches the duty desk through its agreed route

Check who can reconnect an integration as well as who can use it. A person who no longer receives task notifications may still administer the workspace, approve new connections or control its recovery mailbox. Conversely, a departing employee may appear in historical activity solely because they approved a past job. Preserve the historical attribution and review their present authority separately.

Transfer unfinished work by checking its destination

Before a planned departure, identify drafts awaiting approval, operations already started and jobs scheduled after the handover. Give each item an owner and one disposition: finish under current authority, review again under the successor or cancel. For an immediate departure, follow the organisation’s access cutoff first and have an authorised colleague recover outstanding work from business records.

Consider an appointment reminder that shows “sending” when the coordinator finishes. The successor can check the sending service for the message reference and its recorded outcome. If the service accepted the message, record that evidence before deciding whether the job needs further attention. If nobody can establish the outcome, flag it for a person. Automatically rerunning a half-finished job can send customers two reminders.

A draft held for approval deserves a fresh look when the approver changes. Record what the customer was promised and the deadline. Route the proposal to someone who holds the relevant decision authority today. Keep the outgoing coordinator’s earlier comments attached to their original identity. A changed owner field should tell colleagues who acts next while leaving the history understandable.

Remove access at the systems that issued it

Have the responsible administrator perform the agreed account and application changes at the employment cutoff. For a delegated connection, identify the application, resource and granting account. For a shared service identity, review who manages its credentials and who may command the workflows using it. Record the time and the provider’s confirmation using a connection identifier the next administrator can recognise.

Google advises revoking user tokens once they are no longer required and removing them from application storage. Confirm who owns each part of that process when an external vendor operates the assistant. Google OAuth guidance

Microsoft explains that an application can issue its own session after sign-in through Entra ID. The application controls that session, and the effective timing of revocation can vary. Check the application’s own controls and record any interval during which additional verification is needed. Microsoft’s guide to revoking user access

Rehearse the first shift after the handover

Use an invented appointment in the team’s approved test location. Ask the successor to prepare a reminder, open its source, inspect the draft and assign it to the duty desk. Keep customer delivery disabled for the exercise. Compare the identity and approval destination shown in the booking system, workspace and activity record. An unexpected name gives the administrator a precise connection to investigate.

Verify the removal through the former operator’s listed grants, role memberships and application session records using the administrator’s authorised view. Where your platform offers an approved access check, use it with a harmless sample resource. Keep a record of what you could establish and the next check due if the provider applies changes with a delay. Never ask for a former employee’s password to prove the point.

Watch the next scheduled cycle. The morning test may pass while the Friday schedule still names its original creator as reviewer. Assign someone to check that one draft arrived, the successor can see it and the former operator is absent from the current notification list. If your team coordinates specialist work through Fulcrum Sessions, include the person receiving the recap and the person who controls the connected business tool in this exercise.

Leave a handover record the duty manager can use

A short closure note should answer four questions. Which access ended, which work continues, who owns it now and what evidence supports those statements? An example might read “Personal calendar grant removed at the agreed cutoff. Reminder schedule paused pending review. Priya owns the three remaining drafts. Duty manager checks the first resumed Friday run.” Store the references to administrative confirmations alongside the note.

Related guides: Sovereign AI in Australia: a practical guide for operators · Least privilege for AI agents: give each one only the access its job needs · 20 questions to ask before connecting an AI assistant to your business.

Frequently asked questions

Does a password change remove every AI integration?

Check each integration’s identity and provider controls. A team application can hold independently authorised access, and an application session can have its own lifetime. Verify the named grants, active sessions and scheduled runs involved in the person’s work.

Can the successor keep using the outgoing operator’s connection?

Give the successor the access approved for their own role or use an explicitly managed business identity where the provider supports it. Record the responsible owner and test the narrow task. Sharing a former colleague’s credentials makes later actions difficult to attribute.

How can a small team tell that offboarding is complete?

Ask the new owner to show one continuing job end to end, then ask the administrator to show which old grants and roles were removed. Record any scheduled check still due with a name and date so the next shift knows exactly what remains open.

Sources

  1. Google OAuth guidance
  2. Microsoft’s guide to revoking user access

General information only, not legal, financial or professional advice. Check the source for your circumstances.