Conservative AI triage for XenForo approval queues
AI Rules Moderation helps XenForo forum owners reduce moderation workload by checking new and updated supported public text content against their own plain-language rules.When content clearly appears to breach those rules, it is moved into XenForo’s built-in approval queue with a moderation reason for staff review. Your moderators remain in control. The add-on does not automatically delete content, ban users, warn users, punish users, publicly mark users, or make final moderation decisions.
The short version
| Area | Details |
|---|---|
| Main purpose | AI-assisted rule-violation triage for XenForo |
| Action taken | Moves clear likely violations to XenForo’s approval queue |
| Final decision | Always made by human moderators |
| Trial | 14 days, up to 100 moderation checks |
| Trial billing | Payment method required; billing starts only if not cancelled before trial ends |
| Paid access | $25 USD per year, including 1,000 moderation checks |
| Additional checks | Optional $5 USD top-ups for 500 checks |
| Auto top-ups | Disabled by default; can be enabled with an annual cap |
| Supported content | Posts, threads / first posts, profile posts, profile post comments |
| Not supported | Private conversations, images, files, media, attachments, old-content bulk scanning |
| API access | Dedicated custom XenForo API scope only: ai_rules_moderation:write |
| AI processing | Hosted moderation backend using OpenAI’s API Platform |
| Training | Customer forum content is not used by the service or OpenAI to train AI models |
| Visible branding | No end-user branding |
| Requirements | XenForo 2.1.0+, PHP 7.2.0+, active trial/subscription, outbound HTTPS |
| Version behaviour | XenForo 2.3+ uses native webhooks. XenForo 2.1–2.2 uses an add-on compatibility driver. Scope controls require XenForo 2.3.8+. |
What problem it solves
Some forum moderation problems are not well handled by keyword filters.AI Rules Moderation was originally built for a stock and crypto community dealing with sophisticated spam, manipulation attempts, self-promotion, personal attacks, and high-emotion discussion during volatile market periods. The problem was not simply “bad words”. The problem was context. Blunt filters missed important issues, created false positives, or treated normal adult disagreement as if it needed action.
This add-on is for forum owners who want faster identification of clear rule-breaking content without handing final moderation authority to AI.
What it does — and does not do
It does
| Capability | What happens |
|---|---|
| Checks supported new or edited content | Eligible public text content is checked after creation or update |
| Applies your rules | Rules are written by the admin in plain English |
| Uses XenForo’s normal workflow | Flagged content goes to the built-in approval queue |
| Gives staff a reason | Moderators see why the content was flagged |
| Keeps a local audit trail | Admin CP audit log records moderation callback outcomes |
| Allows scoped moderation where supported | Scope can be narrowed by node, user group, and content type where scope controls are available |
| Keeps your forum server lightweight | AI processing runs through the hosted moderation backend |
It does not
| Limitation | Why it matters |
|---|---|
| Does not automatically delete content | Prevents irreversible AI enforcement |
| Does not ban, warn, punish, or publicly mark users | Staff remain responsible for enforcement |
| Does not scan private conversations | Avoids private-message monitoring |
| Does not scan images, media, files, or attachments | Current scope is text-based supported XenForo content |
| Does not bulk-scan historical content | It is event-based, not a retroactive crawler |
| Does not replace moderators | It assists human review rather than making final decisions |
| Does not use broad XenForo API permissions | Uses only the add-on’s custom API scope |
How it works
- Install the XenForo add-on using the normal XenForo add-on process.
- Open the AI Rules Moderation setup page in the Admin CP.
- Enter your forum details and write your moderation rules in plain English.
- Choose moderation scope where supported by your XenForo version: nodes, user groups, and content types.
- When eligible supported content is created or updated, the add-on sends the moderation event to the hosted moderation backend. On XenForo 2.3+, this uses XenForo’s native webhook system. On XenForo 2.1–2.2, this uses the add-on’s compatibility driver.
- The backend checks the author’s submitted message against your rules.
- If the content clearly appears to breach your rules, the add-on moves it into XenForo’s approval queue.
- Staff review the moderation reason and make the final decision using XenForo’s normal moderation tools.
Built for cautious trials
AI Rules Moderation is deliberately conservative.The goal is not to punish users automatically. The goal is to surface clear likely rule violations sooner, inside the moderation workflow your staff already use. If the AI is unsure, the intended behaviour is to avoid acting on borderline cases, ordinary disagreement, or heated discussion that does not clearly breach your written rules.
This matters because automated moderation is risky when it becomes opaque, overconfident, or detached from human context. The Santa Clara Principles emphasise understandable rules, transparency about automated moderation, explainability, and human review. Australian AI governance guidance also stresses accountability, human oversight, monitoring, and avoiding overreliance on automated outputs.
Best suited to
AI Rules Moderation is best suited to forums where moderation is:| Forum type | Why it may help |
|---|---|
| Finance and trading forums | Spam, manipulation, self-promotion, and high-emotion debate can be context-dependent |
| Gaming communities | High-volume public posting and recurring behavioural rules |
| Marketplace communities | Promotions, scams, disputes, and off-platform solicitation |
| Political discussion forums | Heated debate where context matters |
| Large hobby and enthusiast forums | Repetitive moderation workload |
| Fast-moving public discussion communities | Staff may not see clear issues quickly enough |
| Communities with detailed rules | Plain-language rules can be applied consistently as a first-pass triage layer |
Not suited to
This is not the right add-on if you need:| Requirement | Why this add-on is not a fit |
|---|---|
| Automatic bans | It does not ban users |
| Automatic warnings | It does not warn users |
| Automatic permanent deletion | It queues content for review instead |
| Private conversation scanning | Private conversations are not scanned |
| Image, file, media, or attachment moderation | Those are not currently supported |
| Bulk scanning of old content | It only checks eligible new or updated content |
| AI making final decisions | Human moderators make the final decision |
Moderation scope
AI Rules Moderation currently supports:| Content type | Supported |
|---|---|
| Posts | Yes |
| Threads / first posts | Yes |
| Profile posts | Yes |
| Profile post comments | Yes |
| Private conversations | No |
| Images / files / media / attachments | No |
| Historical bulk scanning | No |
Moderation scope controls can be used to limit checks by node, user group, and supported content type where XenForo’s native scoped webhook dispatch is available. XenForo 2.3.8 or newer is required for those scope controls.
On XenForo 2.1–2.2, the add-on remains installable and functional using its compatibility driver, but scope controls are unavailable and broad supported-content behaviour is retained.
On XenForo 2.3.0 to 2.3.7, the add-on remains installable and functional using native webhooks, but scope controls are unavailable and broad webhook behaviour is retained.
Important scope details
| Scope option | Behaviour |
|---|---|
| Nodes | Applies to supported content with a forum/node context, such as posts and thread first posts |
| Profile posts | Do not have a normal forum node context |
| User groups | If narrowed from All, selected groups act as a strict allowlist |
| Multi-group users | A user is checked only if every primary and secondary group they belong to is selected |
| Trusted groups | Leave a group unselected to skip users who belong to that group |
| Scoped-out content | Does not consume credits where scoped dispatch is supported |
| Older XenForo versions | On XenForo 2.1–2.2 and XenForo 2.3.0–2.3.7, scope controls are unavailable, so supported content remains broadly eligible for checks |
API access and security posture
The add-on creates a dedicated XenForo API key using only the add-on’s own custom API scope:ai_rules_moderation:writeIt is not a super-user key and it is not a general-purpose XenForo API key. No standard XenForo API scopes are granted for posts, threads, users, attachments, conversations, nodes, alerts, authentication, or general administration.
In practical terms, the API key exists so the hosted moderation backend can return a moderation decision to your XenForo installation, allowing the add-on to move clearly flagged content into the approval queue and record the moderation outcome.
Admins who want to fully revoke callback access can remove, disable, or regenerate the API key from XenForo’s API key area. Uninstalling removes the add-on’s local tables and disables the XenForo-side integration where applicable, but the API key and webhook/integration records are deliberately not silently deleted so the integration artefacts remain visible for transparency and auditability.
Hosted processing and data handling
AI Rules Moderation requires the hosted moderation backend to function. The hosted service is operated by The Stock Exchange Forum. Payments are handled by Stripe, AI processing may be handled by OpenAI, and security / traffic handling may involve Cloudflare.For moderation classification, the backend may use:
| Data type | Purpose |
|---|---|
| Forum domain / URL | Identify the forum and service account |
| Forum name and description | Provide community context |
| Saved moderation rules | Define what should be checked |
| Supported content type and ID | Identify the submitted content |
| Author’s submitted message | Classify the actual text |
| Related forum, thread, or sub-forum context where available | Improve contextual interpretation |
Where native scoped webhook dispatch is available, content outside the configured moderation scope is not sent for AI classification. On supported XenForo versions where scope controls are unavailable, supported public text content remains broadly eligible for checking.
Storage and retention summary
| Item | Handling |
|---|---|
| Payment card details | Handled by Stripe, not stored by the add-on |
| Service records | Forum/account, subscription, billing identifiers, credit totals, rules, top-up settings, and operational records may be stored |
| Successful production checks | Not retained as saved hosted service execution history |
| Errored service runs | May be retained temporarily for troubleshooting and pruned after up to 7 days, subject to normal operational requirements |
| Short-lived cache | Stores forum domain, content ID, and a hash of message content |
| Permanent archive of forum posts | Not intended or created by the hosted moderation service |
| Local audit trail | XenForo audit log may record outcomes and moderation reasons inside your own installation |
OpenAI’s own API data controls state that API data is not used to train or improve OpenAI models unless the customer explicitly opts in, and that abuse-monitoring logs may contain customer content and are retained for up to 30 days by default unless longer retention is required by law or necessary to protect services or third parties.
Pricing, credits, and top-ups
| Item | Details |
|---|---|
| Trial | 14 days |
| Trial checks | Up to 100 moderation checks |
| Payment method | Required to start the trial |
| First charge | Only occurs if the trial is not cancelled before the trial ends |
| Annual price | $25 USD per year |
| Included checks | 1,000 moderation checks per year |
| Extra checks | $5 USD for 500 additional checks |
| Auto top-ups | Disabled by default |
| Auto top-up trigger | Remaining credits reach 50 or fewer |
| Spending control | Annual top-up cap can be set after paid access is active |
| Credit usage | One credit is used when eligible content is successfully checked, not only when content is flagged |
| Scoped-out content | Does not consume credits where scoped dispatch is supported |
| Backend outage | No credit is consumed unless a check is successfully processed |
Example yearly costs
These examples assume steady eligible content volume across a paid year, with automatic top-ups enabled and an annual top-up cap high enough to allow the required top-ups.| Approx. eligible checks per day | Approx. checks per year | Estimated paid-year cost |
|---|---|---|
| 1 per day | 365 | $25 USD |
| 3 per day | 1,095 | About $30 USD |
| 5 per day | 1,825 | About $35 USD |
| 15 per day | 5,475 | About $75 USD |
| 50 per day | 18,250 | About $200 USD |
| 100 per day | 36,500 | About $385 USD |
Actual usage may be lower if content is outside your configured moderation scope where scope controls are supported, is otherwise not eligible for checking, is skipped by the short-lived cache, or if your forum activity varies seasonally.
What happens during outages or credit exhaustion
AI Rules Moderation is designed to assist moderation, not sit in the critical path for normal posting.If the hosted backend is temporarily unavailable, normal XenForo posting should continue. AI moderation checks may be missed or delayed during the outage. No moderation credit is consumed unless a moderation check is successfully processed.
If usable credits reach zero, AI moderation checks may pause until more credits are available, payment details are updated, an annual cap is increased where available, or credits are otherwise added.
Trial testing checklist
After starting the trial and saving your settings:- Enter a small set of clear test rules.
- If moderation scope controls are available, confirm your test account, node, and content type are inside the configured moderation scope.
- Submit a new post that clearly breaches one configured rule.
- Check XenForo’s approval queue.
- Review the AI moderation reason.
- Check the Admin CP audit log.
Requirements
| Requirement | Minimum |
|---|---|
| XenForo | 2.1.0 or newer |
| PHP | 7.2.0 or newer |
| Subscription status | Active trial or paid subscription |
| Network access | Outbound HTTPS access to the hosted moderation backend |
| Scope controls | XenForo 2.3.8 or newer required |
On XenForo 2.3+, AI Rules Moderation uses XenForo’s native webhook system. On XenForo 2.1–2.2, the add-on uses its own compatibility driver to detect supported content create/update events and queue moderation checks. Moderation scope controls require XenForo 2.3.8 or newer for native scoped webhook dispatch.
Installation
Upload and install the add-on using XenForo’s standard add-on installation process.After installation, open the AI Rules Moderation setup page in the Admin CP, start the trial or connect the subscription, enter your forum details, write your moderation rules, choose moderation scope where supported by your XenForo version, then test the integration with a clear rule-breaching post that is eligible for checking.
Télécharger V1.0.7 :
Pour consulter le contenu, vous devez : Se connecter ou S'inscrire.
