When someone leaves¶
A person leaves; the things they set up keep running. Hand over their keys, give what they owned a new owner, then remove them. Nothing that runs on their keys stops, and every step is recorded with a reason.
Before you start¶
You're an organisation admin (or a group admin for someone in your teams, for the keys and agents in your part of the organisation). Know who takes over each thing.
Steps¶
- See what they hold. Open People, choose the person and open Keys. On Delete, What goes with them lists everything in one place: live keys, roles, the agents, applications and service accounts they own, and the rules set on them. You can open it to look, and cancel.
- Hand over the keys that matter. On each key, choose Hand over…, pick the new holder and the team it acts for, choose Issue a new secret (recommended) or Keep the secret, and give a reason. See Hand over a key.
- Revoke the rest. A key nobody needs: Revoke.
- Give their agents, applications and service accounts a new owner on each one's Owners tab.
- Disable or delete them. Disable keeps their teams and roles for a while; delete ends them for good. See Disable or delete someone.
Check it worked¶
- The handed-over keys show their new holder and keep working.
- Home's Needs attention has nothing about their agents having no owner, or keys nobody handed over.
- The audit log lists each handover with its reason.
Good to know¶
- Once someone is deleted, their keys stay suspended until revoked or handed over: hand over the ones you need first. A key whose holder was deleted can still be handed over, and works again for its new holder.
- A key keeps everything that belongs to it across a handover: its models, rate limit, routing, exemptions, guardrails and budgets.
- When the person who issued a key can no longer issue it (they left its team, say), the key keeps working and says so. An admin of its team can Take over: they become its issuer, and the secret stays the same.
- Their past calls stay charged where they were charged when made.