This is an old revision of the document!
Table of Contents
Committee onboarding
Welcome! If you're reading this you're either joining the CSS committee, or you're nosey. This document is to help you get set up with all the different services we have, and to hopefully ease the burden during handover.
The first step you need to do is to do your committee training, and importantly the GDPR training. Without it, you can't be added to any of our internal services. add link
GitHub
You will be invited to join our GitHub organisation. This hosts the repository for cssbham.com, where you'll need to add a bio for yourself on the committee page. Of course, you can ask someone to do this for you, but it is best you learn to do this yourself.
Google Drive
Once you've completed your GDPR training, let the rest of the committee know and you can be added to our Google Drive. You will need to have your own personal Google account for this. This is where most of our forms are kept, along with meeting notes, photos, planning documents, etc.
You'll want to make yourself familiar with what's in the Drive as there is a lot!
Vaultwarden
Next, you should be added as a user on Vaultwarden. Vaultwarden is our password manager and keeps account credentials for all the different services we use, like the Guild webmail, Canva, Google Drive, etc. You should have received an invitation to your student email, but if you haven't (or it has expired), then let the rest of committee know.
If you want browser or device integration, then you can download one of the many Bitwarden clients.
It probably doesn't need to be said, but please choose a strong password and/or enable 2FA. Our Vaultwarden is a public instance.
Guild webmail
One thing you should bookmark is the Guild webmail. This is a shared inbox for all committee members, and is the primary method of contacting the Guild and our co-ordinator. There is one shared set of credentials for this, and it is stored Vaultwarden.
Infra setup (optional)
Finally, if you're quite technical and are happy to do the sysadmin-y stuff, then ask to have your SSH key added to our server(s). We have a lot of self-hosted applications which will need maintaining, so the rest of this wiki will be of greater importance to you as it contains (hopefully) up to date documentation on what is where. You'll also become responsible for making sure that stuff doesn't fall over, and that this wiki is kept up to date. Good luck!