Would be nice ! I will have a look at the DocHub implementation.

This would mean that we could include restrictions based on the faculty also ?

I think we should make a proper database first (like not a Google spreadsheet) before accessing (and potentially storing) more students data. I may have someone willing to help us with that.

This would mean that we could include restrictions based on the faculty also ?

I'm not sure, maybe

I think we should make a proper database first (like not a Google spreadsheet) before accessing (and potentially storing) more students data. I may have someone willing to help us with that.

Yes! I also wonder if the IT staff can host a db for us at their on-prem. It would resolve some of the problems we keep having when self-hosting

see their PR that implements it: DocHub-ULB/DocHub#192

⚠️ DocHub licensed under an AGPL-v3, we need to take this into consideration if we use their implementation

here's a quick idea of a (flask?) website to link the accounts: https://codepen.io/lucasplacentino/full/QWYYVwB

The registration flow would be:
Connect to website using ULB CAS -> Button to connect to Discord account via OAuth -> Backend links the username and ulb email address in db (maybe other info too?) -> Bot adds roles in the servers they're in

Users should be able to unlink their Discord by themselves (so it should remove their roles in all servers and remove their discord_username entry in the db) .
It would also be nice (GDPR-wise) to allow users to completely remove themselves from the db (and remove roles etc, or ask first to unlink their account).

See:
https://github.com/LucasPlacentino/cas-sso-discord-bot
and
https://github.com/bepolytech/quidam-ulb-bot

Do we want to release it in this repo as a v2 or in a new repo as a new project?