OffboardingChecklist.md

Offboarding Checklist

Instructions

When someone leaves the cloud.gov team

1. Create a new issue in cg-product called "Remove [person's name] from cloud.gov team".
2. View the raw source of this file
3. Copy everything below the line into the new issue's body
4. Replace "LeavingPerson" with the leaving person's name
5. Delete any checklists irrelevant for the skill domain of the leaving person
6. Submit the issue
7. Assign the issue to the person who bravely volunteered to be handle the person's offboarding
8. Put the issue into the "In Progress" pipeline in Favro

---

In order to complete LeavingPerson's exit from the cloud.gov team, the assignee should complete a prescribed set of tasks that will remove any special access.

Directions:

Assignee: The tasks below are organized by the role needed to complete them. If you can’t complete any of the items on your checklist personally, you are responsible for ensuring that an appropriate person does it.

Assignee

• Remove them from @cg-team, @cg-operators, and any other @cg- teams in the Slack Team Directory
• Remove them from the team roster
• Remove them from the squad list
• In the training tracker: if they're staying at 18F, move them to the "former teammates" tab; if they're leaving 18F, delete them from the spreadsheet
• Remove them as invitees for any meetings on the cloud.gov calendar
• If they are leaving 18F, ensure the 18F Handbook exit process has been kicked off via the 18F talent team

System Owner (or person delegated by System Owner)

• Remove them from GitHub teams that start with cloud-gov
• Remove them from the Cloud Foundry Community GitHub org cloud.gov team
• Remove their access to Zendesk - switch their role to "end user"
• Remove their access to StatusPage - likely have to ask devops@gsa.gov
• Remove their access to PagerDuty
• Remove their access to New Relic
• Remove their access to Favro
• Remove them from the cloud.gov team Google Group
• Remove them from the cloud.gov notifications Google Group
• Remove them from the cloud.gov inquiries Google Group
• Remove them from the cloud.gov support Google Group
• Remove them from the cloud.gov emergency Google Group
• Remove them from the cloud.gov operations Google Group
• Remove them from the cg-supportstream private Slack channel
• Remove them from the project in Float
• Remove their membership in cloud.gov-specific Trello boards (eg the business-tracker)
• Remove them from DigitalGov Search access for cg-site
• Remove them from Nessus

Cloud Operations

• Remove them from any IAM roles they hold in AWS GovCloud
• Remove their access as an admin on the platform
• Remove any Org or Space roles that their cloud.gov account holds due to membership in the cloud.gov team (for example, remove them from the cloud-gov-operators organization)
• Confirm the System Owner (or person delegated by System Owner) has removed them from all GitHub teams
• Ensure any keys or passwords they had direct access to are rotated

Customer Team

• Delete their account from the customers app.
  • Production Site
  • Staging Site