Production Release - sequence of events for implementation day

Issue: we can't have people on the old account at the same time as they are invited to the new one and given the new KC group.

- Choose a quiet time/day to make the flip (Debbie can advise)

Plan:
Debbie
- [ ] 1. Remove her from old BCROS staff account -14752
- [ ] 2. Remove her staff roles from KC
- [ ] 3. Invalidate membership row for the staff account
- [ ] 4. Create GOVM account with Debbie as first admin
- [ ] 5. Debbie accepts invite and enter GL coding
Per staff member:
- [ ] 1. Remove individual from old BCROS staff account
- [ ] 2. Remove individual's staff roles from KC
- [ ] 3. Invalidate membership row for the staff account
- [ ] 3. Debbie invites staff member to new account
- [ ] 4. Pay dev adds new KC group to the staff user

Contact centre BCOL HD acct list below:
https://docs.google.com/spreadsheets/d/1lmCI6dkTjixmToq7AWsfsB8fbFWiQ0TluAgpb5M3ln8/edit?gid=1837233806#gid=1837233806

Maximus acct list:
https://docs.google.com/spreadsheets/d/1IRNO2N_CpOReEFN_P4iFczsqz9_oAkuaDIS6w5TyQDQ/edit?gid=0#gid=0

Start with the checklist in this issue and review the linked BCOL HD and Maximus account lists before the planned production change. Confirm the sequence with Debbie and the team; done means each old account, staff role, membership row, new invitation, and KC group is handled for Debbie and every staff member.

Written by the indexing model from the issue text.