Differences

This shows you the differences between two versions of the page.

--- misc:committee-onboarding [2025/03/29 12:43] – created root
+++ misc:committee-onboarding [2025/10/31 01:17] (current) – [Guild webmail] root
@@ Line 1: / Line 1: @@
 ====== 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. [[https://canvas.bham.ac.uk/enroll/LWGCTK]]
+===== GitHub =====
+You will be invited to join our [[services:github|GitHub organisation]]. This hosts the repository for [[https://cssbham.com|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 [[services:google-drive|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!
+===== Google Calendar =====
+In addition to the Drive, you'll also be given access to three different calendars within CSS - one is the main event calendar that is visible to everyone, but you'll be able to alter the dates and times on it now. The other two are the internal and deadlines calendars, which will only be visible to you, but are immensely useful for tracking when things are taking place. The internal calendar can be used for tracking university holidays, provisioned event dates and important EDI event dates, whilst the deadlines calendar can be used for publicity deadlines, grant deadlines or anything else with a strict timeline.
+If you don't often use calendar apps and aren't sure you'll be able to reliably check it, Google Calendar (and other calendar apps) can have a widget set up on your phone so that when you open your phone screen, you'll be able to see the calendar at a glance.
+===== Vaultwarden =====
+Next, you should be added as a user on [[applications:vaultwarden|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 [[https://bitwarden.com/download/|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 Emails =====
+Previously, we had a single login for a shared mailbox, which was only accessible via an online portal. CSS has now been migrated to M365, meaning each individual committee member gets their own M365 account, email address and inbox, which is then subsequently given access to a shared mailbox. All emails should still be sent through the shared mailbox for consistency.
+There is currently an issue where if an email is sent from the shared inbox, the item will be placed in the individual users' "Sent" folder, rather than the sent folder on the shared inbox. This is a known issue with M365 and can be fixed in configuration by the Guild, which we are still waiting for them to do. If an email is important, committee members are recommended to copy the email from their own sent folder into the shared sent folder as well for prosperity.
+===== 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!