search

ministryofjustice / operations-engineering

This repository is home to the Operations Engineering's tools and utilities for managing, monitoring, and optimising software development processes at the Ministry of Justice. • This repository is defined and managed in Terraform
https://user-guide.operations-engineering.service.justice.gov.uk/
MIT License
12 stars 5 forks source link

SPIKE: Review the process of removing users from the two GH Orgs #2242

Closed NickWalt01 closed 12 months ago

NickWalt01 commented 1 year ago

Background

When removing users from the MoJ and GH Org, the user needs to be removed from both Orgs to recover the license. If a GH Owner removes the user from one Org we need to be informed or that person needs to remove the user from both Orgs. There is the leavers process that informs the ops-eng team but not sure if that is being used by users in the AP Org. If not action is taken once the user is dormant for 90 days the inactive repo automation will pick that user up and should remove the user.

MoJ GH Owners

AP GH Owners

We need to know what the Data dept / AP / AS process for when a user leaves the MoJ to make it align with our process

The leavers process form: https://leavers.form.service.justice.gov.uk/

On the leavers form: "For D&A, I’m not sure what to select on that. D&A falls under HQ, but not Central Digital, Engineering, SSIGG or Strategy and Operations as far as I know"

Maybe the leavers form needs updating as well?

Maybe speak with Calum Barnett to see what their process is / spread the word to use the leavers form

NickWalt01 commented 1 year ago

Example where a user has left the Org but no one has informed us and the user still has access to the tooling.

AntonyBishop commented 12 months ago

Closing this story. At present the is no JML process for the AS Org. We have to rely on the automation at the moment for ensuring users are removed from the org.