Artemis gives branch moderators a dedicated set of tools to review content, act on rule-breaking users, and keep the mod team organized. This page covers every major workflow available to moderators — from triaging the mod queue to configuring per-moderator permission sets.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/artemis-development-group/artemis/llms.txt
Use this file to discover all available pages before exploring further.
Mod Queue
The mod queue is the central inbox for content that needs moderator attention. Each view is accessible under/r/<branch>/about/.
| Route | What it shows |
|---|---|
/about/modqueue | All reported posts and comments not yet actioned |
/about/reports | Items that have received at least one user report |
/about/spam | Items the spam filter removed automatically |
/about/unmoderated | New posts that no moderator has yet approved or removed |
/about/edited | Posts and comments that were edited after they were approved |
Items in
/about/spam were removed by the spam filter automatically (auto=True). Approving them sets verdict = 'mod-approved' and clears any pending reports.Approving and Removing Content
When you approve a post or comment, Artemis marks itverdict = 'mod-approved' and clears any associated reports. When you remove it, Artemis marks it verdict = 'mod-removed'. The spam action additionally trains the spam classifier.
Review the item
Read the post or comment in context. Use the report reason to understand why it was flagged.
Take action
Click Approve to restore the item, Remove to take it down without spam-training, or Spam to remove it and train the classifier.
Distinguishing and Stickying Posts
Moderators with theposts permission can distinguish their own comments as moderator comments and sticky up to the branch’s maximum allowed sticky posts.
Banning Users
- Temporary Ban (TempTimeout)
- Permanent Ban
A temporary ban uses the
TempTimeout class (in r2/models/bans.py) to schedule an automatic unban via TryLaterBySubject. When the duration elapses, the ban is lifted automatically.Enter the username and duration
Provide a username and a duration (e.g.
3 days). Artemis calls TempTimeout.schedule(victim, duration) to queue the unban.Muting Users
Muting prevents a user from sending modmail to the branch. It does not prevent them from posting. Muted users appear at/r/<branch>/about/muted.
The muteuser and unmuteuser actions are both recorded in the mod action log.
Mod Action Log
Every significant moderation action is recorded in theModAction store (backed by Cassandra with a 120-day TTL) and is viewable at /r/<branch>/about/log.
Logged actions
Content actions
removelink, approvelink, removecomment, approvecomment, distinguish, marknsfw, ignorereports, unignorereports, sticky, unsticky, lock, unlock, setcontestmode, unsetcontestmode, setsuggestedsortUser actions
banuser, unbanuser, muteuser, unmuteuser, addcontributor, removecontributor, addmoderator, invitemoderator, uninvitemoderator, acceptmoderatorinvite, removemoderator, setpermissionsBranch settings
editsettings, editflairWiki actions
wikibanned, wikiunbanned, wikicontributor, removewikicontributor, wikirevise, wikipermlevel, wikipagelistedRule management
createrule, editrule, deleterulesr_id36), the moderator account ID (mod_id36), the action name, an optional target_fullname (the affected post, comment, or user), and an optional details sub-category.
Log entries expire after 120 days due to the Cassandra TTL set on
ModAction.User Lists
All user list pages follow the pattern/r/<branch>/about/:where:
:where value | Who it lists |
|---|---|
moderators | Current moderators and their permission sets |
contributors | Approved contributors (private/restricted branches) |
banned | Banned users, including ban reason and expiry |
muted | Muted users |
wikibanned | Users banned from editing the wiki |
wikicontributors | Users granted wiki editing access |
Moderator Permissions
Artemis usesModeratorPermissionSet to grant moderators scoped access. Each permission is toggled independently; setting +all grants full access.
Available permission flags
Available permission flags
| Permission | What it controls |
|---|---|
access | Manage contributor and banned/muted user lists |
config | Edit settings, sidebar, CSS, images, and AutoModerator config |
flair | Manage user flair, link flair, and flair templates |
mail | Read and reply to moderator mail |
posts | Use the approve, remove, spam, distinguish, and NSFW buttons |
wiki | Manage the wiki and wiki access controls |
Branch Rules
Moderators with theconfig permission can create, edit, and delete the branch’s public-facing rules. Rules are stored in BranchRules (backed by Cassandra) and each rule has a short_name, description, priority, and optional kind (link, comment, or all). Branches may have at most 10 rules. Changes are logged as createrule, editrule, and deleterule in the mod action log.