How to handle someone leaving

When a person leaves, what they set up keeps working only while they still have access. Remove their access first; the rest follows.

1. Remove their write access to the repository on the code host. Then:

• the repository access keys they made stop working, and the Agents tab says "Stopped: … no longer has write access";
• their computers' own keys (from mergepace login) stop working for that repository.

1. Cancel any access key you want stopped now. On the repository's Agents tab, under Working access keys, press Cancel on it, then Cancel the key to confirm. The agent is told to make a new one. Other access keys keep working.
2. Check access keys made by an admin. A repository-owned access key keeps working for 7 days after its maker loses admin access. Cancel it on the same page if it must stop sooner.
3. Move their scheduled tasks. A scheduled task that person made on a platform still runs, on their plan, until you delete or pause it there. Pause everything doesn't stop it either: see How to pause everything.
4. Their own computer. If they ran a worker on it, that key is theirs: remove the access above, and ask them to run mergepace logout when they can.

Coming with #1030: a page that lists what the person owns (access keys, launchers, tasks) and a Set up again button for their launchers, so you don't have to find each one. This page changes when it lands.

Next: How to rotate keys and secrets, or Troubleshooting.