Leavers process

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 if they're moving teams they may still need access to the systems (though may need to be removed from notify teams within those systems).

• Pagerduty
• Github
• Zendesk
• gds-users AWS

Extra details for developers with GPG keys

Revoke your GPG key.

This stops anyone using it to e.g. encrypt credentials or sign commits.

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