An employee is leaving: revoke AI access and hand over automations
Plan process ownership, credentials, continuity and access revocation when a person leaves or changes roles.
Article language: English

In this article
The computer is back at the company and the mailbox is closed, yet an automation still runs on a former employee's private key. Or it stopped precisely because their account was removed. When someone working with AI leaves, connect revocation of permissions with handover of processes and responsibility. The access list should include integrations, resources and owners. An offboarding procedure needs to end with more than signing out of one screen.
The procedure below concerns a planned handover of duties. If misuse or account compromise is suspected, use the appropriate incident process and do not delay restricting access until housekeeping is complete. Technical steps must fit the actual provider, service plan and administrator permissions; there is no single button that disconnects every possible connection.
What should be found before the last working day?
Start with resources, not application names. A person may own projects, shared assistants, schedules, drive connections, API keys and rules for passing on results. An entry in your company's AI tool inventory is a good starting point, but usually needs account- and process-specific detail. When organising the inventory, you can use the AI tool inventory guide (in Polish).
Give each resource a decision: transfer, retain for reading, end or clarify. Add a business owner, the person making the change and a deadline. Not every employee conversation is knowledge the team needs, and not every automation deserves continuation. The decision should follow the purpose and authorised scope for using materials.
Ask the departing person about processes operating without daily supervision. A monthly report may not appear during a one-week handover, and its absence may only be noticed after the account is deleted. Compare their account with schedules and available documentation. If scope is uncertain, record the specific gap rather than confirming a complete inventory.
Check payment and notification owners too. An invoice may go to the departing person's address, while an alert about an approaching limit remains in their inbox. Moving those contacts is not a minor administrative detail: the new process owner needs service information before the team notices an outage.
How do you separate process ownership from credentials?
Ownership says who is responsible for operation. A credential lets a system perform an action. Transferring a project in a dashboard need not change the token used by an integration. For each important task, separately record the owner, execution account, connection used and person responsible for renewing it.
Power Automate documentation on changing a flow owner shows that the handover method depends on the flow type and ownership is connected to licensing. It illustrates why company procedures should refer to current documentation for the specific product. Do not transfer steps from one platform to another merely because both dashboards have a “share” button.
During an AI integration permissions review (in Polish), check that the new connection has the scope needed to continue. Do not automatically copy a predecessor's excessive rights. If a process used a personal account with broad access, handover is an opportunity to identify the task's actual scope and clarify responsibility.
Technical access shared by several people needs separate assessment. Changing a password alone may not end existing sessions and every type of token. Establish which mechanisms the provider supports, which secrets need changing and how to check the effect. Do not put new keys in the handover document or an ordinary team message.
In what order should a planned handover occur?
First approve the disposition of resources and the new owner. Then prepare the takeover at the agreed time, check operation and only then end the departing person's access according to the schedule. This order concerns a calm, planned departure. In a higher-risk situation, immediate access restriction may take priority over continuity.
For recurring processes, set a switching point. Old and new schedules should not send the same report simultaneously. Mark tasks already completed and those still queued. Without reliable state, prepare a manual review of the next run rather than assuming recipients will notice a duplicate.
The new owner should perform a trial independently, without using the predecessor's session. They check entry to the resource, reading materials, approval of the result and necessary target operations. A screenshot showing a name in the owner field does not confirm that the integration will run once the old credential is removed.
Keep separate confirmations of handover and access revocation. The first concerns ability to continue; the second concerns restriction of previous rights. If one fails, the remaining risk is clear. A general “account closed” field hides that distinction and makes later explanation harder.
What does effective access revocation mean?
Disabling new sign-ins may not end all existing sessions. Microsoft describes differences between tokens and application sessions, noting that an application may manage its own session. The procedure must therefore specify the mechanisms checked and confirm behaviour of services the company actually uses.

