Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| misc:committee-onboarding [2025/05/20 19:10] – external edit 127.0.0.1 | misc:committee-onboarding [2026/03/22 15:53] (current) – [Guild Emails] root | ||
|---|---|---|---|
| Line 29: | Line 29: | ||
| It probably doesn' | It probably doesn' | ||
| - | ===== Guild webmail | + | ===== 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 either Outlook for Windows or Outlook Web, despite sending the email from the shared email, the item will be placed in the individual users' " | ||
| + | |||
| + | ===== Guild Admin ===== | ||
| + | |||
| + | The guild uses a provider called MSL to handle back-end for essentially all guild systems - including societies. Once you are recognised as a committee member (that is to say, when you've completed the guild canvas training and the guild have granted you access) you'll be given access to the admin panel for the society. To access this, a " | ||
| + | [[https:// | ||
| + | |||
| + | MSL also have a basic set of help pages that detail the different functions you will have access to - this can be found here: | ||
| + | [[https:// | ||
| + | |||
| + | A large number of the widgets listed on the MSL support pages are not actually accessible to us - for the simple reason that the guild doesn' | ||
| - | One thing you should bookmark is the [[https:// | ||
| ===== 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, | 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, | ||