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
On report creation, a notification is sent to all users with admin rights.
Possible actions following a report:
sent an email to the reported user
suspend the comment or workout of the reported user
suspend the reported user's account.
A suspended user can log in, but access will be limited (TBD, at least allow export request and account deletion)).
A suspended user can appeal the suspension.
TODO:
reports management
report creation on comment, workout and user
mark report as (un-)resolved
store reported object (since it can be updated) ? => in a next version
UI notifications
administration actions
suspend a user account
suspend workout
suspend comment
user warning
administration actions logs
report status update
on user (un-)suspension
on workout (un-)suspension
on comment (un-)suspension
on user warning
handle suspended user
limited access for suspended user
suspended user display
suspended user workouts and comments should not be visible
suspended user is not visible in user directory
notifications from suspended user are not displayed
handle suspended content
suspended workout
suspended comment
allow user to appeal suspensions
account suspension
workout suspension
comment suspension
🔄 user warning
mail notifications
user warning
account suspension
workout suspension
comment suspension
🔄 UI notifications
user warning
workout suspension
comment suspension
appeals for admin
The text was updated successfully, but these errors were encountered:
🚧 First part - WIP 🚧
Users can report:
On report creation, a notification is sent to all users with admin rights.
Possible actions following a report:
A suspended user can log in, but access will be limited (TBD, at least allow export request and account deletion)).
A suspended user can appeal the suspension.
TODO:
The text was updated successfully, but these errors were encountered: