CSS Wiki
Page
  • Show page
  • Old revisions
  • Backlinks
  • New page
  • New folder
  • Back to top
    • Site
  • Recent Changes
  • Media Manager
  • Sitemap
    • User

    Page tools

  • Show page
  • Old revisions
  • Backlinks
  • New page
  • New folder
  • Back to top

    • Site tools

  • Recent Changes
  • Media Manager
  • Sitemap

    • User tools
    You are here: start » misc » committee-onboarding

    Differences

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

    Link to this comparison view

    Both sides previous revisionPrevious revision
    Next revision    		Previous revision
    misc:committee-onboarding [2026/03/22 15:52] – [Guild Emails] rootmisc:committee-onboarding [2026/05/16 16:16] (current) – root
    Line 3: Line 3:
     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. 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]]+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/MJ4DCJ]] 
     + 
     +===== Teams ===== 
     + 
     +We have a Teams chat (note chat, not a Teams team or a Teams channel, a chat) with all committee + our school contact. This should generally be the way to communicate with the school for admin things but email is also good. If handover has somehow gone so horrifically wrong that committee aren't sure who the school contact is, the student experience team can direct you - csstudentexperience@contacts.bham.ac.uk.
      
     ===== GitHub ===== ===== GitHub =====
    Line 27: Line 31:
     If you want browser or device integration, then you can download one of the many [[https://bitwarden.com/download/|Bitwarden clients]]. 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.+It probably doesn't need to be said, but please choose a strong password and enable 2FA. Our Vaultwarden is a public instance and is configured so anyone without 2FA enabled will not be able to access it. 
      
     ===== Guild Emails ===== ===== Guild Emails =====
    Line 33: Line 37:
     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.  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' "Sent" folder, rather than the sent folder on the shared inbox. This is a known "feature" of 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 all emails from their sent folder to the sent folder on the shared inbox, but this is especially important for important or urgent emails so all of committee can monitor and respond if needed. +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' "Sent" folder, rather than the sent folder on the shared inbox. This is a known "feature" of M365 and can be fixed in configuration by the Guild, which we are still waiting for them to do. Committee members are recommended to copy //all// emails from their sent folder to the sent folder on the shared inbox, but this is especially important for important or urgent emails so all of committee can monitor and respond if needed.  
     + 
     +When a committee handover takes place, the current committee member with access to the M365 account needs to login, remove all 2FA methods and then hand over the username and password to the new committee member. The new committee member will then be prompted to setup their own 2FA when they login for the first time. 
      
     ===== Guild Admin ===== ===== Guild Admin =====
    Line 44: Line 50:
      
     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't feel like it. I (Matty) have been bothering them about this for years and nothing has changed, so take that as you will.  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't feel like it. I (Matty) have been bothering them about this for years and nothing has changed, so take that as you will. 
     +
     +===== Discord Dev Team =====
     +
     +[[applications:tex-bot:start|TeX Bot]] is owned by a Discord Developer Team. Anyone who wants to do discord bot related admin stuff will need to be added to this team. It's very rare that we ever actually need to make changes to the config on here, but it's mentioned here just because it's easy to forget about and if you do, reaching out to whoever still has access could prove challenging. 
      
      
    misc/committee-onboarding.1774194761.txt.gz · Last modified: by root