title | layout | category |
---|---|---|
Offboarding |
article |
Team |
Review the Leaving TTS page in the TTS Handbook and follow the instructions there.
- Review and share leaving GSA/TTS guidance with this person.
- If this person is unable to email their resignation letter for any reason you must do it on their behalf.
- If applicable, send an email to the login.gov team announcing that this employee is leaving Login.gov
- Create a new issue in the
identity-devops
GitHub repository using the off-boarding template and ping@login-devops-oncall
in Slack to alert them to the new offboarding issue - 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 fromidentity-*
GitHub teams.- Note that CircleCI, CodeClimate, and Snyk rights are removed via GitHub integration
- Create a ticket in the Jira AdminTasks project requesting that the user be removed from the Login.gov project (and deactivated if they are no longer working for GSA).
- Use the TTS Slack Form to submit user modification
- Remove user from Login.gov Google Groups
- Remove the user from Hubspot
- Remove UX members from GSA owned applications
- Remove the user as admins from any dashboards
- Update team.yml
- Update the Login.gov org chart