Appendix #
Notes, supplementary information, and IT procedure references for offboarding staff.
Platform-Specific Notes #
Salesforce #
When a staff member departs, their Salesforce record should be updated to remove the “OASIS Staff Contact” designation for each TC individually. This change propagates to Higher Logic on the next scheduled sync. This step is owned by Cathie and Kelly.
Higher Logic #
Following the Salesforce sync, confirm that the departed employee’s community access has been removed. Any TC-level community admin or super admin access must be manually revoked. This step is owned by Cathie and Kelly.
GitHub #
The departed employee’s GitHub org membership should be removed or downgraded. If the person held Owner access, confirm that no repos or org settings were altered on their way out. This step is owned by Kelly and Claudia.
Groups.io #
Remove the departed employee from all relevant Groups.io groups directly inside the platform. If the employee held elevated permissions (Owner or Moderator), reassign those roles before removing the member. This step is owned by Kelly and Claudia.
IT Procedure Appendixes #
The following appendixes provide detailed procedures for IT-specific offboarding tasks. Each appendix is maintained by the IT Director and should be referenced alongside the main offboarding checklist.
| Appendix | Title | Summary |
|---|---|---|
| A | Google Workspace Account Suspension & Data Archival | Account suspension, Drive transfer, Takeout archival procedure |
| B | IT Data Retention Schedule | Minimum retention periods for all IT-managed data |
| C | JumpCloud MDM Device Unenrollment & Wipe | Pre-wipe verification, unenrollment, and wipe procedure |
| D | Obsidian Security Post-Departure Review | Post-departure security review checklist |
| E | 1Password Deprovisioning | Vault transfer, account removal, credential rotation |
| F | Core Platform Deprovisioning Reference | System-by-system deprovisioning notes for all 15 platforms |