Just for future reference, my usergroups all use similar wording so it is easier to understand what they do. I use prefixes like this:
"
Allow" enables a permission for selected users (which are usually features like a custom title, thread prefix usage, etc.)
"
Revoke" removes permissions from users (which could be the private conversations, a forum area, a feature such as avatars or attachments, etc.)
"
Access" opens up access to a forum area (such as our "Marketplace" area with classified ads, deals, etc.).
"
[P]" prefix are for the two primary groups: Non-registered/unconfirmed, and Registered.
"
[Staff]" prefix is used to grant staff permissions (moderation features, etc.).
Two special groups I use:
Verified Member: the first handful of posts from new members go into the moderation queue. Once they've had a number of messages approved, they gain "verified" status, which enables instant posts, access to the Off-Topic area, and a few other features we do not enable for new sign-ups.
Suspend: this takes away posting and private conversation privileges, along with avatar and attachment uploading. In essence, they can read the forum but can't do much else. This is triggered by a total of 100 warning points.
What was really confusing at first was how I was setting up permissions--I finally figured out I was OVER-applying permissions everywhere. I've since been enlightened.
Looking at my Revoke groups, for instance: the usergroups that remove access to forum look like they do nothing--they are all set to "Not Set (No)". Instead, the power of this usergroup is applied in the forum permissions instead, where it get the "Never" permission applied (such as, access to Off-Topic). If one of the Revoke groups removes a
feature, though, such as uploading avatars/attachments, those permissions are set to "Never" while all others are left alone.
Groups, I've found, best apply their permissions in small nibbles.
Once I figured that out, I had that same "lightbulb" moment.
