We're working with community non-profits who have a Host Home or empty bedrooms initiative to develop a workflow management tool to make the process scalable (across all providers), reduce institutional bias, and effectively capture data.
We need to have a checklist of items to do when a design team member onboard and offboards so that the process can be consistent and fast.
Date Updated
date created: 2022-04-15
date updated: 2022-04-15
(insert date you created this issue and keep updating the date each time the org template change are integrated)
Action Items
[ ] Check to see if the org template for this process has new steps in it, and if it does, update this issue and its template with content and add the last date you updated the template below
[ ] Copy template to comment below
[ ] Add name of person
[ ] Check off as done
#### Onboard
- [ ] Slack channel membership
- [ ] ```#home-unite-us```
- [ ] ```#home-unite-us-dev```
- [ ] ```#home-unite-us-fe-devs```
- [ ] Add to Google calendar invites
- [ ] TUESDAY - All-team meeting
- [ ] TUESDAY - Dev team meeting
- [ ] Add to team page on Wiki (Does Not Currently Exist)
- [ ] Google Drive
- [ ] as Contributor if team member
- [ ] as Manager if lead
- [ ] Roster
- [ ] Send link
- [ ] Team member adds themselves
- [ ] Confirm they have filled out all the fields with white headers
- [ ] Check for Public and note in roster
- [ ] Update the Dark Gray column to M or L depending on if they are a
- [ ] team member (M)
- [ ] team Lead (L)
- [ ] Update the Dark Gray column for Google Drive access to
- [ ] Contributor if they are a member
- [ ] Manager if they are a lead.
- [ ] GitHub
- [ ] Add to team write team
- [ ] Change membership to maintainer if lead
- [ ] Add to read vault
- [ ] Change membership to maintainer if lead
- [ ] Update the Dark Gray columns in the roster with the `write` permission granted
- [ ] Figma
- [ ] invite
- [ ] acceptance
- [ ] 1password
- [ ] invitation
- [ ] acceptance
- [ ] add to vaults
- [ ] Home Unite Us (if needed)
- [ ] Zoom vault (if lead)
- [ ] Add to email address(s)
- [ ] homeuniteus-ux@hackforla.org (if lead)
- [ ] Social Media Accounts with role assignment
- [ ] Facebook (TBD)
- [ ] If lead, train how to
- [ ] login to team account
- [ ] setup chrome shortcut for adding to desktop
- [ ] use zoom spreadsheet, vault and accounts
- [ ] calendar invite
- [ ] Update the hackforla.org website team
#### Offboard
- [ ] Remove from Google calendar invite
- [ ] TUESDAY - All-team meeting
- [ ] TUESDAY - Design team meeting
- [ ] WIKI
- [ ] move to new place on team page
- [ ] 1password setup
- [ ] remove from team vaults
- [ ] Home Unite Us
- [ ] Zoom vault
- [ ] Google Drive
- [ ] remove from drive, note in roster
- [ ] Roster
- [ ] mark as inactive
- [ ] GitHub
- [ ] unassign them from any issues they are assigned to (see tab in roster)
- [ ] check to make sure they are on the base team, and remove from write team
- [ ] update the Dark Gray column in the roster to indicate they have `read` permission instead of `write`
- [ ] Figma
- [ ] remove from team
- [ ] Help them delete the desktop shortcut to email address if they made one.
- [ ] Remove from email address(s)
- [ ] homeuniteus-ux@hackforla.org
- [ ] Remove from Social Media Accounts with role assignment
- [ ] Facebook (TBD)
- [ ] Update the hackforla.org website team
Overview
We need to have a checklist of items to do when a design team member onboard and offboards so that the process can be consistent and fast.
Date Updated
date created: 2022-04-15 date updated: 2022-04-15 (insert date you created this issue and keep updating the date each time the org template change are integrated)
Action Items
Resources/Instructions
Forward emails to team members
org template updated 2022-02-23 Changelog
Other onboarding issues