Vanilla's inline moderation controls and member-driven moderation queues means that community managers spend less time on reviewing content and moderation.
Moderators get full in-line controls to affect single or multiple items. They get all of the standard controls like close, announce, split, merge, delete, etc.
Moderators can edit everything in real-time, split, merge and move discussions. Sinking a thread makes it fall down the discussion list even if it gets new comments.
You can read about these in more detail here:
Spam & abuse moderation queues are populated by trusted members, making it easy for moderators to jump in and take care of issues before they become problems.
Online communities each have different social norms, whether prescribed by the community sponsor or that have evolved organically. Allowing the community to self-moderate reduces the workload on moderators and involves the community in deciding what is and is not acceptable behaviour.
Managing Spam & Abuse
See main article on Spam
Curating with Reactions
See main article on curating with Reactions
Consider the Troll Plugin to find out if a user has multiple accounts and learn how to deal with Trolls by making them invisible to other members.
Just like demerit points on a driver’s license, moderators can assign warning points to members who break the rules. Get enough points and you end up in jail. Moderators can add notes to keep track of past activity.
Edit & Delete History
Your moderators have access to a full edit & delete history for all comments, and can even roll-back content to a previous version or undelete deleted content.
Mods and Admins can post a dismissible message that can appear anywhere throughout the site.
In the Dashboard under the Moderation Tab, you’ll be able to lookup users. Clicking on the pencil icon will let you edit a user’s profile information, appoint roles and perform a password reset.
If the Spoof plugin is turned on, Administrators can also spoof this user, i.e. experience Vanilla from that user’s point of view. This is useful when trying to replicate a problem this user might be having.
See main article on adding users here:
If your registration is set to ‘Approval’ you can approve or reject applicants.
Banning a user is an extreme but sometimes necessary action.
A user can be banned by going to their user profile page or via the Dashboard. There are different ways to ban a user:
- By email address
- By username
- By IP address
It it also possible to use wildcards in banning rules, for example to ban all users with email addresses on the .ru domain, you could create an email ban and enter @*.ru as the value. Or you can create an email ban and enter ihatecommunity* as the value and ban all email addresses that have ihatecommunity as part of their email address prefix. Wildcards will also work with IP addresses, for example you can ban all users with an IP addresses prefixed with "111.111.111" by adding an IP-type ban with the value "111.111.111.*".
Caution: Using wildcards in banning rules might result in banning large groups of potential users. We suggest contacting your CSM or Support before creating a wildcard ban.
Using Ranks with limited abilities for newbies is a good way of frustrating banned members that try to register after having been kicked out of the community. When banning a user, you can optionally delete all of the user’s existing posts.
Roles and Permissions
See main article on roles and permissions
Searching for Accounts
To search users in your community you can use either their email address or their username.
A few tips:
- To search for Banned users search "Banned"
- To search for users assigned to a specific role, search for the name of that role. On the Roles & Permissions page you'll see how many users are assigned to each role, this number links you back to the user table where you'll see all users assigned to that specific role.
- Use the % to indicate wildcards. e.g. to search for all gmail accounts use "%@gmail.com"