You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.
This needs UI and resolvers to handle the requests. The DB schema has user_bans already, so a given user can be banned from a specific Chapter.
Until #814 is in, we can make some progress by implementing the UI for banning users and a resolver to update the DB. After the auth PR is in, we'll need to consider if 'banned' becomes a role that denies you access or if we need to handle banned user access differently.
As an owner I can ban anyone except other owners
As an admin of a Chapter I can ban anyone in a Chapter except other admins
As any other role, I cannot ban anyone
The main thing to check is that requests from unauthorised users fail, but it's also helpful to confirm that the UI reflects their role.
We will also need tests to confirm that banned users can no longer interact with Chapters they are banned from.
The text was updated successfully, but these errors were encountered:
QuincyLarson
changed the title
As an organizer I can ban a participant whom I believe is toxic or who has previously broken my organization's code of conduct.
API: As an organizer I can ban a participant whom I believe is toxic or who has previously broken my organization's code of conduct.
Nov 30, 2019
QuincyLarson
changed the title
API: As an organizer I can ban a participant whom I believe is toxic or who has previously broken my organization's code of conduct.
As an organizer I can ban a participant whom I believe is toxic or who has previously broken my organization's code of conduct.
Feb 11, 2020
ojeytonwilliams
changed the title
As an organizer I can ban a participant whom I believe is toxic or who has previously broken my organization's code of conduct.
As an owner or Chapter admin I can ban a participant whom I believe is toxic or who has previously broken my organization's code of conduct.
May 13, 2022
This needs UI and resolvers to handle the requests. The DB schema has user_bans already, so a given user can be banned from a specific Chapter.
Until #814 is in, we can make some progress by implementing the UI for banning users and a resolver to update the DB. After the auth PR is in, we'll need to consider if 'banned' becomes a role that denies you access or if we need to handle banned user access differently.
The main thing to check is that requests from unauthorised users fail, but it's also helpful to confirm that the UI reflects their role.
We will also need tests to confirm that banned users can no longer interact with Chapters they are banned from.
The text was updated successfully, but these errors were encountered: