...
Internal Onboarding
Samvera
Users: All
Action: Developer or Systems Admin should make a new user as under Application administration→Create new users. Have new user go to digital.sciencehistory.org/login and select "Forgot my Password". They will get an email allowing them to then set their password to whatever they like.
Amazon Web Services
Users: Systems, Developers, Managers
Action: Ask Systems Admin to add user to Amazon Web Services. Go to the IAM (Identity and Access Management) page. Select users, add a user. Current permissions options are Billing (for managers), or AdministratorAccess for Developers or Systems Admins. Other permissions can be added as needed. AdministratorAccess is full access to all systems.
Server Access
Users: Systems, Developers
Action: Ask systems admin to have user provide link to their github public keys. Add that link and the username to the ansible-vault file group_vars/all in our repo. Commit the changes to staging, make sure the user is now on staging, then have a pull request to add that user to production as well. Current process requires user has their github account set up, though it does not need to be in our group when we do this.
External Onboarding
Access to the following platforms are managed by Institute IT staff, who will initiate onboarding procedures. In general, access to these platforms should be specified on HR Onboarding documentation or a help desk ticket.
...
Samvera
Users: ALL
Actions: Scramble Lock the user's password in Samvera. Their account will still exist, useful for certain issues, but cannot be accessed without someone resetting their password via the server.
Method: Have Developers or System Admin follow the instructions in Application administration→ Lock out User
ArchivesSpace
Users: Systems
...