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
Since proposals are user-generated content there's a chance inappropriate content might be published at Decidim. In order to detect this kind of content, we should let users report proposals that might be offensive or irrelevant.
Reporting a proposal
Users can report a proposal only one time. When reporting, users will see a model window with these options to choose as a reason:
Spam: This proposal contains clickbait, advertising, scams or script bots.
Abusive/Offensive: This proposal contains racism, sexism, slurs, personal attacks, death threats, suicide requests or any form of hate speech.
Does not belong here: This proposal contains illegal activity, suicide threats, personal information, or something else you think doesn't belong on %{organization name}.
Users should view a message telling them that the content has been reported and it will be reviewed by an admin. Admins & process admins should receive an email telling them the proposal has been reported.
Reviewing a reported proposal
When a proposal is reported three times it gets hidden and admin & process admins receive an email notifying them about it.
Admins can list all reported proposals (either with a filter at proposal index or a special section), a reported proposal is any proposal with one or more reportings. The reason(s) about the reporting should also be listed.
Admins can un-report a reported proposal. It will reset the reporting counter in that proposal and it will be public again.
Admins can hide a reported proposal even if it hasn't reached the reporting limit.
A user that reported a proposal can't report again in the future even if an admin has unreported it.
Don't use a default scope to hide proposals, add a visible scope (or similar) to each use case were we load proposals (ProposalSearch, ProposalsController or linked proposals in other resources)
When a proposal reaches the report limit, use a separate date time column to hide it (hidden_at maybe?)
Use Decidim.config to store the configuration about the number of times a proposal has to be flagged in order to be hidden (3 by default).
The text was updated successfully, but these errors were encountered:
This is a Feature Proposal
🎩 Description
Since proposals are user-generated content there's a chance inappropriate content might be published at Decidim. In order to detect this kind of content, we should let users report proposals that might be offensive or irrelevant.
Reporting a proposal
Users can report a proposal only one time. When reporting, users will see a model window with these options to choose as a reason:
Users should view a message telling them that the content has been reported and it will be reviewed by an admin. Admins & process admins should receive an email telling them the proposal has been reported.
Reviewing a reported proposal
📌 Related issues
📋 Additional Data
visible
scope (or similar) to each use case were we load proposals (ProposalSearch, ProposalsController or linked proposals in other resources)hidden_at
maybe?)Decidim.config
to store the configuration about the number of times a proposal has to be flagged in order to be hidden (3 by default).The text was updated successfully, but these errors were encountered: