How we handle GDPR data-subject requests on a deadline
Legal
On a schedule, an agent checks for newly marked departures and runs the offboarding checklist across Okta, Google Workspace, Google Drive, and GitHub — revoking access, transferring ownership, and reclaiming licenses — holding the ownership transfer for approval and never deleting an account.
Offboarding is a checklist that has to run to completion. When someone leaves, their access has to be revoked everywhere, their documents and repositories have to change hands, and their licenses have to come back. Miss a step and a former employee keeps a login, a shared drive loses its owner, or a paid seat sits unused. The steps are simple; the risk is in the ones that get skipped.
We run offboarding through an agent on Kortix. On a schedule, the agent checks for newly marked departures and works the checklist across every connected tool, posting what it did and what is still pending. This is the security counterpart to how we onboard.
When an employee leaves, their access has to be pulled from every system they touched, their work has to be handed off, and their licenses have to be reclaimed. That means Okta, Google Workspace, Slack, and GitHub, each with its own steps, done in the right order, on the same day.
The common approaches leave gaps. A written runbook depends on someone working it by hand under time pressure, and a missed line is a live account no one notices. A provisioning tool covers SSO but not document ownership or repository access. IT tickets spread the work across people and days, and the parts that are easy to forget are exactly the ones that matter for security.
On Kortix, an agent checks Okta on a schedule for newly marked departures. Each check spawns an isolated session (a cloud sandbox) with scoped access to Okta, Google Workspace, Google Drive, and GitHub, and works the offboarding checklist for every departure it finds: revoke SSO and app access, remove the person from the GitHub org, transfer document and drive ownership, and reclaim licenses. The ownership transfer waits at a human approval gate — account deletion is never attempted — and the agent posts a completed checklist showing what it did and what is still pending.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the offboarding checklist skill and the hourly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up an employee offboarding agent in this workspace.
Create the agent agents/employee-offboarding.md. Its job is to run the offboarding checklist for each departing employee. It may use the Okta, Google Workspace, Google Drive, GitHub and Slack connectors.
Create the skill skills/offboarding-checklist/SKILL.md with these rules:
Add a cron trigger offboarding-check to kortix.yaml. It runs the employee-offboarding agent every hour, on the hour, with the prompt "Load the offboarding-checklist skill and work every new departure in the Offboarding group."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your identity provider, Google Workspace, Google Drive, GitHub and Slack. Credentials are brokered server-side and never enter the agent's machine.
Finds new departures and revokes SSO and app access.

Marks the departure that starts the checklist.
Posts the completed checklist, with pending and failed steps.
Merge the change request, then start a session with the employee-offboarding agent and send this prompt. Check each step in the checklist before you let the schedule take over.
Run the offboarding checklist once.
The change request added this trigger to kortix.yaml. From now on the agent
runs every hour, on the hour, each run in a new session on its own cloud
computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: offboarding-check name: Offboarding checklist run on: cron: "0 0 * * * *" run: agent: employee-offboarding prompt: Load the offboarding-checklist skill and work every new departure in the Offboarding group.Revoking access and reclaiming licenses run on their own, because they can be undone. Transferring ownership cannot be undone, so it stops for a person. An automated session waits at most 30 minutes for a person, then stops without transferring, and the next run asks again. The agent never deletes an account.
Each departure ends as one checklist in #it-ops. This is what a run looks like in the session:
Found 1 new departure. Deactivated the Okta account, removed 9 app assignments and removed GitHub org access. The transfer of 214 Drive files to the manager is waiting for approval, so the Workspace account stays active until then.
Once it works, paste any of these into the same session.
Also list the personal access tokens and OAuth apps the person created in GitHub, and revoke each one after the Okta account is deactivated.
Send the manager a Slack DM with the completed checklist and the files that will move to them.
On the first of each month, check that everyone who left last month is still deactivated in Okta and absent from GitHub, and report any gap to #it-ops.
The agent revokes access and transfers ownership across every system, so the access is scoped and contained:
Access that used to depend on someone working a runbook by hand now comes down the same day a departure is marked, with ownership transferred and licenses reclaimed in the same run. The ownership transfer waits for a person, and the completed checklist shows exactly what happened and what is still pending.