-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboarding Alejandro Silva #771
Comments
Created a google account for Alejandro: [email protected] |
Added to the relevant google groups. |
Sent invites for the corresponding GH teams. |
Added to corresponding Slack groups. |
Sent a link to the 2i2c team drive. |
@damianavila I assume you'll want Alejandro to have access to FreshDesk? If so, I can request another seat licence for him. |
Indeed, @jmunroe, I would appreciate it if you could do it for me 😉, thanks! |
Hey @AIDEA775! You should have received a bunch of emails about new accounts on GCP and AWS. You will need to accept the invitations there and change a few passwords after your first login. Also, can you please create accounts on the platforms below and share the username for each of them once they are ready so I can invite you in the relevant groups? Thanks.
|
I've created an account on FreshDesk for @AIDEA775 -- he should have an activation email sent to [email protected] |
And we have a shared zoom account (see bitwarden for password) across all of 2i2c. |
I created accounts in the following services with my email at 2i2c:
Thanks you @GeorgianaElena! |
Thank you very much @AIDEA775! You should have received a few more invitations today too. @damianavila, I believe I covered all of the things that I had privileges to grant access to. Also, I've updated the top comment with the actions that I've took. |
Welcome @AIDEA775! It's great to have you on the 2i2c team. |
Onboarding checklist
The Onboarding champion should follow the checklist below to onboard a new team member. Don't hesitate to delegate some actions to others (e.g. if another person needs to give access to an account because you aren't able to).
First steps
Accounts
Create new accounts and share their account name:
Create 2i2c accounts and add to team accounts:
Communication
Documentation
Cloud engineering permissions
This is only relevant for others that are joining our Engineering team.
Add to 2i2c hubs as an admin
Add to appropriate GCP organizations and projects
2i2c.org
's admin group2i2c.org
s engineering groupcloudbank
meom-ige
callysto
pangeo-hubs
Add to appropriate AWS projects
2i2c-sandbox
(Grants SSO access at https://2i2c.awsapps.com/start#/)carbonplan
openscapes
nasa-veda
Add to appropriate Azure projects
utoronto
see Get all 2i2c engineers access to UToronto Azure portal #386Add to quay.io 2i2c team
NameCheap administration privileges to
2i2c.org
and2i2c.cloud
Roles
External
Wrap up
#general
Slack channel about our new team memberThe text was updated successfully, but these errors were encountered: