Offboarding checklist for @Carley-Jackson

[danswick]

For everyone

• Remove from Google groups as applicable:
  • FAC-team
  • fac-gov-test-users
  • fac-gov-api-dev
• Remove from the FAC team in GitHub
• Remove from the private channels #oros-fac-private and #fac-helpdesk in Slack (“/remove @[person]”)
• Remove from active Figma projects
• Remove from Mural
• Remove from Zendesk
• Check for and remove admin access in the FAC application: this may include designated permissions and/or checked-in API access (for example)

For GitHub contributors

• Make a PR to remove the departing team member from the list of developers and managers with access to our spaces.
• Remove the departing team member as a member of the FAC group in New Relic. (@GSA-TTS/fac-admins can do this)
  • If they're leaving TTS altogether, also delete their account.

For admins

• If the departing team member is a Google Group manager, designate a new manager for any groups they manage.
• If they are the on Make someone else the Maintainer and remove the departing team member from the FAC-admins team in GitHub and the FAC-team team in GitHub.
• Remove any deployment tokens associated with the PL/PO from the repository.

[jadudm]

Not applicable (for reference):

• If the departing team member is a Google Group manager, designate a new manager for any groups they manage.
• If they are the on Make someone else the Maintainer and remove the departing team member from the FAC-admins team in GitHub and the FAC-team team in GitHub.
• Remove any deployment tokens associated with the PL/PO from the repository.
• Remove the departing team member as a member of the FAC group in New Relic. (@GSA-TTS/fac-admins can do this)

[jadudm]

@Leighdiddy , could you please check the Mural, figma access?

@tadhg-ohiggins , @timoballard , could one of you please check the app access?

[danswick]

Looks like we're all done here.