[[PageOutline(1-999,Table of Contents,pullout)]]

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.
1. To reduce risk of unauthorized actions, whatever the motivation or cause.
1. To reduce risk for the ex-employee of being blamed for problems and/or suspected of unauthorized actions, however unlikely.

## Communicate departure and impact of it ##

For each relation, colleague:
- Communicate departure and impact of it.

### Examples ###

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

## 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.)

### Examples ###

1. E-mail aliases and mailing lists.
1. VPS hosts.
  1. Dashboards/control panels etc.
  1. SSH keypairs, htpassword files and other local credentials.
1. 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.
1. GitLab groups.
1. External (administrative) accounts .
1. CLARIN ERIC website
1. CLARIN IdP: drop your roles down to a ‘citizen scientist’.
1. Google Drive, Calendar and other cloud services: unshare.
1. Personal work e-mail accounts. 
1. Cancel Slack account.

## 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.
1. Kill processes.

For each host you administer, find leftover files.

### Examples ###

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

Good utilities for this are [https://github.com/sahib/rmlint `rmlint`] and `find`.


## Complete formalities before leaving ##

### Examples ###

1. Timesheets