| Both sides previous revisionPrevious revision | |
| misc:committee-onboarding [2025/05/20 19:10] – external edit 127.0.0.1 | misc:committee-onboarding [2025/10/31 01:17] (current) – [Guild webmail] root |
|---|
| It probably doesn't need to be said, but please choose a strong password and/or enable 2FA. Our Vaultwarden is a public instance. | 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 ===== | ===== Guild Emails ===== |
| |
| One thing you should bookmark is the [[https://webmail.guild.bham.ac.uk/|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. | 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) ===== | ===== 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! | 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! |
