title	description	layout	category	subcategory
Offboarding	List of steps which must be completed when a person leaves the Login.gov program	article	Team	People Ops

Full Offboarding

If a person leaves the Login.gov program they should have privileges revoked.

Review the Leaving TTS page in the TTS Handbook and follow the instructions there.

Create an issue in the Interrupts project in Gitlab using the offboard-devops template and ping @login-devops-oncall in Slack to alert them to the new offboarding issue. Tip: view current AWS users
Check in #admins-github to ensure that GitHub access for this person has been removed (TTS #people-ops is usually on top of this). If this person is moving elsewhere in TTS ensure they have been removed from identity-* 18F teams, GSA-TTS teams. Cc @github-admins-slack on your request.
- Note that CircleCI, CodeClimate, and Snyk rights are removed via GitHub integration
Using the JIRA Portal, choose Application Access and request that the user be removed from the Login.gov project (and deactivated if they are no longer working for GSA).
Remove from [Login.gov Slack groups]({% link _articles/slack.md %}).
Remove from [all accounts]({% link _articles/accounts.md %})
Update the Login.gov org chart

Partial Offboarding

If a person leaves temporarily, for example to fill a Detail, they can have privileges temporarily suspended.

Work with the devops team to remove AWS access (this is moving from GitHub to GitLab) and ping @login-devops-oncall in Slack to alert them to the new offboarding issue
Remove user from identity-admins GitHub team
Remove user from login-devops and login-security
Update the Login.gov org chart