Week 1 #

There is a proposal for future improvement regarding a pre-onboard meeting, that you can read about in the Appendix A.

Employee Accounts and System Access #

OASIS Open provides IT assets, system access, and communication tools to enable employees and contractors to perform their assigned duties securely and efficiently. All provisioning follows a role-based access model, where system access is determined by the employee’s position and approved by the designated system owner.

IT initiates and coordinates all account provisioning during onboarding, and maintains administrative oversight across all organizational systems to ensure continuity of operations. For complete provisioning details, refer to User Provisioning.

All individuals granted access to OASIS Open systems are required to acknowledge the Organization’s monitoring and acceptable use policies prior to receiving credentials — see Appendix C (U.S.) or Appendix D (EU/Germany).

IT Systems #

Provisioned by Dustin / IT as required. These systems are IT-only and provisioned only when applicable to the employee’s role. See User Provisioning for details.

Financial and Member Systems #

Note: Access to Higher Logic, Github, and Groups.io may not be applicable for all staff members. Access to these systems is dependent on the job function.

Upon approval, IT provisions remaining role-specific accounts at the designated access level.

Salesforce #

Within Salesforce, the new employee must be designated as “OASIS Staff Contact” for each relevant TC individually, as there is no batch method to do this. That designation then pushes to Higher Logic on the next scheduled sync. This step is owned by Cathie and Kelly.

Higher Logic #

For Higher Logic, once the sync completes, Community Admin Access must be assigned for each applicable TC, again one at a time, with Super Admin access granted where appropriate. This step is also owned by Cathie and Kelly.

Github #

For GitHub, the new employee creates a free account and shares their username with Kelly or Claudia, who then grants either Member or Owner access depending on the person’s role at OASIS. Owner access goes to anyone with administrative responsibilities for operations or a project; Member access is the default for everyone else who wants it. Because all orgs and repos are public, staff can follow activity without any permissions at all. This step is owned by Kelly and Claudia.

Groups.io #

For Groups.io, Kelly or Claudia sends the new employee an invitation to each relevant group directly inside the platform. The invitation triggers an email the person must accept, after which their account is automatically populated with the permissions that were set at the time the invite was created. As with GitHub, staff with administrative responsibilities for a project receive elevated access so they can perform their role. This step is owned by Kelly and Claudia.

Marketing #

Orientation #