Default template

Yearly Transition Steps

By pdhyani.

Last edited by ericlau. Created .

The following is a list of things that should happen every year when leadership transitions to make sure we don’t lose access to or forget any technology.

  1. Add the new leadership to the password manager and make sure they can access the necessary vaults of passwords. Read more here
  2. Renew our MCommunity groups for email forwarding so they don’t expire (read more). Then, add the new leadership to the respective MCommunity groups (read more). Finally share this link on setting up email filtering to the new leadership.
  3. Add the new MOEs and Big 3 as admins to the Newspack site. Read more here
  4. Add the new MOEs and Big 3 to the Newspack slack channel. Read more here
  5. Ensure the new MOEs have access to tmdwebystem@gmail.com (the password should be in the password manager)
  6. New MOEs should be added to our AWS if they have not been added already. Read more here
  7. New MEs and Big 3 should be aware of and read through how to use Library. Here is documentation on using Library. Check that MEs have access to edit their team’s documentation.
  8. The new DME and MOEs should read through and become familiar with all of the content under Technology in Library here.
  9. The new MOEs (and other MEs) should be made workspace administrators in Slack
  10. The new Big 3 should be made workspace owners in Slack
  11. The new MOEs should be made owners on GitHub
  12. The new MOEs should create a new listserv to manage Google Calendar invites and emails
  13. The new MOEs and the DME should be invited to Google Analytics and Google Search Engine

This is a living document, so please continue to add steps here every year!