A weekly moderation workflow for Jetonomy communities

Most community managers burn out not because their community is too large, but because moderation has no defined stopping point. Every open tab is a potential pending decision. The queue is never empty. Time spent grows with the community whether you want it to or not.

Jetonomy’s trust level system takes the human out of the obvious-decision path: new accounts are rate-limited until they build a posting history, and any member can flag what slips through. What remains for the community manager is a smaller, bounded set of decisions that genuinely require judgment.

This post is a concrete workflow for keeping Jetonomy moderation to a short weekly routine and having it be enough.

The moderation surfaces you have

Jetonomy’s moderation work happens in three places:

Surface	What lives there	How often to check
Moderation queue	Posts/replies held for review	Daily
Flags tab	Content flagged by members	2x per week
Users screen	Each member’s trust level, reputation and post counts	Weekly

The queue is the daily touchpoint. Everything else is the weekly review.

Day-to-day: the moderation queue

The moderation queue (admin - Jetonomy - Moderation) collects posts held for approval. In Free, that means posts in any space with Require Approval ticked. In Pro, an Advanced Moderation New User Restriction rule can also hold posts from members below a chosen trust level. The actions are fast:

1. Approve - post looks fine, goes live.
2. Spam - marks it as spam in Jetonomy.
3. Trash - not spam but not appropriate - move it to the trash.

Clearing the queue is quick if you are making fast calls. The decisions that slow you down are the borderline ones - usually a real member asking a low-quality question. The right call here is almost always Approve with a note suggesting they improve the question, not Trash. Trashing posts from legitimate members causes churn.

One configuration decision that keeps the queue manageable: hold posts only where the risk is highest. Free: tick Require Approval only on your highest-risk spaces (public-facing, heavily indexed). Pro: a New User Restriction rule holds posts below a chosen trust level, so established members are never held. Internal or gated spaces can publish immediately - the newcomer rate limits cover them.

Twice a week: flag review

When members flag content, it enters the flag queue. This is different from the moderation queue - flags are typically from legitimate members who spotted something wrong in published content, not pre-publication review.

Flag review procedure:

1. Open admin - Jetonomy - Moderation and switch to the Flags tab.
2. For each flagged item: read the content, read the flag reason.
3. Valid: the flag is right. The content moves to the trash.
4. Dismiss: the content is fine, the flag was wrong or overly cautious.
5. For genuinely contested items, leave the flag open while you take more time, or consult a second moderator.

The flag queue should move fast. If individual flags are taking you a long time, either the flags are genuinely contested (which is unavoidable) or your community rules are not clear enough for members to apply them consistently.

A healthy flag queue is mostly quick calls, with only the occasional one that needs thought.

Weekly review: trust levels

From admin - Jetonomy - Users, filter by trust level. The list shows each member’s trust level, reputation and post counts, so you can see who has been climbing.

What to do with this list:

• Check the member’s recent posts. Is the pattern genuinely high-quality? Or are they gaming - posting frequently but with low signal? Reputation from upvotes and accepted answers is part of the trust calculation, and reported or removed posts cost reputation, which makes gaming hard. But a quick scan confirms the system is tracking what you expect.
• Demote a member if needed. If a high-trust member has turned adversarial, lower their level so the new-member limits apply again. Rare, but worth a glance.
• Look for members who should become moderators. Trusted members (level 3) with a long track record of helping others are candidates for a moderator role. This is a deliberate decision - levels 4 and 5 are granted by an admin, and moderation powers come from the role you assign, not the level.

Skip weeks where nothing notable is on the list.

Weekly review: patterns and problem users

This is the judgment layer that the trust system cannot handle automatically. Work from the Flags tab and the Users screen:

• Repeated low-quality posts from the same member. Pattern detection catches what single-post review misses.
• Members who consistently generate flags. Even if individual posts are borderline-acceptable, a member who keeps drawing flags is consuming disproportionate moderation bandwidth.
• High-quality contributors to acknowledge. Who answered the most questions this week? A public thank-you or a badge nudge (Pro) costs nothing and keeps contributors engaged.

The standard actions:

Pattern	Action
Repeated spam despite the approval queue	Ban the member, site-wide or from one space
Pattern of borderline rule-breaking	Private message with specific examples
Consistent off-topic posting	Reply on the posts, link to the right space
High contributor needing recognition	Public reply or badge (Pro)

The decisions you do not have to make

The goal of the trust level system is to remove the obvious decisions from your plate. Specifically, with trust levels correctly configured:

• Spam from new accounts - newcomer rate limits slow it down, Akismet catches the obvious ones, and anything held for approval waits in the queue for your quick pass.
• Spam that slips through - any member can flag it, and moderators are notified of new flags, so you are not hunting for it.

If you run Pro’s New User Restriction rule and find yourself approving a steady stream of good posts from members who have clearly found their feet, the trust level in the rule or the thresholds themselves may be too conservative for your community. Adjust the thresholds on the Trust Level Thresholds card under admin - Jetonomy - Settings - Permissions.

The full weekly schedule

When	Task
Every morning	Clear the pending queue
Tuesday, Friday	Flag review
Friday	Users screen, problem-member review
Friday	Write a short community note or reply to a standout post

The morning queue check is the only daily task and it should stay short. If it is taking longer, either volume is growing (scale the morning check to twice a day) or the threshold for pending is too aggressive (loosen it).

Scaling beyond this workflow

This workflow suits a community that a single community manager can look after alone.

When volume outgrows it, the right move is not to hire a full-time moderator immediately - it is to lean on the members you have already watched climb the trust levels. Identify your most active Trusted and Leader members and explicitly invite them to act as volunteer moderators. Give them a moderator role, since trust alone does not carry moderation powers, and a communication channel with you.

Jetonomy’s moderation is designed so the community handles the volume and you handle the exceptions. The workflow above is the minimum structure that makes that design work.