-
Notifications
You must be signed in to change notification settings - Fork 9
Description
Context/background
Community members who violate the rules, such as the Code of Conduct, are added to the Blocking List (by Community Managers), which is represented by a checkbox on the Contact page.
When users are added to the Blocking List, it's essential to handle their access to our platforms appropriately. This involves restricting their access to maintain a safe environment for all users.
What needs to be done?
We have discussed the solution before, so here is the all information I gathered:
- Create the Account Suspended Notification for users that are in a Blocking list (to update the integration to simply check if a Contact is on the block list or not).
If a blocked user tries to log in, we then show the "Account Suspended Notification" below:
🚫 Account Suspended Notification.
Looks like your account has been deactivated. If you believe this is a mistake or have any questions, please reach out to us at [email protected]. We're here to help!
Thank you!
Important comments that were made by Team:
- If the community manager decided to uncheck the box, then the user would go back to exactly the state they were before.
- The integration always loads the Contact record first. We can make it so the backend denies processing requests for Contacts where the Blocking List checkbox is checked.
- We should also add some guards on the nestjs side (a "deny requests to load this or that record" check/rule)
- Additionally please also fix the error (mentors/mentees logging in from the wrong location) colour - for both this existing error and the new error (see screenshot below):
Just for your information here are the reports:
Connect profile+ Blocking list: see report
TP profile+ Blocking list: see report
Thank you!
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Status