@@ -33,20 +33,46 @@ TODO: can we have buddies? mentors? whatever you call those, the person you ask
...
@@ -33,20 +33,46 @@ TODO: can we have buddies? mentors? whatever you call those, the person you ask
# Offboarding process
# Offboarding process
1. Employee sends letter of resignation to Erin. (Or team lead or Isa)
## Lay off or resignation
Offboarding process right now for Staff that resigns or laid off:
1. Employee sends letter of resignation to HR and team lead.
2. Exit interview is sent (a list of questions replied by email).
2. Exit interview is sent (a list of questions replied by email).
3. Erin checks with employee if they will continue contributing to the project as a core volunteer. (Sometimes we get an answer.)
3. Remove from benefits
4. Employee gets remove from payroll; send reminder to submit all expenses and finish time sheet through last day worked.
4. Return of company property
5. Remove from benefits
5. Send reminder to submit all expenses and finish time sheet through last day worked.
6. Erin creates a ticket to remove employee from people page if no volunteering is happening. (This is the gray area that should be cleaned up by the membership audit.)
6. Remove from payroll
7. Return of company property
7. HR checks with employee if they will continue contributing to the project as a core volunteer. If they volunteer HR needs to ask in which area.
8. Team lead create ticket in TPA to remove permissions (all of them if not volunteering).
8. if they do not volunteer:
9. Remove employee from mailing lists if not continue contributing (but remove from employees list no matter what)
1. HR creates a ticket in tpo/web/tpo to remove employee from people page
2. Team lead create confidential ticket in TPA to remove permissions.
* TODO: what happens when people get "terminated"
3. Remove from all mailing lists and aliases.
4. Handle employee's email
9. if they will volunteer:
1. Team lead create ticket in TPA to remove permissions not associated with the area they will continue volunteering with.
2. Remove from tor-employees mailing lists.
Offboarding process right now for Staff that gets terminated (fired):
1. Team lead create confidential ticket in TPA to schedule the permissions removal
2. Exit interview in person while TPA removes accesses, including mailing lists and aliases
3. Remove from benefits
4. Return of company property
5. Send reminder to submit all expenses and finish time sheet through last day worked.
6. Remove from payroll
7. HR creates a ticket in tpo/web/tpo to schedule employee removal from people page.
8. Handle employee's email.
* TODO: emergency termination
* TODO: emergency termination
* TODO: core-only offboarding procedure
* TODO: core-only offboarding procedure
* TODO: what happens with email: https://gitlab.torproject.org/tpo/tpa/team/-/issues/32558 propose that we auto-reply with a bounce explaining the replacement email, to give agency to the sender, expiry 12 months, remove existing forwards older than 12 months
* TODO Need template for auditing services for removal/changes of accounts when offboarding https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service - maybe instead of a template, make some automation to parse the service.md list and ask the operator to act (or not) on each
Next steps:
- discussion on onboarding/offboarding procedures for core-only contributors. Send a msg to cecylia and roger to be included in this discussion. (gaba)
# what is missing
# what is missing
a systematic process by which people get the accesses they need when they join, and it gets removed when they leave
a systematic process by which people get the accesses they need when they join, and it gets removed when they leave
