Closed NickWalt01 closed 1 year ago
Have cleaned up the allow lists in each Org, manually checked the users have been active and are still members of the Org. Create new list of inactive users for both Orgs. Have used Notify to send out the emails to the inactive users. A list of users that were emailed is in the GH action printout on each repo Notify has a list of the emails that went out.
Restart this task after 2023-05-15
For the AS Org users if they still report as inactive contact them again before running the automation to remove them to see if they still require access and add them to the ignore list
Have sent out a mass bcc email to the AS Org users to remind them to log into GitHub before Monday 15th May in prep for restarting the process
New dormant file added to repo to which users should be removed
Removed these users from GH MoJ Org
Removed these users from the GH AS Org
Freed up 82 seats, some users have been added back already, 5 of these were email accounts that no longer exist closed
Run the Dormant GH Users scripts on the MoJ and AP GH Orgs, get the dormant export file from Tony, add it to the repo, run the script with false, email all the users that are not active, after a week or two, get another Dormant export file from Tony, run the script with false to check for any new users, add their usernames to the allow list temporarily, run the script with true, to remove the users that haven't logged into GH, expect users to email after to be added back into the GH Orgs.
Before removing users post a heads up in the slack channels for AS, Data Engineering, and our channels so that users are aware that we will be removing users soon