...
The Head of Engineering (HoE) should be signing into Mongo using the HoE email (head-of-engineering@utdnebula.com) provided through the Google Workspace for the organization. The new HoE HoE Google Group. The new HoE can gain access to this email once they are *******added to the HoE group, and then they can sign into Mongo here. This will require transferring the password and 2FA, but after doing so the account transfer is complete. During this process the existing HoE can use the time to dive into why we use Mongo and how to manage the permissions for this application.
Treasurer
Transfer the billing account for the Mongo Atlas organization
Explain how billing works for Mongo
The Treasurer should be signing into Mongo using the Treasurer email (treasurer@utdnebula.com) provided through the Treasurer Google Group. The new Treasurer can gain access to this email once they are *******added to the Treasurer group, and then they can sign into Mongo here. This will require transferring the password and 2FA, but after doing so the account transfer is complete. During this process the existing Treasurer can explain how all Mongo billing is done through ***Google Cloud Marketplace.
Lead of API
Transfer the Lead of API account for the Mongo Atlas organization
Explain all the data collections
Remove all old access keys & explain how to set up new ones
The Lead of API should be signing into Mongo using the Lead of API email (lead-of-api@utdnebula.com) provided through the Lead of API Google Group. The new Lead of API can gain access to this email once they are *******added to the HoE groupLead of API group, and then they can sign into Mongo here. This will require transferring the password and 2FA, but after doing so the account transfer is complete. This transfer process is extremely important as the Lead of API is currently the manager of all data within our Mongo Atlas organization, so it is important the new lead becomes very familiar with it.