Give the administrator an environment-specific action list with required roles. Where relevant it covers accounts, connections, mobile applications, keys and sharing. The list should not demand actions the product does not support. If a particular session cannot be revoked centrally, record the limitation and an agreed alternative control.
Test denial of access in an approved way, without bypassing security or taking over private accounts. An administrative view, change record and control trial on a prepared test account may often suffice. The evidence required depends on risk and system capability. Excess personal data is not needed simply to confirm an action.
Do not equate access revocation with deletion of materials a person may have downloaded earlier. That is a different matter requiring appropriate organisational rules and agreements about devices and data. The technical record should state its scope honestly. Claiming that “no copies exist” after disabling an account usually exceeds available evidence.
What might a hypothetical weekly-report scenario look like?
Suppose an analyst created an assistant that summarises customer requests. The report goes to a manager weekly. Before leaving, she hands over the folder and instructions, but the process still uses her connection to the request system. The new owner can see the project but cannot refresh data after the predecessor's account is disabled.
During a trial handover, the team finds the dependency using fictional requests. It prepares a new approved connection, limits read scope and sets the switching point. The old schedule is disabled. The new owner runs the report and checks that it has the correct data and does not go to an outdated recipient list.
One query concerns a previously closed case and needs context from the analyst's note. The team does not copy the entire conversation history. It adds a status-interpretation rule and a link to the source in the company system to the instructions. Necessary knowledge is transferred while the material scope remains aligned with the process purpose.
After access is actually revoked, the new owner repeats the reading and distribution trial on control data. The result closes that specific scenario. A review of the next weekly run remains planned because a manual trial has not yet checked the real schedule at its scheduled time.
How can knowledge be handed over without copying everything?
Prepare brief instructions covering the process purpose, sources, limits, known exceptions and how to verify the result. Good company knowledge architecture (in Polish) places information where the team actually looks. A private history of experiments may be unnecessary if the approved way of working is clearly described. If the process uses saved model instructions, also hand over prompt-library versions and owners (in Polish), so the successor knows which instruction applies and who approves changes.
Include one ordinary example and one boundary case. The new person should know what a correct result looks like and when to stop and request a decision. Prepare examples without confidential data if it is not necessary for handover. Documentation should also remain useful for the next deputy.
Identify the owner of substantive decisions. The person maintaining an integration need not be authorised to approve an answer to a customer. An AI-agent workflow (in Polish) should retain clear roles after a staffing change. Transferring access does not automatically transfer all of the predecessor's competence or responsibility. If the process is also divided among AI performers, check handover of conditions and evidence between agents (in Polish), rather than assuming the successor knows the preceding task's state.
Decide what happens to unnecessary materials. AI data retention and deletion (in Polish) helps distinguish a justified archive from abandoned copies. Do not mechanically delete everything on the last day if the organisation must retain certain documents. Retention needs a basis, scope and owner, not indefinite postponement of cleanup.
What should be checked when someone changes roles within the company?
When moving to another department, align resources and permissions with the new role. The account remains active, making it easier to overlook a connection to an old folder or receipt of reports the person no longer needs.
Determine which automations move with the employee and which remain owned by the team. The new manager should know which processes the employee must maintain and what assigned services cost. The former team needs cover for processes still serving it. One shared confirmation by both sides helps avoid each assuming someone else took over.
During handover, check the AI assistant's memory (in Polish) too. Establish which saved information concerns the process, where it is accessible and whether it should still influence responses. Removing one person's account does not automatically explain the fate of context used by the whole team.
How do you close the record and notice delayed problems?
Record resources, changes made, evidence of tests and remaining limits. Distinguish “done”, “checked” and “awaiting the next run”. This is more honest and practical than a blanket confirmation of complete closure. For an open point, name a person and a date to assess the result.
- Every important resource has a decision and a new owner or a closure plan.
- Project ownership and integration credentials were checked separately.
- The new owner performed the task without the predecessor's session.
- Schedules do not run the same operation in parallel.
- The scope of revoked access reflects the mechanisms of the actual services.
- Instructions, payments and notifications reach the right people.
- Remaining copies and materials have an agreed retention or deletion method.
If the company has automations tied to individual accounts, see the scope of Aeneia Audit.








