Internal moderation tools
For user documentation about moderation, see Moderation​
We don't provide any interface for the moderation features yet. To access them you'll need a direct access to the database - through Forest, PgAdmin, DBeaver...etc
All features (submitting expenses, commenting...) will be blocked for this user.
A warning will be displayed at the top of all pages for this user.
User is clearly spamming or trying malicious things on the platform.
Set User.data.features.ALL to false
The specified feature will be blocked for this user.
User has a strange behavior with a feature, or is abusing a specific one. We want to prevent the use of it without blocking access to the others. For example, users having bad language in a conversation - we want to prevent them from commenting, but it's ok to have them creating orders.
Set User.data.features.{FEATURE_NAME} to false
To see a list of all features names, check https://github.com/opencollective/opencollective-api/blob/master/server/constants/features.ts​
Example
Disable access to expenses:
User.data.features.EXPENSES = falseDisable access to conversations:
User.data.features.CONVERSATIONS = false
Please refer to this query to ban users and collectives from the platforms. You'll need to input a list of collective slugs to the query. When banning a user, all the related data (memberships, expenses, comments...etc) are (soft-) deleted. A special flag is set in user.data.isBanned is set to true.
User's email will be locked in database, to that it will be impossible for the user to register with the same email address.
​
