Granting Content Moderation Permission

You can grant content moderation permission at a sub-space or root space level. You should consider having more than one moderator doing moderation wherever you need it. Having just one moderator can mean a bottleneck if that person becomes unavailable. Here's why:

• Content set for moderation will remain unpublished (and invisible to the community) until it is approved.
• The moderation queue for a given context (root space, sub-space, and so on) is visible only to those who are granted content moderator permissions for that context. It's not visible to moderators of other contexts, for example.
• Existing moderation requests can't be routed to another moderation queue (say, from a sub-space to the root space) after they've been queued. They remain in the queue until they're resolved.
• People added as moderators in a given context won't see existing requests in that context's queue — only new requests. That means that requests need to be resolved by whoever was assigned as a moderator when the requests arrived.

You do have a failsafe for new moderation requests, however. New requests are routed in the following order:

1. If content would be moderated at the sub-space level but there's no moderator there, it goes to the root space moderator's queue.
2. If content would be moderated at the root space level but there's no moderator there, it goes to the system administrator's queue.

This applies to new requests only. Existing requests won't be routed to the next queue up. Be sure to see the Content Moderation section of Content Moderator for more on what happens if moderators are deleted from the system.

You grant moderation permission in the admin console. For more on granting content moderation permission, see Managing Space Permission Levels and Managing Space Permissions.