Skip to content

Leavers process

Leo Hemsted edited this page Apr 11, 2022 · 10 revisions

When someone leaves you should reverse the joiners process steps. You should similarly make a Pivotal ticket to track the progress of the tasks. Even if they are not a developer, you should check all the tasks as we often give permissions to non developers such as allowing product managers and content designers to edit Github.

Some accounts are handled centrally to GDS, and the removal process for those should be picked up when their line manager completes their leavers process. This includes:

  • Pagerduty
  • Github (you should still remove them from notify teams before anyway, as this will instantly stop their ability to merge and access concourse)
  • Zendesk
  • AWS

Extra details for removing access to AWS account

Remove user from:

notifications-aws repo

  • terraform/modules/local-development/iam.tf
  • terraform/modules/local-development/variables.tf
  • terraform/modules/main/modules/iam/variables.tf

notifications-broadcasts-infra repo

  • terraform/deployments/preview/account/site.tf
  • terraform/deployments/staging/account/site.tf
  • terraform/deployments/production/account/site.tf

Run terraform on all environments

Clone this wiki locally