Besides having an onboarding procedure, an offboarding procedure (proper procedure for leaving as an employee) is also important. This is true in particular for highly authorized and/or key personnel. A number of reasons should be mentioned:

1. To manage the expectations of external relations, users, etc.
2. To reduce risk of unauthorized actions, whatever the motivation or cause.
3. To reduce risk for the ex-employee of being blamed for problems and/or suspected of unauthorized actions, however unlikely.

1. Communicate departure and impact of it

For each relation, colleague:

• Communicate departure and impact of it.

1.1. Examples

1. External developers.
2. Identity federations.
3. Academic hosters (generally, hosters that work on informal basis).

2. Drop permissions and data access

For each host, service you have access to:

• Relinquish you permissions to access and/or capabilities.

For each company data item you possess:

• Destroy. (Such data should already be protected and encrypted, and accessible from different copies by remaining colleagues.)

2.1. Examples

1. E-mail aliases and mailing lists.
2. VPS hosts.
   1. Dashboards/control panels etc.
   2. SSH keypairs, htpassword files and other local credentials.
3. GitHub organization. Normally, you should only be removed from teams/roles. In case repos are configured to grant you access personally, convert into team membership and remove yourself from the team.
4. GitLab? groups.
5. External (administrative) accounts .
6. CLARIN ERIC website
7. CLARIN IdP: drop your roles down to a ‘citizen scientist’.
8. Google Drive, Calendar and other cloud services: unshare.
9. Personal work e-mail accounts.
10. Cancel Slack account.

3. Tidy up data and processes you leave

Prevent that others will be distracted by irrelevant data.

For each host you have access to:

1. Backup and remove your personal data.
2. Kill processes.

For each host you administer, find leftover files.

3.1. Examples

1. Home directories.
2. Long-running processes such as tmux/screen sessions.

Good utilities for this are ​`rmlint` and find.

4. Complete formalities before leaving

4.1. Examples

1. Timesheets