Feature Overview

Everything Jetonomy does, on one page. This is the fastest way to see whether Jetonomy fits your community - it groups every feature by what it actually does for you, links straight to the deep-dive guide for each area, and marks which features are free and which are Jetonomy Pro.

How to Use This Page

Each section below is a job your community needs done - publishing discussions, organizing them, keeping them clean, recognizing contributors, and so on. Read the benefit, scan what is included, then follow the links to the full guide for anything you want to set up.

Features marked Pro require Jetonomy Pro. Everything else ships in the free plugin.

Content & Discussions

This is the heart of Jetonomy: a fast, modern composer and a reply system built for threads with hundreds of contributions. Members write clear topics, the best answers float to the top, and nobody loses a half-finished post.

What is included:

• Topics - the primary unit of discussion, with a Markdown composer, inline image upload, tags, similar-topic detection, and topic prefixes. See Creating Topics.
• Replies and threading - threaded conversations, multiple sort orders, and efficient loading for long threads. See Replies & Threading.
• Voting - upvote and downvote on posts and replies so the most useful content rises naturally. See Voting.
• Accepted answers - mark the reply that solved a question in Q&A spaces. See Replies & Threading.
• Drafts and scheduling - save work in progress and publish now or at a future date. See Drafts & Scheduling.

Pro adds:

• Polls - attach a single or multi-select poll to any topic for decisions and feedback. See Polls.
• Reactions - emoji reactions on posts and replies so members can respond without writing a full reply. See Reactions.
• Anonymous Posting - members post and reply without showing their name, enabled per space, with an audited admin-only reveal. See Anonymous Posting.
• File Attachments - attach new images, PDFs, and documents to topics and replies, with a lightbox and an inline PDF viewer. (The free plugin already displays any attachment already on a post - see File Attachments.)

Spaces & Organization

Spaces are how you keep a large community navigable. Group them into categories, pick the right space type for each purpose, and control exactly who can join. The right structure makes your community feel purpose-built instead of generic.

What is included:

• Categories and spaces - top-level categories that group focused discussion spaces. See Creating Spaces.
• Four space types - Forum, Q&A, Ideas, and Feed, each changing how posts and replies behave. See Space Types.
• Membership and join policies - public, private, or hidden visibility paired with open, approval-required, or invite-only join rules. See Membership & Join Policies.
• Invites - invite-link landing pages so the right people get in without manual setup. See Membership & Join Policies.

Pro adds:

• Custom Fields - structured fields on posts, member profiles, and spaces so you collect exactly the information your community needs. See Custom Fields.

Moderation & Trust

Jetonomy keeps quality high without a moderator watching every post. Trust grows automatically with good participation, members flag problems, and one queue handles everything that needs human review.

What is included:

• Trust levels 0 to 5 - members earn higher trust and gain capabilities automatically as they contribute. See Trust Levels.
• Flagging and reporting - any logged-in member can report content that breaks your rules. See Flagging & Reporting.
• Moderation queue - a single dashboard for posts awaiting approval, flagged content, and spam-caught items. See Moderation Queue.
• Anti-spam - multiple silent layers of spam protection that real members never notice. See Anti-Spam.
• Banning - remove disruptive members from your community. See Trust Levels.
• Blocking - members can hide a disruptive member's replies from their own view and report them in one step, from the mobile app or the REST API. See Flagging & Reporting.
• Pinning and announcements - keep important topics at the top of a space. See Topic Management.

Pro adds:

• Advanced Moderation - rules that catch bad content automatically before it ever appears. See Advanced Moderation.
• Site Announcements - feature one post at the top of every space across the whole community. See Site Announcements.

Members & Gamification

Recognition keeps people coming back. Every member gets a public profile, reputation built from real contributions, and a place on the leaderboard worth competing for.

What is included:

• Member profiles - a public page showing who a member is and what they have contributed. See User Profiles.
• Reputation - a contribution score that powers trust levels and rankings. See User Profiles.
• Leaderboard - public recognition for your top contributors. See Leaderboard.
• Account deletion - members can permanently delete their own account from the mobile app or the REST API. See User Profiles.

Pro adds:

• Custom Badges - design your own badges and the conditions members earn them by. See Custom Badges.

Search & Discovery

Members can only engage with content they can find. Full-text search and cross-space tags make every discussion discoverable the moment it is published.

What is included:

• Full-text search - fast search across topics and replies with filters. See Search & Filters.
• Tags - connect related discussions across every space from a single tag page. See Tags.

Pro adds:

• SEO Pro - per-space meta titles, Open Graph images, Twitter Cards, schema markup, and sitemap rules. See SEO Pro.

Notifications & Messaging

Jetonomy brings members back when something relevant happens. Every event has an in-app notification and an email, and Pro adds direct messaging plus the channels members actually check.

What is included:

• In-app notifications - real-time alerts for replies, mentions, votes, and more. See Notifications.
• Email notifications - an email for every event type, with per-member control over what is delivered. See Email Settings.

Pro adds:

• Private Messaging - one-on-one and small-group direct messages without leaving your community. See Private Messaging.
• Email Digest - a curated daily or weekly summary of community activity. See Email Digest.
• Web Push - browser push notifications that reach members even after they close your site. See Web Push.
• Reply by Email - members reply to discussions straight from their email client. See Reply by Email.

Admin & Branding

Run the whole community from a clean WordPress admin. Every setting has a home, every action is logged, and Pro lets you present the community as entirely your own.

What is included:

• Settings - configure general behavior, permissions, email, appearance, SEO, anti-spam, and access control. See General Settings.
• Admin pages - manage spaces, categories, content, and users from the dashboard. See General Settings.
• Activity log - a read-only, filterable audit trail of every important event. See Activity Log.

Pro adds:

• White Label - remove all Jetonomy branding and present the community as your own product. See White Label.

Analytics & Integrations

See what your community is doing and connect it to the tools you already run. Jetonomy integrates with the major membership, commerce, learning, and community plugins so access follows enrollment automatically.

Pro adds:

• Analytics - a single dashboard for growth, engagement, and your most active members. See Analytics.
• Webhooks - send community events to Slack, Zapier, your CRM, or any custom pipeline. See Webhooks.

Integrations included:

• MemberPress - gate spaces by membership level. See MemberPress.
• Paid Memberships Pro - gate spaces by PMPro level. See Paid Memberships Pro.
• WooCommerce - open spaces on product purchase or active subscription. See WooCommerce.
• LearnDash - pair course and group enrollment with discussion spaces. See LearnDash.
• Tutor LMS - pair course enrollment with discussion spaces. See Tutor LMS.
• BuddyPress - make groups and forum spaces feel like one membership. See BuddyPress.
• FluentCommunity - run the social feed and the forum as one product. See FluentCommunity.

Developer Platform

Jetonomy is built to be extended. Everything members can do is reachable through a documented REST API, hooks, WP-CLI, blocks, and shortcodes - so you can automate, embed, and customize without touching core.

What is included:

• REST API - 48+ free endpoints under jetonomy/v1, 90+ with Pro active. See REST API.
• Hooks - 58 free hooks plus 9 in Pro for actions and filters. See Hooks Reference.
• WP-CLI - 14 free command roots and 15 in Pro for headless automation. See WP-CLI.
• Blocks and shortcodes - eight Gutenberg blocks, four classic widgets, and eight shortcodes to embed community content anywhere. The four widgets are Recent Posts, Leaderboard, Active Spaces, and User Stats (Active Spaces and User Stats are reachable only through the [jetonomy_widget] shortcode). Most surfaces are available as both a block and a shortcode, with three exceptions each way: Navigation, Login, and User Panel are block-only, while [jetonomy_user_profile], [jetonomy_space_members], and [jetonomy_widget] are shortcode-only. See Shortcodes, Widgets & Blocks.

Pro adds:

• AI - bring large language models into spam detection, auto-moderation, reply suggestions, and thread summaries, with self-hosted options. See AI.

What's Next?

Ready to set it up? Start with installation, then run the setup wizard to go live.

• Install Jetonomy →
• Run the Setup Wizard →
• Build Your First Community →

Installation

Get Jetonomy running on your WordPress site in under five minutes. This guide covers system requirements, how to install, and what happens the moment you activate.

What You Will Learn

• Whether your server meets the requirements
• Three ways to install Jetonomy
• What Jetonomy sets up automatically on first activation

See it running first - community.wbcomdesigns.com is Wbcom's own support community, running Jetonomy in production. Browse the spaces, read the threads, and see how topics, replies, voting, trust levels, and moderation feel on a live site before you install. Public registration is open, so you can sign up and ask a question there if you have one.

Requirements

Jetonomy requires a modern WordPress stack. Check these before installing.

Requirement	Minimum
WordPress	6.7 or higher
PHP	8.1 or higher
MySQL	5.7 or higher (or MariaDB 10.4+)
Browser	Any modern browser (Chrome, Firefox, Safari, Edge)

Jetonomy works with any WordPress theme. For the best visual result with zero extra configuration, use BuddyX.

Note: Jetonomy does not use WordPress custom post types. It stores all community data in its own optimized database tables (wp_jt_*). This is intentional - it gives your community the query performance and scalability that CPT-based plugins cannot match.

Installation

Method 1: WordPress Admin (Recommended)

1. Go to Plugins → Add New Plugin in your WordPress admin.
2. Search for Jetonomy.
3. Click Install Now, then Activate.

Method 2: Upload a ZIP File

1. Download the Jetonomy ZIP from jetonomy.com or wordpress.org.
2. Go to Plugins → Add New Plugin → Upload Plugin.
3. Choose the ZIP file and click Install Now, then Activate.

Method 3: WP-CLI

wp plugin install jetonomy --activate

What Happens on Activation

Jetonomy sets everything up automatically the first time you activate it. You do not need to run any SQL or configure anything manually.

Database tables created:

Jetonomy creates its own set of custom tables under the wp_jt_ prefix - one for each data entity: categories, spaces, posts, replies, votes, user profiles, notifications, subscriptions, tags, moderation flags, revisions, invite links, bookmarks, and more. It does not use WordPress custom post types.

WordPress capabilities registered:

Jetonomy registers its own custom capabilities (jetonomy_read, jetonomy_create_posts, jetonomy_moderate, and others) and maps them to your existing WordPress roles automatically.

Permalink rules flushed:

Your community URLs (e.g. yoursite.com/community/) are registered and rewrite rules are flushed immediately. No manual permalink reset needed.

URL Note: Throughout this documentation, /community/ is used as the default base URL. You can change this to any slug (e.g. /forum/, /discuss/, /hub/) in Jetonomy → Settings → General → Community Base URL. All community URLs automatically update when you change the base slug.

Cron jobs scheduled:

Six background jobs are scheduled via WP-Cron:

• Trust level evaluation - promotes members who have earned higher trust levels.
• Expired restriction cleanup - lifts temporary restrictions once they expire.
• Activity log pruning - trims old activity-log rows to keep the table lean.
• Notification cleanup - removes stale read notifications.
• Scheduled post publishing - publishes posts queued for a future date.
• Verification reminders - nudges members who have not completed verification.

After activation, you will see a blue notice at the top of your dashboard:

Your community is almost ready. Run the setup wizard to get started.

Click that notice to launch the setup wizard and go live.

Tip: If you are migrating from bbPress, wpForo, or Asgaros Forum, activate Jetonomy first to complete setup, then use the importer at Jetonomy → Import. Your existing data is never touched until you explicitly start an import.

WordPress Multisite

Jetonomy is multisite-compatible. When you network-activate the plugin from Network Admin → Plugins, Jetonomy automatically creates all required wp_jt_* database tables on every existing subsite in the network.

New subsites created after network activation are also provisioned automatically. The moment WordPress adds a new subsite to the network, Jetonomy detects it and creates the required tables before any community activity can occur.

Note: Each subsite has its own independent set of wp_{blog_id}_jt_* tables and its own community data. Spaces, posts, and members are not shared across subsites.

If you prefer per-site activation rather than network activation, install and activate Jetonomy on each subsite individually. Both approaches work correctly.

Uninstalling

If you deactivate Jetonomy, your data is preserved. Only a full uninstall (delete) removes the wp_jt_* tables, all plugin options, and all registered capabilities, giving you a clean removal with no database debris. Jetonomy Pro behaves the same way: uninstalling it removes every wp_jt_pro_* table, its options and user meta, and its scheduled tasks (fully covered as of 1.5.0).

What's Next?

Run the three-step setup wizard to choose your community URL, create your first space, and go live.

Run the Setup Wizard →

Setup Wizard

After you activate Jetonomy, a three-step wizard walks you through the only decisions you need to make before your community goes live. The whole process takes about two minutes.

What You Will Learn

• How to set your community URL slug
• How to choose between creating your first space manually or loading demo data
• What the wizard does, and what you can always change later

Opening the Wizard

Click the blue notice at the top of your WordPress dashboard, or go to Jetonomy → Dashboard and click Launch Setup Wizard.

The wizard runs in a full-screen overlay. You can close it at any time. Your progress is saved, and you can return to finish it later.

Step 1: Community URL

Choose the slug where your community will live on your site.

The default is community, which gives you yoursite.com/community/. You can change this to anything that fits your site: forum, hub, members, discuss, or your brand name.

Example slug	Resulting URL
community	yoursite.com/community/
forum	yoursite.com/forum/
hub	yoursite.com/hub/

Default space type: Also on this screen, choose the default type for new spaces you create. Your options are:

• Forum - open-ended threaded discussion
• Q&A - questions with votable answers; the best answer can be marked accepted
• Ideas - feature requests and votes with a status-lane roadmap
• Feed - short-form cards for status updates, introductions, and sharing work

You can create spaces of any type regardless of what you choose here. This setting just controls the default when you click "Add Space" later.

Tip: You can change your community URL slug later in Jetonomy → Settings → General. Jetonomy automatically flushes permalink rules when you save.

Make the community your homepage: Under Jetonomy → Settings → General → Community Setup, enable Show the community home on the site front page to serve the community home at your site root. This takes precedence over the WordPress "Your homepage displays" setting, and all other community URLs, posts, and feeds keep working unchanged.

Step 2: First Space

This step gets real content into your community so it is ready to share the moment you finish. Choose the path that fits where you are right now.

Path A: Create Your First Space

Choose this if you are setting up a production site and want to start with your own content.

1. Enter a name for your first space (e.g., "General Discussion").
2. The space uses the default type you picked in Step 1 (Forum, Q&A, Ideas, or Feed). You can change a space's type any time under Jetonomy → Spaces → Edit.
3. Click Create Space.

Your space is created and visible immediately after you finish the wizard.

Path B: Load Sample Data

Choose this if you want to try Jetonomy's features before committing to a structure.

Jetonomy seeds your site with a complete, realistic community:

• Four categories - Start Here, Product & Engineering, Community, and Help & Support
• A full set of spaces across all four types - Forum, Q&A, Ideas, and Feed - so you can see how each type behaves (for example, "Feature Requests" is an Ideas space with a roadmap, "Bug Reports" is a Q&A space with accepted answers, and "Announcements" is a Feed space)
• Demo users with realistic avatars, trust level badges, and posting history
• Sample posts and replies - enough content to see voting, accepted answers, tags, and notifications working in context

This lets you experience the full community interface as a regular member would see it, without writing any content yourself.

When you are ready to go live, click Remove Demo Data on the Jetonomy dashboard. Every demo post, reply, space, category, and user record is deleted in a single operation. Any real content you added alongside the demo data is preserved.

Note: Demo data is tracked internally via a jetonomy_demo_data record. Removal is precise and does not affect any content you created yourself.

Step 3: Done

The final screen confirms your community is live and gives you two quick links:

• Visit your community - opens yoursite.com/community/ in a new tab so you can see the frontend immediately.
• Go to admin dashboard - takes you to Jetonomy → Dashboard where you can manage spaces, moderate content, and configure settings.

Everything you configured in the wizard can be changed later:

Setting	Where to change it
Community URL slug	Jetonomy → Settings → General
Default space type	Jetonomy → Settings → General (Community Setup)
Space name, type, join policy	Jetonomy → Spaces → Edit
Email notifications	Jetonomy → Settings → Email (Notification Defaults)

What's Next?

Your community is live. Now learn what to do in the first hour: create categories, set up your real spaces, and invite your first members.

Your First Community →

Your First Community

Your community is installed and the wizard is complete. This guide walks you through what to do next, from organizing your spaces to inviting your first members, so your community is genuinely ready for people on day one.

What You Will Learn

• How to organize spaces with categories
• How to create your first real space and choose the right type
• How to invite members with a shareable link
• How to customize the look and feel
• How to import from bbPress or wpForo if you are migrating
• What the community frontend looks like for your members

Create Categories to Organize Your Spaces

Categories are the top-level groupings in your community. Every space belongs to a category. Before you create more spaces, take a moment to plan your category structure - it is much easier to do now than to reorganize later.

To create a category:

1. Go to Jetonomy → Categories.
2. Enter a name and optional description in the form on the left.
3. Click Add Category.

Your category appears in the table on the right. Drag rows to reorder them. The order here is the order your members see on the community home page.

Tip: Start with two to four broad categories. You can always add more later. Common patterns: "Support / General / Announcements" for a product community, or "Ideas / Questions / Showcase" for a creator community.

Create Your First Real Space

A space is where discussions happen. Each space has a type that shapes how members interact with content.

Choosing a Space Type

Type	Best for	Key feature
Forum	General discussion, announcements, support	Threaded replies, newest/popular sort
Q&A	Technical help, knowledge bases	Votable answers, accepted answer highlight
Ideas	Feature requests, roadmaps	Status lanes (Planned, In Progress, Shipped, Declined) with roadmap view
Feed	Status updates, introductions, sharing work	Card feed with optional title and votes

To create a space, you can use either the wp-admin form or the front-end Create Space page. Both produce the same result.

From wp-admin:

1. Go to Jetonomy → Spaces → Add Space.
2. Enter a name and optional description.
3. Pick an icon from the visual Lucide picker (16 defaults plus a search field).
4. Choose the space type.
5. Set visibility: Public (anyone can see it), Private (members only see content), or Hidden (not listed, invite only).
6. Set the join policy: Open, Request to join, or Invite only.
7. Click Save Space.

From the front end (so non-admin owners can create spaces too): visit /community/new-space/ while signed in. The form is identical and is available to any role you've enabled under Jetonomy → Settings → General, in the Front-end space creation field.

Your space is immediately available on the community frontend under its category.

Invite Members

You do not need to wait for members to discover your community organically. Jetonomy gives you a direct invite link you can share anywhere.

Generate an Invite Link

1. Go to Jetonomy → Spaces and click on your space.
2. Click Members in the space navigation.
3. Click Generate Invite Link.
4. Set an expiry date, or leave it open with no expiry.
5. Copy the link and share it via email, Slack, social media, or anywhere else.

When someone visits the link, they are added to the space immediately after logging in or creating a WordPress account.

Note: Invite links work for any WordPress user registration flow you have configured. If you allow open registration, new members can sign up and join in one step.

Existing WordPress Users

Anyone who already has an account on your WordPress site can visit yoursite.com/community/ and join public spaces by clicking Join Space. Their existing avatar, display name, and email are used automatically.

Customize the Appearance

Jetonomy inherits your theme's fonts, colors, and border radius automatically via WordPress theme tokens. If you are using BuddyX, this integration is immediate. Jetonomy reads BuddyX's design tokens and matches your brand without any manual work.

To adjust further:

• Go to Jetonomy → Settings and open the General and Advanced tabs.
• To override specific templates, create a jetonomy/ folder inside your active theme directory and drop in any template file from wp-content/plugins/jetonomy/templates/. Jetonomy always checks your theme folder first.

Tip: You do not need to copy all templates. Only override the ones you want to change. Unmodified templates are served directly from the plugin.

Importing from bbPress, wpForo, or Asgaros

If you are migrating an existing community, Jetonomy includes a built-in importer for three sources.

1. Go to Jetonomy → Import.
2. Select your source plugin: bbPress, wpForo, or Asgaros Forum.
3. Jetonomy auto-detects your existing data and shows a summary, for example: "Found: 12 forums, 3,847 topics, 28,419 replies."
4. Run a Dry Run first to check for any mapping issues.
5. Click Start Import when you are ready.

Imports run in background batches. You can close your browser and come back. The import continues via WP-Cron and resumes from where it left off if interrupted.

What gets migrated:

Source	Jetonomy
Forums	Categories + Spaces
Topics	Posts
Replies	Replies
Users	WordPress users + Jetonomy profiles
Inline images and attachments (1.8.0+)	Media library + Jetonomy attachments

The Community Frontend: A Quick Tour

Once you have content, here is what your members will see.

Community Home (/community/)

The home page lists all categories with their spaces. Each space card shows the post count, member count, and a recent activity indicator. Members can sort by activity or browse by category.

Space Listing (/community/s/space-slug/)

Inside a space, members see a topic list with vote scores, reply counts, author avatars, tags, and time. They can filter by Latest, Popular, or Unanswered. A New Post button appears in the top right for members who have permission to post.

Single Topic (/community/s/space-slug/t/topic-slug/)

The topic view shows the full post, vote buttons, and all replies. Replies are threaded up to three levels deep. For busy topics with many replies, Jetonomy loads the first 10 and last 10 replies by default, with a gap-loader button in between to fetch more. This keeps page load fast regardless of reply count.

In Q&A spaces, the accepted answer is pinned to the top and highlighted with a green checkmark.

Sidebar

The community sidebar (where the theme layout places it) shows active members, trending tags, and recent activity. The exact sidebar layout depends on your theme.

Note: All community pages are server-side rendered. There are no JavaScript-only pages, so every URL is indexable by search engines out of the box.

What's Next?

Now that your community is live and populated, learn how to organize it further with spaces and categories, including visibility rules and per-space permissions.

Spaces and Categories →

In-Page Authentication

Jetonomy can handle Login, Register, and Forgot Password right inside your community pages, with forms that match your theme instead of bouncing members to the generic WordPress login screen. It does this through its own /auth/* REST endpoints, so signing in to upvote a post or reply to a thread happens in place, without a jarring redirect to wp-login.php and back. This is an optional enhancement you can set up at any time after launch.

What You Will Learn

• Where the in-page auth forms appear and how they behave
• Why the Login block improves member experience over a bare login screen
• How captcha protection now covers signup, not just posting
• How signed-out interactions and Private community mode route visitors
• How to customize the auth surface with theme tokens

Where the Forms Appear

In-page auth is delivered by the Login block (wp:jetonomy/login). Place the block on any page or template, and it renders Login, Register, and Lost Password tabs inline, styled to match your community. The forms submit to Jetonomy's own /auth/* REST endpoints, so a visitor signs in or registers without ever leaving the page the block is on.

Use it wherever a sign-in surface makes sense:

• A dedicated member-login page you build with the block
• A sidebar or footer widget area
• A landing page that gates content behind membership

Signed-Out Interactions

When a signed-out visitor tries to do something that requires an account - upvoting a post, starting a reply, following a space, subscribing to a tag, or bookmarking - Jetonomy sends them to the WordPress login screen (wp_login_url) with a redirect_to parameter back to the page they were on. After they sign in, they land back where they started.

For a fully in-page experience, point those visitors at a page that hosts the Login block instead of relying on the default wp-login.php redirect.

Why This Matters

The old wp-login.php flow worked, but it had three real problems:

1. Visual jarring. The WordPress login screen does not look like your community. Visitors went from your themed pages to a generic blue-and-white form and back. The break in visual continuity made the community feel less polished.
2. Lost context. Visitors who clicked "Reply" had to sign in, then find their way back to the thread. WordPress's redirect handling did not always land them on the right page, especially with theme-specific URLs.
3. Slow perceived load. Two full page navigations for what should be a quick "sign me in and let me reply" step.

The Login block fixes all three. The forms render inline on the page you place the block on, look like the rest of the community, and submit through the /auth/* endpoints without a full page navigation.

Captcha Now Protects Signup

Site owners can configure reCAPTCHA or Cloudflare Turnstile keys under Jetonomy → Settings → Anti-spam. Before 1.4.0, those keys only protected post and reply submission. Bots could still register accounts freely.

From 1.4.0, the same captcha keys also protect:

• New account registration
• Password reset requests
• Login attempts after repeated failures from the same IP

Nothing needs to change in your settings. If you already had captcha configured, it now extends to signup automatically. If you don't have captcha configured, the auth forms still work; they just have less spam protection.

Captcha Providers Supported

Provider	Where to get keys
Google reCAPTCHA v3	https://www.google.com/recaptcha/admin
Cloudflare Turnstile	https://dash.cloudflare.com/?to=/:account/turnstile

Choose whichever fits your stack. Turnstile is recommended if you're privacy-conscious or already on Cloudflare; it runs without challenging visitors in most cases.

Who Still Uses wp-login.php

The Login block gives members an in-page sign-in surface. The standard WordPress site-wide login is unchanged.

Administrators (anyone with the manage_options capability) sign in at wp-login.php and reach wp-admin/. That's intentional. Site owners need a reliable way to get into the admin area even if community pages have an issue, and security plugins, two-factor plugins, and SSO integrations all hook into wp-login.php.

In practice:

• Members can use a page hosting the Login block, or fall back to wp-login.php
• Signed-out interactions that require an account redirect to wp-login.php unless you route them to a Login-block page
• Any plugin you have that customises wp-login.php (login restrictions, two-factor, branding) still works for admin login

Private Community Mode

If you've set your community to Private (the Public / Private access control under Jetonomy → Settings → General → Access Control), signed-out visitors cannot read any community content.

Every community URL redirects an anonymous visitor to the WordPress login screen (wp_login_url) with a redirect_to parameter back to the page they were trying to reach, so they land there as soon as they sign in. If you've built a page with the Login block, point your members at it for an in-page sign-in instead.

Registration can be disabled separately if you only want to allow invited members. In that case the Login block hides its Register tab.

Customization

The auth surface uses the same --jt-* design tokens as the rest of Jetonomy. That means your theme's brand color, fonts, border radius, and spacing are picked up automatically. No custom CSS required for a polished match.

Light Auth Surface in Dark Mode

There's one intentional exception: the Login block stays in light mode even when the rest of your community is in dark mode. This is a deliberate UX choice. Sign-in forms in dark mode are statistically harder to read and easier to mistype, especially on mobile. Keeping the auth surface light maintains form readability where it matters most: at the point of conversion.

If you want to override this and run a dark auth surface (for a fully dark community theme), you can do it via CSS:

.jt-login-block {
  --jt-bg: #1a1a1a;
  --jt-text: #f5f5f5;
}

Customising Form Labels

All auth form labels are translatable through the standard WordPress translation pipeline. They use the jetonomy text domain. If you're running a translated site, the forms pick up your translations on the next load.

What's Next?

With onboarding complete, fine-tune your community in the settings screens, starting with General settings for your community URL and access controls.

General Settings →

Admin Dashboard

The Jetonomy admin dashboard is your first stop after logging in to wp-admin. It shows a live snapshot of community health and gives you one-click access to the most common management tasks.

What You Will Learn

• What each stat card measures
• How to use the Quick Actions panel
• What the Recent Activity feed shows
• Where to find System Info

Go to Jetonomy → Dashboard to access this screen. It is also the landing page when you click Jetonomy in the wp-admin sidebar.

Setup Wizard Notice

On a fresh install where the setup wizard has not been completed, a blue notice appears at the top of the dashboard asking you to run the wizard. The wizard creates your first space and seeds optional demo content. Once you complete it, the notice disappears and does not return.

Stat Cards

Six cards show current counts for the most important community metrics. Counts update in real time - refreshing the page fetches the latest values.

Card	What It Counts
Total Posts	All published posts across every space
Total Replies	All published replies across every post
Active Spaces	Spaces with status "active"
Registered Users	Total WordPress users with at least one Jetonomy profile row
Pending Flags	Flags in the moderation queue that have not been resolved
Posts Today	Posts created in the current calendar day (UTC)

When the Pending Flags count is greater than zero, the card turns orange and shows a Review flags → link that takes you straight to the moderation queue - so the count is a one-click action, not just a visual signal. On the moderation queue itself, the "N pending" badge updates live as you resolve each flag, without a page reload.

Recent Activity Feed

The Recent Activity table on the left side of the dashboard shows the most recent member actions logged in the activity system. Columns:

Column	Description
User	Display name of the member who took the action
Action	What they did (colored dot indicates category: green = create, blue = vote, orange = moderation)
Object	The post, reply, space, or user the action involved, with a link to the relevant admin page
When	Relative time (e.g. "3 minutes ago")

If no activity has been logged yet, a placeholder message appears. The feed is read-only - use it for monitoring, not for taking action on specific items.

Quick Actions Panel

The right sidebar has a Quick Actions card with three buttons:

Button	What It Does
Create Space	Opens the new-space form at Jetonomy → Spaces → Add New
View Community	Opens the community home in a new browser tab
Flush Rules	Triggers flush_rewrite_rules() to rebuild WordPress permalink rules

Use Flush Rules any time your community URLs return 404s after changing the base slug, activating a new plugin, or running a migration.

Demo Data Notice

If you used the setup wizard's demo-data option, a yellow card labeled Demo Data Active appears below Quick Actions. Click Remove All Demo Data to delete all demo posts, replies, spaces, and the related setup option.

This card only appears while jetonomy_demo_data option is set. It disappears permanently once you click Remove.

System Info

A small table at the bottom of the sidebar shows:

Row	Value
Plugin Version	Current Jetonomy version constant
DB Version	The database schema version currently applied
PHP Version	Server PHP version
WordPress Version	WordPress core version
Base URL	The configured community base slug (e.g. /community/)

Use this table when filing a support request or diagnosing compatibility issues. Copy the values rather than describing them from memory.

Pro Analytics Widget (Jetonomy Pro)

When Jetonomy Pro is active and the Analytics extension is enabled, Pro adds an analytics mini-widget to the sidebar showing recent engagement trends. A full analytics dashboard is available at Jetonomy → Analytics.

When Pro is not active, a small card in the sidebar describes what the Analytics extension adds and links to the Jetonomy Pro store page.

What's Next?

Give members a sign-in experience that matches your community by adding in-page login and registration.

In-Page Authentication →

Instant Navigation

Moving around a Jetonomy community does not reload the page. Clicking from the home feed to a space, from a space to a member profile, or from search results to the leaderboard swaps the view in place: the surrounding layout stays put, the address bar updates to the new URL, and the browser back and forward buttons work exactly as expected. Posting a reply and casting a vote update in place too, without any page reload at all.

What You Will See

As a member, instant navigation means the community feels responsive. Switching between areas is immediate - there is no white-flash load between pages, and the persistent navigation bar never disappears and reappears. Scroll position on the sidebar and the header persist across moves.

As a site owner, instant navigation is automatic. There is nothing to configure. It activates as soon as Jetonomy loads on the community page and works across all the views Jetonomy renders.

Which Views Navigate in Place

The following views load via the in-place router:

• Home feed - the community landing page with category and space listing
• Category pages - a filtered view of spaces within a category
• Space listing pages - the topic list for any space
• Space members - the member roster for a space
• Tag pages - topics grouped by a community tag
• User profiles - any member's public profile page
• Search results - the community search view
• Leaderboard - the top contributors ranking
• Notifications (Pro) - the notification inbox
• Messages and conversations (Pro) - the direct messaging views

Two views always load with a full page navigation because they use rich editor scripts that require a clean initialization:

• Single topic with replies - the reply composer and code syntax highlighter boot on page load and do not re-initialize after an in-place swap
• New topic form - the topic composer has the same requirement

Every other link in the community navigates in place. External links, new-tab links, and links outside the community URL space are passed to the browser unchanged.

What Happens When JavaScript Is Off

Instant navigation is a progressive enhancement. Every link in the community is a plain HTML anchor. If JavaScript is disabled or the router encounters an error on a particular navigation, the browser performs a normal full-page load to the destination. Members reach the correct page either way.

How It Works

Instant navigation is built on the WordPress Interactivity API client-side router, the same routing engine used in the Block Editor. When a member clicks an internal community link, Jetonomy's global store intercepts the click, fetches the new view's HTML from the server, and swaps the main content region in place. The address bar is updated via the browser's History API, and focus is moved to the new content region for keyboard and screen-reader users.

After each navigation, Jetonomy fires a jetonomy:navigated custom DOM event so that other scripts - such as the load-more pagination and the icon picker - can re-initialize on the swapped content without needing a full page load.

Voting, replying, and other in-place mutations work through the Interactivity API store's reactive state rather than the router, so they update the visible counts and UI immediately without any navigation at all.

Welcome Banner

A first-time visitor who lands on your community home page sees a welcome banner before anything else. It introduces the community with a short heading and a sentence of context, shows live activity numbers, and gives them two clear choices: create a free account or log in. Logged-in members never see it.

What the Banner Contains

The banner has three parts:

Heading - A short introductory line. The default reads "Welcome to [community title]", where the title comes from your community name in settings.

Subheading - One sentence of context. If you have set a community tagline under Jetonomy → Settings → General, it appears here. If you have not set a tagline, the default reads: "Ask questions, share what you build, and join the discussion. Create a free account to post, vote, and follow the spaces you care about."

Community pulse - Three live numbers drawn from your community data: total member count, total post count, and posts published this week. The "this week" figure only appears when it is greater than zero, so a brand-new community with no recent activity shows only the member and post counts. The pulse numbers are cached for one hour so the query does not run on every page view.

Call to action - Two buttons below the pulse. "Create free account" links to the WordPress registration page. "Log in" links to the login page with a redirect back to the community home after sign-in.

Who Sees the Banner

Only signed-out visitors see the banner. Logged-in members go straight to the space and category listing without an intro screen. If registration is disabled on your site, the "Create free account" button links to a WordPress registration page that will itself tell visitors registration is closed - the banner does not check this itself.

Customise

The heading and subheading are both filterable. Add the following to your theme's functions.php or a site-specific plugin to override them:

// Override the welcome heading.
add_filter( 'jetonomy_home_welcome_heading', function( $heading ) {
    return 'Join the conversation';
} );

// Override the welcome subheading.
add_filter( 'jetonomy_home_welcome_subheading', function( $sub ) {
    return 'Ask questions, share ideas, and connect with others.';
} );

Both filters receive the current string as their only argument and expect a plain-text string in return. HTML is escaped on output, so do not pass markup.

The banner's visual style follows the same --jt-* design tokens as the rest of the community, so it automatically picks up your theme's brand color, typography, and border radius with no extra CSS.

Anonymous Posting

Anonymous Posting lets members start topics and write replies without showing their name or avatar to other members. It is a Pro feature, and it is off until you turn it on - both site-wide and per space.

How it works at a glance

• A member ticks Post anonymously (new topic) or the Reply anonymously toggle (reply) when writing.
• Everyone else sees the author as "Anonymous" with a neutral silhouette - in the feed, on the topic, in replies, in search, in the RSS feed, in notifications, on profiles, and in the mobile app.
• The member's real identity is still stored privately, so moderation, rate limits, and reputation keep working - and a site administrator can reveal the real author when needed. Every reveal is written to the activity log.

Turn it on

Anonymous posting needs two switches, both on:

1. Enable the feature (site-wide)

Go to Jetonomy ▸ Extensions and switch Anonymous Posting on. That extension toggle is the global master switch - there is no separate settings screen for it.

2. Allow it in a space

Anonymous posting only appears in spaces where a space admin has opted in:

1. Open the space and go to Edit ▸ Anonymous.
2. Tick Allow anonymous posts and save.

Turn it on only where it fits - for example a support, feedback, or sensitive-topics space. Leave it off everywhere else. A space where it is not allowed never shows the anonymous option, even while the extension is enabled.

What a member sees

In a space that allows it:

• New topic: a Post anonymously checkbox in the composer.
• Reply: an anonymity toggle (mask icon) in the reply toolbar - it highlights when active.

When they submit with it on, their post shows as Anonymous to everyone else. They can still edit or delete their own anonymous post, and they still receive replies and reactions to it.

Revealing the real author (administrators only)

Only site administrators can reveal who is behind an anonymous post or reply - space moderators cannot. On a post or reply, an admin uses Reveal author. The real name is shown only for that explicit action, and every reveal is recorded in the activity log (who revealed it, which item, and when), so reveals stay accountable.

Use this sparingly - for abuse investigations, not routine browsing. Anonymous stays anonymous by default, even for administrators, until they explicitly reveal.

Good to know

• The real author is never discarded. Anonymity hides identity from other members on every surface; it does not make the post authorless. That is what lets you moderate, rate-limit, and - if necessary - reveal.
• Both switches are required. Disabling the extension, or turning the space option off, immediately stops new anonymous posts. Posts that were already anonymous stay masked.
• Abuse: because the poster is still a real, rate-limited member behind the scenes, blocking and standard moderation remain the remedy for misuse.

Related

• Extensions - where every Pro extension, including Anonymous Posting, is enabled or disabled
• Activity Log - where every author reveal is recorded
• REST API reference - the POST /anonymous/reveal endpoint for a custom admin surface
• Anonymous Posting (Pro Features) - the full feature reference

File Attachments

File Attachments lets members attach files - images, PDFs and documents - to topics and replies. As of 1.8.0, viewing attachments works in the free plugin. Jetonomy Pro adds the ability to attach new files, plus a lightbox, an inline PDF viewer, and configurable size/type limits.

What members see without Pro

Any attachment already on a post or reply - from a forum import, the mobile app, or the REST API - renders even on a free-only install:

• Images show an inline thumbnail.
• Everything else (PDFs and documents) shows a download chip with the file name, size, and type.

If you deactivate Pro, your files keep showing. Attachment storage and display live in the free plugin as of 1.8.0, so nothing disappears - you just lose the composer, the lightbox, the inline PDF viewer, and the size/type limits until Pro is active again.

What Pro adds

With the File Attachments extension enabled, the composer gains an Attach files control (a full "Attach files" button on the new-topic form, a compact paperclip in the reply toolbar) so members can attach new files. The display also gets richer:

• Images get a lightbox (click to enlarge).
• PDFs get a first-page preview with filename · pages · size and an Open viewer button that opens the PDF inline (page navigation + zoom, or open in a new tab).
• Documents (DOCX, XLSX, PPTX, ODT, TXT, CSV) keep the same download chip you get without Pro.

Turn it on

Go to Jetonomy → Extensions and switch File Attachments on.

Configure it

Under Jetonomy → Settings → Attachments you control:

• Allowed file types - tick the image and document types members may attach. SVG is never available (it can carry scripts).
• Max file size - per file, in MB (default 10).
• Max files per post/reply - default 5.

Every upload is validated against this allow-list on the server (file extension and actual content must match an allowed type), so the settings are a real security boundary, not just UI.

Good to know

• PDF previews need server support. The first-page thumbnail is generated by your host's image tools (Imagick + Ghostscript). If the host can't rasterise PDFs, the PDF card falls back to a document icon - the file still opens and downloads normally.
• The viewer is only loaded when needed. The PDF viewer library is downloaded the first time a member opens a PDF, never on a normal page load, so it doesn't slow the community down.
• Removing an attachment detaches it from the post/reply; genuinely orphaned uploads are cleaned up automatically by a daily background task.
• Deleting a topic or reply removes its attachment links.

Related

• Extensions - where every Pro extension, including File Attachments, is enabled or disabled
• REST API reference - the attach, detach, download, and batch endpoints under jetonomy-pro/v1
• File Attachments (Pro Features) - the full feature reference

Categories are the top-level groupings members see on your community home page - think of them as the tabs or sections that organize your spaces. Every space belongs to a category, so it makes sense to set up your categories first, then create spaces inside them.

What You Will Learn

• How categories relate to spaces (and why you set them up first)
• How to create, edit, delete, and reorder categories
• How category visibility works
• How icons and colors appear in navigation

Categories vs Spaces

• A category is a label that groups related spaces together (for example "Support", "Community", or "Product").
• A space is the actual discussion area where members post topics and replies.

A space must be assigned to a category to appear in the community navigation. So the normal setup order is: create a category, then create one or more spaces inside it. See Creating Spaces once your categories are ready.

Where to Find It

Go to Jetonomy → Categories in your WordPress admin.

This screen is administrator-only by default - it requires the jetonomy_manage_settings capability, which is granted only to administrators. Editors and other roles do not see this page.

Page Layout

The Categories screen is split into two panels side by side:

• Left - Add New Category form for creating a new category
• Right - Categories table listing existing categories and their children

Creating a Category

Fill in the Add New Category form and click Add Category.

Field	Required	What it does
Name	Yes	Shown in navigation and on the category page
Slug	No	Auto-generated from the name if left blank. Used in the URL.
Description	No	Optional text shown on the category listing page
Parent Category	No	Nest this category under an existing one. Two levels maximum.
Visibility	No	Controls who can see this category (see below)
Icon	No	Choose from the built-in Lucide icon picker
Color	No	A color swatch shown next to the category name in navigation

Visibility Options

Option	Who can see the category
Public	All visitors, including logged-out visitors, when guest access is on
Private	Logged-in members only
Hidden	Not shown in navigation or listings; the direct URL still works

A category's visibility does not override the visibility of the individual spaces inside it. A public category can still contain private spaces - each space keeps its own visibility setting.

Editing a Category

Click Edit in the row actions under any category name. An Edit Category dialog opens with the same fields as the creation form. Make your changes and click Update Category.

Deleting a Category

Click Delete in the row actions. A confirmation prompt appears before the delete runs.

Warning: Deleting a category does not delete the spaces inside it. Those spaces lose their category assignment and become "uncategorized," which means they drop out of the community navigation until you reassign them. There is no undo - reassign the spaces first if you want to keep them visible.

Reordering Categories

Drag the handle icon at the far left of any row to reorder categories. The new order saves automatically when you drop the row. Child categories follow their parent when the parent moves.

Child Categories

Set Parent Category when creating or editing a category to nest it under an existing top-level category. The table shows children indented below their parent. Two nesting levels are supported.

Search

Use the search box in the table toolbar to filter categories by name. Clear the search to see all categories again. Searching does not affect the Add New Category form.

Rows Per Page

The dropdown in the table toolbar controls how many categories appear per page (20, 50, or 100). The list refreshes as soon as you change the selection - useful once you have a large number of categories.

What's Next?

Now that your categories are set up, create the spaces members will actually post in.

Creating Spaces →

Spaces are the discussion areas inside your community - each one has its own topic listing, member list, and settings. This guide shows you how to create, configure, and manage them.

What You Will Learn

• What spaces are and how they relate to categories
• Every field on the space creation form
• How the space header looks on the frontend
• How to edit and archive an existing space

What Is a Space?

A space is a focused discussion area organized around a single topic or purpose. Examples: a "General Discussion" space, a "Product Feedback" space, a "Help & Support" space.

Every space belongs to a category. Categories are the top-level groupings (like tabs or sections) that members see on the community home page. A space without a category will not appear in the community navigation, so set your categories up first. See Categories for how to create and organize them.

Tip: Plan your space structure before creating anything. Too many spaces fragment your community early. Start with three to five and add more as demand grows.

Creating a Space

You have two ways to create a space, depending on who needs to do it:

• wp-admin path (admins): Go to Jetonomy → Spaces in your WordPress dashboard and click Add New Space.
• Front-end path (anyone you choose): Visit /community/new-space/ while signed in. This page is available to any user role you've allowed under Settings → Front-end space creation, so you can let space owners or moderators create spaces without giving them wp-admin access. See Creating Spaces From the Front End for the full walkthrough.

Both paths show the same fields and produce the same result. The rest of this section describes each field.

Basic Information

Title - The name members see in listings, the space header, and breadcrumbs. Keep it short and descriptive.

Slug - The URL-safe identifier for this space. Jetonomy auto-generates a slug from the title. The final URL will be /community/s/your-slug/. You can change the slug, but doing so after posts exist will break any existing links.

Description - A short sentence or two explaining what this space is for. This appears in the space header below the title and in category listing cards. It also populates the meta description for search engines.

Icon - The space icon is selected from Jetonomy's built-in Lucide icon picker (16 default icons plus 8 extras revealed by the "Show more" button, plus a search field to find any other Lucide name). The chosen icon appears in the space header and on category listing cards alongside the title. Icons render as crisp SVGs at every size, so they read clearly on mobile.

Category - Select which category this space belongs to. A space must be assigned to a category to appear on the community home page.

Space Configuration

Type - Choose Forum, Q&A, or Ideas. This controls how posts and replies behave. See Space Types for a full explanation of each.

Visibility - Controls who can see the space and its content. Options: Public, Private, or Hidden. See Membership & Join Policies for details.

Join Policy - Controls how members gain access. Options: Open, Approval Required, or Invite Only.

Defaults: if you leave Visibility and Join Policy untouched, a new space is Public + Open - anyone can find, read, and join it. Change them for private or invite-only spaces. Note that Hidden visibility always forces Invite Only; see Membership & Join Policies.

Click Save Space to publish it immediately.

The Space Header (Frontend)

Every space has a header at the top of /community/s/your-slug/ showing:

• The Lucide icon at large size
• The space title and description
• A stat bar with total post count, member count, and last activity time
• A Follow button for logged-in users (subscribes them to new post notifications)
• A Join button when the space requires membership

Members who have already joined see the Join button replaced with their role badge (Member, Moderator, or Admin).

Editing a Space

Two paths, same fields:

• wp-admin: Go to Jetonomy → Spaces, find the space in the list, and click Edit.
• Front end: Visit the space at /community/s/your-slug/ while signed in as a space owner / moderator and click the Edit space button in the space header. See Editing Spaces From the Front End for screenshots.

All fields are editable from either path, including the type and visibility settings.

Note: Changing the space type after content exists does not reformat old posts. Existing posts keep their original structure. Only new posts use the new type's behavior.

Archiving a Space

To archive a space, open it for editing and set its Status to Archived. An archived space becomes read-only - members can read existing posts and replies, but cannot create new ones. The space remains visible in listings with a clear "Archived" label.

Archived spaces do not count toward activity stats on the community home page.

To permanently remove a space, click Delete in the space list. This action also deletes all posts, replies, votes, and member records inside that space. It cannot be undone.

What's Next?

Learn how each space type changes the way posts and replies behave.

Space Types →

The space type you choose determines how posts are structured, how replies work, and what extra features appear. Pick the right type and your community will feel purpose-built - pick the wrong one and members will feel like they are fighting the interface.

What You Will Learn

• What each space type is designed for
• How posts and replies behave differently per type
• The unique features each type unlocks
• How to change a space type after creation

The Four Space Types

Forum

Forum is the default type. It is the right choice for general discussion, support, announcements, or any conversation without a single "correct" answer.

How it works:

• Members post a topic with a title and rich content.
• Replies thread up to three levels deep (reply to a reply to a reply).
• Votes on replies surface the best contributions via the Best sort, but no reply is formally "accepted."
• Topics can be sorted by Newest, Oldest, or Best on the space listing page.

Use Forum for: support channels, general discussion, community announcements, staff Q&A sessions.

Q&A

Q&A is built for questions that have a definitive best answer. It follows the model made popular by Stack Overflow. The person who asked the question marks one reply as the accepted answer.

How it works:

• Every post is a question. The title should be phrased as a question.
• Replies are answers. Each answer is voted on independently.
• The post author sees an Accept button on every reply. Clicking it marks that reply as the accepted answer and pins it to the top of the reply list, regardless of sort order.
• The accepted answer author earns a reputation bonus (+15 points).
• The post listing shows an "Answered" badge on topics with an accepted answer. This badge also appears on the space list so members can see at a glance which Q&A spaces have resolved questions.

Use Q&A for: help & support, how-to guides, technical documentation requests, troubleshooting.

Tip: The Unanswered filter on the space listing page shows only topics with no accepted answer. This is a powerful tool for community moderators and support teams tracking open questions.

Ideas

Ideas is built for feature requests, product feedback, and roadmap voting. Each idea has a status that you control, and members vote to indicate demand.

How it works:

• Members submit ideas with a title and description.
• Other members upvote (or downvote) to signal interest. Vote score drives the default sort order.
• Each idea has an Idea Status that the space moderator or admin updates manually:

Status	Meaning
Planned	On the roadmap
In Progress	Being built right now
Shipped	Completed and available
Declined	Will not be implemented

• Status updates appear in the reply thread as a system activity entry, so members can see when an idea's status changed.
• The space listing page has a filter bar showing counts per status, making it easy to browse the roadmap.

Use Ideas for: product feedback boards, feature request trackers, community roadmaps, vote-to-prioritize workflows.

For a full guide to the Ideas roadmap view, see Ideas Roadmap.

Tip: Pick the lightbulb icon from the Lucide icon picker and name the space something like "Ideas & Feedback" to set the right expectation before members click through.

Feed

Feed is designed for short-form status updates - brief posts without a required title. Posts render as feed cards rather than the row list used by Forum and Q&A, so it behaves more like an activity stream than a traditional forum.

How it works:

• The post title field is optional. Members can post a standalone message, image, or link.
• Posts appear in a card-style feed sorted chronologically by default.
• Replies work the same as Forum type, threaded up to three levels deep.
• Voting is available, but the feed sort does not default to Best - it defaults to Latest.

Use Feed for: member introductions, community announcements, daily check-ins, showcasing work, open-ended community updates.

Empty-State Copy Adapts to the Space Type

A space with no posts yet does not show a generic "No posts" message. The empty state speaks the space's own language so the first visitor knows exactly what to do, and its call-to-action button matches:

Space type	Empty-state message	Button
Forum	"No posts yet. Be the first to start a discussion!"	New Post
Q&A	"No questions yet. Ask the first one and get answers from the community."	Ask a question
Feed	"Nothing posted yet. Share the first update."	Share an update
Ideas	"No ideas yet. Suggest the first one and let the community vote."	Suggest an idea

The button only appears for a visitor who is actually allowed to post in the space. A member (or anyone who can join an open space) sees the call-to-action; a visitor who cannot post sees the message without a button.

Note: Space cards on the community home and category listings also carry an "Active [time] ago" recency signal (for example, "Active 2 hours ago"), so members can tell a thriving space from a dormant one at a glance. A space with no recorded activity shows no label.

Changing the Space Type

You can change the type of an existing space at any time. Either open it in Jetonomy → Spaces in wp-admin, or use the Edit space button on the space header itself (front-end edit), and update the Type field.

The change takes effect immediately for all new posts. Existing posts keep their original structure. A Q&A post does not lose its accepted answer, and an Ideas post does not lose its status history.

If you change a Q&A space to Forum, the Accept button disappears from the UI but existing accepted answers remain stored in the database.

What's Next?

Learn how to control who can see your spaces and how members join them.

Membership & Join Policies →

Every space has two controls: who can see it (visibility) and how members get in (join policy). Combining them gives you precise control over every access scenario - from fully public forums to invite-only private communities. The two controls are independent in every combination except one: a Hidden space is always Invite Only (see the note under Hidden below).

What You Will Learn

• The three visibility levels and when to use each
• The three join policies and how they differ
• Per-space posting restrictions
• Space member roles and what each can do
• How to combine visibility and join policy for common use cases

What you get if you leave the defaults alone: a new space is Public visibility with an Open join policy unless you change it (or unless you have changed the community-wide default under Jetonomy → Settings). That means anyone can find, read, and join the space with no approval - the most open setting. Tighten it from there for private or invite-only communities.

Visibility Levels

Visibility controls whether the space appears in listings and whether non-members can read its content.

Public

The space appears on the community home page, in search results, and in category listings. Any visitor - including users who are not logged in - can read all posts and replies.

Members still need to join (or be approved) before they can post or reply, depending on your join policy.

Use Public when you want maximum reach and SEO value. Most community spaces should start here.

Private

The space itself appears in listings and search results, so any visitor can discover it. Only members can read the posts and replies. Non-members see the space name and description, then a Join or Request to Join button depending on the join policy: Open spaces show "Join" for an instant-access join; Approval Required spaces show "Request to Join" for a moderated admission.

The discoverable part is the space, not its content. A post inside a private or hidden space is not leaked to non-members anywhere: it is excluded from search results, from oEmbed and link-preview cards, from tag pages, from trending and popular lists, and from the recent-posts widgets and home feed. A non-member cannot pull the post body in through any of these public surfaces - only members (and admins) see it.

Private is the right choice when the community should be findable but the content should be gated. It is distinct from Hidden: a Private space is visible in the directory and search; a Hidden space is not listed anywhere.

Use Private for paid membership communities, internal team discussions, or beta program spaces where content should be gated but the space itself should be findable.

Hidden

The space does not appear in any listing, search result, or category navigation. Only members who have already joined - and admins - can see it.

Members can only reach a hidden space via a direct link or an invite link you share with them.

Use Hidden for admin-only spaces, private moderator discussion boards, or early access groups where you control every invitation.

Hidden spaces are always Invite Only. Because a Hidden space has no public Join button, its join policy is locked to Invite Only - members can only enter through an invite link you share. If you pick Hidden in wp-admin, the join policy is switched to Invite Only for you automatically (and if you set a Hidden space back to Open or Approval Required, the visibility drops to Private). From the front-end create/edit form or the REST API, the same combination is rejected on save with the message "Hidden spaces must use the invite-only join policy" - so always pair Hidden with Invite Only.

Note: WP Admins and space admins can always see hidden spaces in the admin panel, regardless of their membership status.

Join Policies

Join policy controls how members gain access to the space. It works in combination with visibility.

Open

Any logged-in user can join instantly by clicking the Join button on the space header. There is no approval step.

Members who join an Open space can post and reply immediately (subject to your per-space posting restrictions).

Use Open for general discussion spaces, community-wide help channels, and any space where you want minimal friction.

Approval Required

When a user clicks Join, they submit a join request. The request goes to the space moderators and admins for review.

Moderators see pending requests in Jetonomy → Moderation → Join Requests. They can approve or decline each request. The user gets a notification when their request is reviewed.

Since 1.5.0, space moderators can also handle requests from the community front-end, without opening wp-admin. On the space Members page (/community/s/:slug/members/), a "Pending join requests" panel lists each requester with Approve and Deny buttons. Approving admits the member instantly and emails the requester that they are in; denying clears the request. This is the same approve/admit path as the wp-admin tab, so a space moderator who has no wp-admin access can still run an Approval Required space end to end.

Approved members can then post and reply immediately.

Use Approval Required when you want to vet members before they can participate - for example, a verified customer support channel or a professional community with admission criteria.

Invite Only

No join button is shown to non-members. Members can only enter via an invite link generated by a space moderator or admin.

To create an invite link, open the space in the admin panel (Jetonomy → Spaces → [space] → Edit) and go to the Invite Links section. Each link has a configurable usage limit and optional expiry date. You can see how many times each link has been used.

Invite links are created in wp-admin. Invite-link management lives on the wp-admin space edit screen, not on the front-end editor. A front-end space owner who does not have wp-admin access can still run an Invite Only space, but a site administrator (or someone with wp-admin access) generates and shares the links for them. The front-end Edit Space page can set the join policy to Invite Only but does not create the links themselves.

Anyone who visits a valid invite link is automatically added as a member - no approval step required.

Use Invite Only for private groups, course cohorts, or closed communities where every member should be explicitly invited.

Per-Space Posting Restrictions

Beyond join policy, each space has two additional settings that control what members can do once inside:

Who Can Post - Controls who can create new topics in this space.

Setting	Effect
(Use Global Default)	Falls back to the community-wide Who Can Post setting
Members Only	All members of the space can post
Moderators & Admins	Only space moderators and admins can post
Admins Only	Only space admins (and site admins) can post

Who Can Reply - Controls who can reply to existing topics.

Setting	Effect
(Use Global Default)	Falls back to the community-wide Who Can Reply setting
Members Only	All members of the space can reply
Moderators & Admins	Only space moderators and admins can reply

These settings let you create announcement-only spaces (post set to Moderators & Admins, reply set to Moderators & Admins), or read-heavy Q&A spaces where only trusted members can contribute.

Space Member Roles

Every member of a space has one of three roles:

Member - Can read, post, and reply within the space's configured restrictions. Can vote, follow, and bookmark topics.

Moderator - All member abilities plus: approve pending posts, pin topics, close topics, move topics, delete posts and replies, manage join requests, create invite links, and review flagged content within the space.

Admin - All moderator abilities plus: change space settings, assign moderator and admin roles to other members, manage access rules, and archive or delete the space.

Note: WordPress site admins can perform all admin-level actions on any space, regardless of their space role.

Promoting members from the front-end (1.3.8+)

Space admins (and site admins) can change a member's space role directly from the front-end members page at /community/s/:slug/members/. Each member row carries a role dropdown; picking a new role saves the change live with inline success or error feedback. There is no wp-admin round-trip to add a moderator and no separate settings screen to open.

The dropdown is hidden for members who cannot manage roles, and a member cannot demote themselves below the level needed to keep at least one space admin. Members visible in the list still have to be members of the space to be assigned a role; the same per-space role rules listed above apply.

Common Visibility + Join Policy Combinations

Goal	Visibility	Join Policy
Public community forum	Public	Open
Paid membership forum	Private	Approval Required
Team-only internal channel	Hidden	Invite Only
Verified customer support	Public	Approval Required
Early access beta group	Hidden	Invite Only
Course community	Private	Open (link-gated via Invite Only)

What's Next?

See every per-space setting in one place, including how they override global defaults.

Space Settings →

Each space can override the global Jetonomy defaults with its own settings. This page is a complete reference for every per-space option, how it interacts with global settings, and how invite links work.

What You Will Learn

• Every per-space setting and what it controls
• How per-space settings override global defaults
• How to require moderator approval before posts go live
• How to create, share, and track invite links

Accessing Space Settings

Go to Jetonomy → Spaces in your WordPress admin, find the space, and click Edit. The settings panel is on the right side of the edit screen.

Per-Space Settings Reference

Posts Per Page

Default: Inherits from global setting (default: 20)

Overrides how many topics appear per page on this space's listing. Set a lower number for low-traffic spaces with long post titles. Set a higher number for high-activity spaces where members scan quickly.

Valid range: 5 to 100.

Require Post Approval

Default: Off

When enabled, every new post submitted by a non-moderator is held in a pending state and does not appear publicly until a moderator approves it.

Moderators and space admins can see pending posts immediately in the space listing with a "Pending" label. They can approve, reject, or mark the post as spam from the topic view or from Jetonomy → Moderation.

The post author receives a notification when their post is approved or rejected.

Tip: Enable this for your early community days when you want to review every submission, then turn it off once you trust your membership base.

Allow Voting

Default: On (inherits from global)

Controls whether upvote and downvote buttons appear on posts and replies in this space. Disabling voting also removes vote scores from the space's topic listing.

In Q&A spaces, voting is always available on replies regardless of this setting - otherwise the Best sort and accepted-answer workflow cannot function correctly.

In Ideas spaces, voting cannot be disabled because it is the core mechanism for prioritizing ideas.

Who Can Post

Default: Anyone (members)

See Membership & Join Policies for the full option set. The per-space value overrides the global default for this space only.

Who Can Reply

Default: Anyone (members)

Controls who can add replies to topics in this space. Overrides the global default for this space only.

Post Prefixes

Default: Off

Prefixes are short, colored labels members can attach to the front of a topic title - for example "Bug", "Idea", "Solved", or "Announcement" - so the listing is easier to scan.

Turn on the Enable prefixes toggle to reveal the prefix list, then add one row per prefix. Each row has a label (up to 50 characters) and a color swatch. Add as many as the space needs, and remove any with the × button.

Once prefixes are enabled:

• When a member starts a new topic in the space, an optional Prefix dropdown appears on the compose form. They pick one (or leave it blank).
• The chosen prefix shows as a colored label in front of the topic title on the space listing and the single-topic view, using the color you set.

Prefixes are configured per space, so a "Support" space can offer "Bug / Question / Solved" while an "Announcements" space offers none. You can manage prefixes from either the wp-admin space editor or the front-end Edit Space page.

How Per-Space Settings Override Global Settings

Jetonomy uses a two-layer settings system:

1. Global settings - Set at Jetonomy → Settings → Community. These are the defaults that apply to every space.
2. Per-space settings - Set on individual spaces. When a per-space value is configured, it takes precedence over the global value for that space only.

If you leave a per-space setting at "Inherit from global," any future changes to the global setting will automatically apply to that space. If you explicitly set a per-space value, global changes do not affect it.

This means you can configure a sensible default globally and only override the spaces that need different behavior - instead of configuring every space individually.

Access Rules for Membership-Gated Spaces

Access rules restrict a space based on external membership status - not just whether someone has joined the space. They apply to Private and Hidden spaces, where non-members are already blocked from the content and the rule decides who among them gets in.

Go to the Access Rules tab on the space edit screen to add rules.

Adding a restrictive rule to a Public space converts it to Private automatically. A Public space is readable by everyone, so a membership, role, capability, or trust-level rule attached to it would silently do nothing - the content stays open. To stop that "configured but still accessible" trap, Jetonomy switches the space to Private the moment you save such a rule, so the rule can actually gate access. The admin screen tells you it happened. If you did not intend to make the space Private, remove the rule and the space stays Public.

Each rule has three parts:

Rule Type - What to check:

Type	What it checks
Everyone	Matches every visitor, including logged-out users
Logged In	User is authenticated
WordPress Role	User has a specific WP role (e.g. Editor)
Capability	User has a specific WP capability
Trust Level	User's Jetonomy trust level (0 - 5)
Membership	User has an active membership. The specific provider - MemberPress or Paid Memberships Pro in free, plus WooCommerce Memberships, Restrict Content Pro, LearnDash, and Learnomy (course or membership plan) in Pro - is chosen within the rule via the matching membership adapter

Access Grant - What to allow:

Grant	Effect
Read	Can view posts and replies, cannot participate
Participate	Can read, post, and reply
Full	All participate abilities plus moderator actions

Auto-Assign Role - Optionally assign the member a space role (Member, Moderator, Admin) automatically when the access rule is satisfied. This is useful when you want MemberPress Gold members to automatically become space moderators.

Multiple rules can be stacked. Jetonomy grants the highest matching permission level.

Note: MemberPress and Paid Memberships Pro adapters are available in Jetonomy free. WooCommerce Memberships, Restrict Content Pro, LearnDash, and Learnomy adapters require Jetonomy Pro. The Learnomy adapter gates a space by either a Learnomy course or a Learnomy membership plan.

Invite Links

Invite links let you bring specific people into a space without opening up general membership.

Where to manage invite links: invite links are created and tracked from the wp-admin space edit screen (Jetonomy → Spaces → [space] → Edit → Invite Links), not from the front-end Edit Space page. A space owner without wp-admin access can run an Invite Only space, but a site administrator generates and shares the links on their behalf.

Creating an Invite Link

1. Open the space for editing in wp-admin and go to the Invite Links section.
2. Click Create Invite Link.
3. Set an optional Usage Limit (how many people can use this link before it expires).
4. Set an optional Expiry Date.
5. Click Generate.

Jetonomy generates a unique URL: /community/invite/abc123def/

Sharing an Invite Link

Copy the link from the Invite Links table and share it however you prefer - email, Slack, a membership welcome email, etc.

When someone visits the link, they are prompted to log in if they are not already. After logging in, they are automatically added to the space as a Member.

Tracking Usage

The Invite Links table shows each link's current usage count against its limit. Links that have reached their usage limit are automatically deactivated but remain in the table for your records.

You can manually deactivate or delete any invite link at any time.

Space RSS Feeds

New in 1.5.0. Every public space publishes an RSS 2.0 feed of its latest 20 topics at:

https://your-site.com/community/s/{space-slug}/feed/

Feed readers and browsers discover it automatically from the space page. Members and visitors can follow a single space from any RSS reader without creating an account - useful for announcement spaces, changelogs, and "follow this team" workflows.

Privacy is preserved: the feed serves only what a logged-out visitor could already read. Private and hidden spaces return 404 from their feed URL, and switching the whole community to private mode disables all feeds. Developers can adjust feed contents with the jetonomy_space_feed_posts filter.

What's Next?

Learn how to create topics and posts inside your spaces.

Creating Topics →

Related Pro Features

• Custom Fields - add structured fields to posts and profiles, configurable per space.

Every Ideas space includes a built-in roadmap view. Instead of scrolling through a flat list of feature requests, visitors can see all ideas organized by status - what is planned, what is being built, what has shipped, and what will not be pursued. This page explains the roadmap, the status lanes, and how status changes are communicated to your community.

What You Will Learn

• Where to find the roadmap view
• What the four status lanes mean
• How admins update an idea's status
• How status changes surface in notifications and the activity log
• What the roadmap looks like for community members

What the Roadmap Shows

The roadmap is a dedicated view of an Ideas space that groups all ideas by their current status. Access it at:

/community/s/<space-slug>/roadmap/

A link to the roadmap appears in the Ideas space navigation alongside the main topic list. Members do not need to navigate manually - they can switch between the idea list and the roadmap from within the space.

Each status lane shows all ideas in that state, sorted by vote score within the lane (highest votes first). This gives members a clear view of what the community wants most and where each request stands.

Status Lanes

The roadmap has four lanes:

Status	What it means
Planned	The idea has been accepted and is on the roadmap. Work has not started yet.
In Progress	The team is actively building or implementing this idea.
Shipped	The idea has been completed and is now available.
Declined	The team has decided not to pursue this idea. A reply with context is recommended.

New ideas submitted by members have no status by default. They appear in the main idea list but not in any roadmap lane until a moderator or admin assigns a status.

Tip: When you decline an idea, add a reply explaining why. Members who took the time to submit and vote on an idea deserve a clear answer. Declined ideas with a closing comment are far less likely to be re-submitted repeatedly.

How Admins Update a Status

Any space moderator or admin can change an idea's status:

1. Open the idea (the single post view).
2. Find the Status control in the post meta area below the title.
3. Select a new status from the dropdown: Planned, In Progress, Shipped, or Declined.
4. Click Update Status.

The status change saves immediately. A system entry appears in the reply thread showing what the status changed from and to, with a timestamp. This gives the idea's full history in one place.

You can also update status from the space admin panel at Jetonomy → Spaces → [Space Name] → Posts. The status column is editable inline from that view, which is useful for processing a batch of ideas at once.

How Status Changes Surface in Notifications

When an idea's status changes, Jetonomy sends notifications across three channels:

Activity log - A system activity entry is created in the idea's reply thread, visible to anyone who opens that idea.

Email digest - If a member follows the Ideas space and has email digest enabled, the status change is included in their next digest email (daily or weekly depending on their preference).

In-app inbox - The idea author receives an in-app notification immediately. All followers of the Ideas space also receive an in-app notification.

Members who do not follow the space will not receive notifications about that specific status change. Encourage members to follow the space after submitting an idea so they stay informed.

Customer-Visible Behaviors

What members see at each stage:

• New idea with no status assigned - Appears in the idea list. Not shown in any roadmap lane until an admin or moderator picks a status. Vote buttons are active so members can build up signal even before the team triages.
• Planned - Appears in the Planned lane on the roadmap. A "Planned" badge shows on the idea card.
• In Progress - Moves to the In Progress lane. Badge updates. Members can see work has started.
• Shipped - Moves to the Shipped lane. Badge shows "Shipped." Upvote button remains available so members can react positively to the delivery.
• Declined - Moves to the Declined lane. Badge shows "Declined." Vote controls remain visible.

Ideas can be moved between statuses at any time. Moving a shipped idea back to In Progress (for a revision, for example) is valid and will notify followers again.

What's Next?

The roadmap is a deep-dive on the Ideas space type. To set up a space without leaving the front end, see the front-end create flow.

Create a Space from the Front-End →

Since Jetonomy 1.4.0, members with the right role can create a new space without ever opening wp-admin. The front-end Create Space page lives at /community/new-space/ and gives community owners a way to delegate space creation to trusted regulars, team leads, or paying members without handing out WordPress admin access.

What You Will Learn

• Where the Create Space page lives and who can reach it
• Which roles are allowed to create spaces, and how to change that
• Every field available on the form, including the visual icon picker
• What happens the moment the form is submitted
• When to use this page versus the wp-admin equivalent

Where The Page Lives

The page is always available at /community/new-space/. It is part of the standard /community/ rewrite group, so it inherits the same theme, header, and footer as the rest of your community pages.

There is no separate menu item by default. Most communities expose the page in two places:

• A "Create space" button on /community/ for signed-in users with permission
• A "Start a space" link in the header avatar menu

Both links are conditional. Members who do not have permission never see the link and never see the page either, even if they type the URL directly.

Who Can Create Spaces

Open Jetonomy → Settings → Front-end space creation. The setting is a list of WordPress roles. Tick the roles you want to allow.

The default is Administrator only, which matches the pre-1.4.0 behaviour. Most communities widen this to Editor, Author, or a custom role such as "Community Builder" after they have run for a few weeks and identified trusted members.

A few important notes:

• The permission is role-based, not per-user. If you want to grant one specific member the ability to create spaces, add them to a role that has it.
• Granting the right to create a space is not the same as granting the right to moderate every other space. A member who can create one space only moderates the spaces they created, not the whole community.
• Network admins on multisite have the permission everywhere by default.

The Form Fields

The front-end form covers the fields a member needs to launch a space. The slug is generated automatically from the title, and posts-per-page is set later on the Edit Space page rather than at creation time.

Field	What it controls
Title	The display name shown in listings and the space header. Required.
Description	One or two sentences shown on the space card and the space header.
Type	Forum, Q&A, Ideas, or Feed. Cannot be changed after creation.
Visibility	Public, Private, or Hidden.
Join policy	Open, Approval Required, or Invite Only.
Category	Which top-level community category the space belongs to. Optional but recommended for navigation.
Icon	A visual icon shown next to the title everywhere the space appears.

The form does its own validation in the browser before submission, then again on the server. Submitting with an empty title returns an inline error rather than a generic failure. The slug is derived from the title automatically and made unique by the server.

The Visual Icon Picker

The icon field is not a free-text field. Jetonomy ships with a Lucide icon picker so every space gets a consistent, professionally-drawn icon.

The picker shows 16 default icons up front, covering the most common community space themes: users, hand, megaphone, message-circle, help-circle, lightbulb, star, rocket, book-open, award, shield, pin, bookmark, home, hash, and folder.

Click "Show more" to reveal another 8 icons for less common topics. If none of those fit, the search field at the top filters the entire Lucide catalogue by name, so typing "music" surfaces the music note icon, "camera" surfaces the camera icon, and so on.

The picker stores only the icon name, not an SVG, so the icon stays crisp at any size and automatically picks up the active theme's color tokens.

What Happens On Submit

Submitting the form does five things in one transaction:

1. Creates the space row in wp_jt_spaces
2. Adds the submitting user as the space admin (role = admin)
3. Adds the space to the chosen category, if any
4. Flushes the relevant rewrite caches so the space URL resolves immediately
5. Redirects the user to the new space at /community/s/<slug>/

There is no approval queue. The space is live the moment the form is submitted. Who may reach the form at all is gated by the jetonomy_create_spaces capability plus the Front-end space creation roles setting, so you control space creation by role rather than by an after-the-fact approval step.

Validation Hints

• Title is required and cannot be a duplicate of an existing space title within the same category.
• The slug is generated automatically from the title and made unique by the server. There is no slug field on the create form; you can edit the slug later from the Edit Space page.
• Description is optional but space cards look better with one.
• Category, Type, Visibility, and Join policy default to the community-wide defaults set in Jetonomy → Settings.

Permission Gotchas

A few rules that surprise people on first use:

• Creating is not moderating. A role granted "create spaces" is automatically space admin only for the spaces it creates. It cannot moderate other spaces it did not create.
• Visibility is per-space, not per-role. A role allowed to create spaces can create a space of any visibility, including Hidden. There is no built-in per-visibility gate; restrict who can create spaces at all via the Front-end space creation roles setting if that matters for your community. One rule does apply to the combination, though: a Hidden space must use the Invite Only join policy. Picking Hidden with Open or Approval Required on the front-end form is rejected on save with "Hidden spaces must use the invite-only join policy" - set the join policy to Invite Only when you choose Hidden. See Membership & Join Policies for the full explanation.
• Deactivating a member who created a space does not delete the space. The space remains; ownership transfers to the next admin in the space, or to the site administrator if there is no other admin.
• Slug collisions are checked across the whole site. A member trying to create a space with a slug another space already uses will see an inline error, even if they cannot see the other space.

Front-End Form vs wp-admin

Both paths produce identical spaces. Pick whichever is faster for the situation.

Situation	Use front-end	Use wp-admin
You're a regular member with permission	Yes	Not available
You're an admin and already in the community	Yes, faster	Either
You're an admin setting up the community for the first time	Either	Either, bulk import easier
You want to create 10+ spaces in one session	Either	wp-admin has bulk tools
You want to seed a space with demo content	wp-admin	wp-admin only
You want to change advanced options (access rules, custom roles)	wp-admin	wp-admin only

The front-end form covers everything a member or space owner needs. The wp-admin editor adds bulk tools and a few advanced toggles that only site administrators ever touch.

Developer Hooks

The two controls that come up most often when customising this page:

• jetonomy_create_spaces (capability) - granted to roles via the Front-end space creation roles setting. A user without this capability never sees the Create Space link or page. This is the primary gate.
• jetonomy_use_frontend_space_edit (filter) - returns true to route both the Create and Edit space flows through the front-end UI. Default true. Return false to send these flows to wp-admin instead.

See the Developer Reference for the full signatures and examples.

What's Next?

Once a member has created a space, they often want to tweak it. The Edit Space page lets them adjust the icon, description, join policy, and more without leaving the front-end.

Edit a Space from the Front-End →

Since Jetonomy 1.4.0, space owners and moderators can edit their space directly from the front-end. They click an Edit space button in the space header and adjust the title, description, cover image, icon, type, visibility, join policy, moderation approval, category, posts-per-page, and prefixes without ever loading wp-admin.

What You Will Learn

• Where the Edit space button appears and who sees it
• Every field you can change from the front-end
• How the cover image upload works without wp-admin permissions
• The safety rules that prevent a space from being orphaned by accident
• The difference between archiving and deleting a space
• When to use the front-end editor versus the wp-admin one

Where The Edit Button Appears

The Edit space button lives in the top right of every space header, just above the post listing. It is conditional: only members with the right role inside that space see it.

The roles that see the button:

• Space admin - the member who created the space, plus anyone they promote to admin
• Space moderator - members promoted by a space admin
• Site administrator - sees the button in every space

Regular members and guests never see the button. If a member loses their moderator role mid-session, the button disappears on the next page load.

The button leads to a dedicated page at /community/s/<slug>/edit/. The URL is permission-checked on every request, so typing it directly without the right role returns a 403.

What You Can Edit

Every space setting that is editable in wp-admin is editable from the front-end. The two editors are kept in lockstep release after release.

Field	What it controls
Title	The display name shown everywhere the space appears
Slug	The URL segment under /community/s/. Changing it sets up a redirect from the old slug
Description	The one-line summary shown on the space card and header
Cover image	A wide banner image shown above the space header
Icon	The Lucide icon shown next to the title
Category	Which community category the space belongs to
Type	Forum, Q&A, Ideas, or Feed
Visibility	Public, Private, or Hidden
Join policy	Open, Approval Required, or Invite Only
Require moderator approval for new posts	When checked, new posts are held in the moderation queue until a moderator approves them
Posts per page	A number from 1 to 100; leave blank to use the site default
Post prefixes	Optional tags shown in front of post titles (e.g. "Bug", "Idea")

Changing the type after creation is supported but rarely a good idea. Switching a Q&A space to a Forum keeps every existing post but stops showing the "Mark as answer" affordance. The editor warns you before saving a type change.

The Visual Icon Picker

The icon picker is the same one used on the Create Space page. 16 default Lucide icons up front, 8 more behind a "Show more" button, and a search field that filters the full Lucide catalogue by name.

Changing the icon takes effect immediately on save. Cached pages and listings pick up the new icon on the next refresh. There is no manual cache flush needed.

Cover Image Upload

The cover image field accepts a standard image file. Recommended dimensions are around 1600 x 400 pixels - that is guidance for how the banner is cropped, not an enforced limit.

Uploads go into the standard WordPress media library at /wp-content/uploads/YYYY/MM/, the same place every other site image lives. The space stores only the resulting image URL, so the upload is reusable like any other attachment. The upload endpoint is gated by the logged-in member's edit permission in the space rather than by WordPress's upload_files capability, so a space owner can set a cover without site-wide media upload rights.

There is a Remove cover link below the upload field that clears the image reference from the space. Removing a cover only clears the reference; it does not delete the underlying attachment from the media library.

Role-Protection Rules

The front-end editor is intentionally cautious about anything that could leave a space without an owner.

• No self-demote. A space admin cannot demote themselves if they are the only admin. The role dropdown skips the "moderator" and "member" options in that case and shows a tooltip explaining why.
• No last-admin-out. A space admin cannot delete or archive the space if they have set themselves to leave it. The flow forces a transfer-to-another-admin step first.
• No silent ownership transfer. Promoting another member to admin happens on the Members tab, not on the Edit space page. The editor never moves ownership in the background.

These rules exist because the most common community support ticket pre-1.4.0 was "I accidentally demoted myself and now nobody can edit the space." The front-end editor blocks that path entirely.

Archive vs Delete

The bottom of the Edit space page has two destructive actions, kept visually separate from the save button.

Archive space marks the space read-only. Existing posts and replies stay visible to anyone who could see them before. New posts and replies are disabled. The space disappears from category listings but is still reachable at its original URL. Archive is reversible: re-opening the editor and clicking Unarchive restores everything.

Use archive when:

• A space has run its course but the content is still worth keeping
• A seasonal event ends and you want the archive of last year's discussion to remain
• A topic moves to a different space and you want the old discussions preserved

Delete space removes the space and every post, reply, vote, flag, and subscription in it. It cannot be undone from the UI. The button asks for explicit confirmation (typing the space title) before it fires.

Use delete when:

• The space was created by mistake and has no real content
• The content needs to be removed for legal or moderation reasons
• You are cleaning up after a spam attack

If you are unsure, archive instead of delete. Archiving is reversible; deletion is not.

Front-End Edit vs wp-admin Edit

Both editors produce identical results. They share the same model, the same validation, and the same hooks.

Situation	Use front-end	Use wp-admin
You're a space owner without admin access	Yes	Not available
You're a site admin already in the community	Yes, faster	Either
You want to change advanced access rules	Not supported	wp-admin only
You want to bulk-edit multiple spaces	Not supported	wp-admin only
You want to change Pro extensions config	Not supported	wp-admin only
You want to fix a typo in the description	Yes, fastest	Either

The front-end editor covers the day-to-day fields a space owner touches. The wp-admin editor adds bulk tools and a handful of advanced settings that only site administrators ever need to change.

What's Next?

If you give space-creation permission to a wider group, expect those members to want a single place to see every space they run or belong to. The My Spaces page does exactly that.

My Spaces →

A topic is the primary unit of discussion in Jetonomy - every conversation, question, idea, or update starts here. This guide walks through everything that happens from the moment a member clicks "New Post" to when their topic goes live.

What You Will Learn

• How to open the new post form in a space
• Every field in the post composer and what it does
• How Markdown formatting works in the content editor
• How content moderation and rate limiting affect new members
• Whether posts publish immediately or wait for approval

Opening the New Post Form

Members can start a new topic in three ways:

1. Navigate to a space and click the New Post button in the space header.
2. Visit the direct URL: /community/s/your-space-slug/new/
3. Click + New from any page in the community - this opens a space picker first, then the form.

The new post form is always scoped to a specific space. If a member arrives via the generic + New button, they choose a space before the form loads. This ensures every topic lands in the right place.

If You Have Not Joined the Space (1.6.0)

Jetonomy checks that you are allowed to post before it loads the composer. If you open the new post page for a space you have not joined, you see a permission prompt up front instead of a blank composer:

• Open space you can join - a "Join [space]" prompt appears with a button that takes you back to the space to join. Once you are a member, open the new post page again and the composer loads.
• Restricted space you cannot join - a permission-denied message appears with a link back to the space.

This replaces the old behavior where you could write an entire post and only hit the wall when you tried to submit it. The gate runs first so you never lose a draft to a rejected submission.

The Post Composer

Title

The title field is required for Forum, Q&A, and Ideas spaces. Write a clear, specific title that tells members exactly what the topic is about before they click it.

Good: "How do I set up automatic email digests for my space?" Weak: "Help with emails"

For Q&A spaces, phrase the title as a question - it helps other members find answers when searching.

The title field is optional for Social Feed spaces, where short-form posts without titles are common.

Content

The content field supports rich text via a Markdown toolbar. You do not need to know Markdown syntax - the toolbar buttons handle formatting for you.

Toolbar options:

Button	What it does
B	Bold text
I	Italic text
< >	Inline code
Link	Insert a hyperlink
Quote	Block quote
Image	Upload an image from your device

You can also type Markdown directly if you prefer:

• **bold** → bold
• *italic* → italic
• `code` → code
• > quote → block quote

Images are uploaded to the WordPress media library. Each image is inserted as a standard <img> tag in the content. There is no separate file attachment field - all media goes inline.

Tags

Add up to five tags to help members find your topic through search and tag filtering. Type a tag name and press Enter. Jetonomy auto-suggests existing tags as you type - reusing existing tags is better than creating near-duplicates.

Tags are space-scoped by default. A "bug" tag in your Support space and a "bug" tag in your Dev space are the same tag in the database, but the tag page at /community/tag/bug/ will show posts from all spaces.

Similar Topics Detection

As you type the title, Jetonomy searches for existing topics with similar titles in the current space and shows up to five matches inline below the title field. This is the single best defense against duplicate topics - most duplicates happen because the author simply did not know an existing topic already covered their question.

If you see your question already answered in the list, click the match to jump to the existing topic instead of submitting a duplicate. If none of the matches fit, keep typing - the search re-runs after every few characters.

Similar Topics detection runs a lightweight, debounced search request (about 400ms after you stop typing) against the server search index, so it does not reload the page.

Prefix Selector

If the space has topic prefixes enabled, a Prefix selector appears next to the title field. Pick a prefix (for example, Bug, Suggestion, Solved) from the list and it appears as a colored label in front of your topic in the space listing.

Prefixes are configured per space by the space owner - see the Topic Prefixes guide.

Private Topic Toggle

If your space allows it, a Private toggle appears at the bottom of the composer. Enabling it restricts the topic to you and space moderators only - other space members cannot see it. Use this for sensitive support issues, personal requests, or anything that should stay between you and the moderators.

Not every space allows private topics. If you do not see the toggle, the space owner has disabled the feature.

See Private Topics and Topic Prefixes for the full guide.

Post Type Is Derived Automatically

You do not select the post type - Jetonomy determines it from the space type:

Space type	Post type
Forum	Discussion
Q&A	Question
Ideas	Idea
Social Feed	Update

The composer adapts its UI accordingly. Q&A spaces show a hint to "phrase as a question." Ideas spaces show the Idea Status selector (visible to moderators). Social Feed spaces make the title optional and show a shorter, Twitter-style composer.

Content Moderation Checks

Before a post is saved, Jetonomy runs three checks:

Rate limiting - New members (Trust Level 0) can submit a maximum of 3 posts per day and 10 replies per day. If a member has hit their limit, the submit button shows an error and the post is not saved. Rate limits reset at midnight UTC. Members at Trust Level 1 and above have higher or no limits, depending on your global settings.

Require post approval - If the space has "Require Post Approval" enabled, the post is saved with a Pending status. It is not visible to other members until a moderator approves it. The submitter sees a confirmation: "Your post has been submitted and is awaiting approval."

Auto-moderation rules (Jetonomy Pro) - If Pro auto-moderation rules are configured, Jetonomy checks the content against those rules before saving. Depending on the rule configuration, the post may be flagged, held, blocked, or marked as spam automatically.

Note: WP Admins and space moderators bypass rate limiting and approval requirements. Their posts always publish immediately.

After Publishing

When a topic publishes successfully:

• It appears at the top of the space listing under the Latest sort.
• The author is automatically subscribed to the topic and will receive notifications for new replies.
• The space's post count increments immediately.
• Search indexes are updated on the next cron run (typically within a few minutes).

If the topic is pending approval, it does not appear in the listing, does not increment the post count, and the author's subscription is created but held until approval.

What's Next?

Learn how replies work, how threading is structured, and how to accept answers in Q&A spaces.

Replies & Threading →

Related

• Embedding the Composer - drop a "start a topic" box onto any WordPress page, post, or landing page using the Compose Topic block or the [jetonomy_compose_topic] shortcode.
• You can also surface existing discussions on any page with the Forum Feed and Trending blocks (and their [jetonomy_recent_posts] / [jetonomy_trending_posts] shortcodes) - see Shortcodes, Widgets & Blocks.

Related Pro Features

These Pro extensions add to the discussion experience:

• Polls - attach a single or multi-select poll to any topic.
• Reactions - emoji reactions on posts and replies.

Replies are where conversations happen. Jetonomy's reply system supports threaded discussions, multiple sort orders, accepted answers in Q&A spaces, and efficient loading for threads with hundreds of contributions.

What You Will Learn

• How to add a reply to a topic
• How threaded replies work and how deep they go
• How to sort replies and what each sort does
• How accepted answers work in Q&A spaces
• How to edit your own replies
• How Jetonomy handles large threads efficiently

The Reply Composer

The reply composer appears at the bottom of every topic page. Click into the text area to expand the full Markdown toolbar - the same formatting options available in the post composer (bold, italic, inline code, links, block quotes, image upload, code blocks).

Click Reply to submit. A new top-level reply is added in place without a page reload. A threaded sub-reply (a reply to another reply) reloads the page so it slots into the right position under its parent.

If the space has "Require Post Approval" enabled, your reply is held for moderator review before appearing to other members. A confirmation message tells you it is pending.

Quote Replies

To reply while quoting a specific passage from an existing reply, select the text you want to quote and click the Quote button that appears. Jetonomy inserts the quoted text as a styled blockquote in your reply composer, with the author attribution linked back to the source reply.

You can also click Quote in the ... menu on any reply to quote its full body without selecting text first. This is the quickest way to address a specific point from a long reply - the quoted passage gives readers the context without forcing them to scroll back up.

Threading: Replies to Replies

You can reply to any existing reply by clicking the Reply link that appears when you hover over a reply. This creates a threaded sub-reply nested visually under the parent.

Jetonomy supports three levels of nesting:

Reply (level 1)
  └─ Reply to reply (level 2)
       └─ Reply to reply to reply (level 3)

At level 3, no further nesting is allowed. Members can still reply to a level-3 comment - that reply is added at level 3 as well, keeping the conversation readable.

Threaded replies let you have multiple parallel conversations inside the same topic without them colliding. A question inside a reply gets its own sub-thread. The main discussion continues underneath.

Sorting Replies

Use the sort controls at the top of the reply list to change the order:

Oldest first - Replies appear in chronological order, oldest at the top. Best for reading a long discussion from the beginning. This is the default for Forum spaces.

Newest first - Most recent replies appear at the top. Best for active topics where you want to see the latest contributions without scrolling.

Best - Replies are ranked by net vote score (upvotes minus downvotes), highest at the top. Best for Q&A spaces or any topic where you want the most useful contributions visible first. Within the same vote score, older replies rank first.

Sort preference is stored per-session - if you change it on one topic, it persists as you navigate between topics in the same session.

Note: "Best" is the vote-ranked sort for replies inside a topic. The space topic listing uses a similarly named vote-ranked sort called Popular (see Voting & Reputation). Both rank by net vote score - they are simply labelled differently because one orders replies and the other orders topics.

Accepted Answers in Q&A Spaces

In Q&A spaces, the person who asked the question (the topic author) decides which reply is the accepted answer. This signals to everyone else that the question has been solved and surfaces the winning reply at the top of the thread.

Marking an Answer as Accepted

As the asker, you are the one who confirms which reply actually solved your problem:

1. Open your own question. You must be the post author (space moderators and admins can also accept on your behalf, see below).
2. Find the reply that best answers your question.
3. Click the Accept button, the checkmark icon shown below the reply, on each reply in a Q&A space.
4. The reply is immediately pinned to the top of the reply list, above all other replies and regardless of the current sort order.

What changes the moment you accept:

• The reply gets a green Accepted tag and the whole thread is marked as resolved.
• An "Accepted answer" callout box appears at the top of the topic, so anyone landing on the question sees the solution first without scrolling.
• The reply's author receives a notification and a reputation bonus (a default of +15; you do not earn reputation for accepting your own reply). The bonus amount is admin-configurable under Settings → Permissions → Reputation Points.

Changing or Removing the Accepted Answer

The acceptance is never locked in. As the asker you stay in control:

• Switch answers: Click Accept on a different reply. The previous reply automatically loses its accepted status, so there is only ever one accepted answer at a time.
• Unaccept entirely: On the currently accepted reply, click the Unaccept button (the x-circle icon). This clears the accepted answer, returns the question to the unresolved state, removes the callout, and revokes the reputation that was awarded when it was accepted, so trust scores stay honest.

Tip: Space moderators (and admins) can also accept or unaccept answers on any Q&A topic in their space, useful for resolving questions on behalf of an asker who never came back to mark a solution.

Editing Your Own Replies

Click the ... menu on any reply you authored and select Edit. The reply text becomes an inline editor - you make changes and click Save. No page reload.

Edits are tracked as revisions internally. Moderators can view reply revision history from the moderation panel.

You can edit a reply at any time after posting. There is no edit window.

If a moderator edits your reply, the reply gets an "Edited by moderator" label.

How Jetonomy Handles Large Threads

For topics with many replies, Jetonomy uses cursor-based pagination to load replies in batches.

The first time you open a topic, you see the first batch of top-level replies (default: 20). A Load more replies button appears at the bottom if more exist. Clicking it loads the next batch without reloading the page.

For very high-traffic topics - those with hundreds of top-level replies - Jetonomy uses a smart loading strategy: it loads the first 10 replies and the last 10 replies, with a collapsed gap in the middle showing how many replies are hidden. You can click the gap to load replies from that range.

Threaded sub-replies follow the same pattern. A thread deeper than a few replies shows a "Show X more replies" link inline.

Note: New reply notifications appear as a sticky banner at the bottom of the page when other members post while you are reading. Click the banner to load the new replies without losing your scroll position.

What's Next?

Learn how upvotes and downvotes work, how they affect reputation, and how they power the Popular sort and trending sidebar.

Voting & Reputation →

Voting is the engine behind Jetonomy's quality signals. It surfaces the best content, rewards helpful members, and gives you a community where the most useful posts rise to the top naturally, without moderator intervention.

What You Will Learn

• How to vote on topics and replies
• How vote scores appear in listings and on reply cards
• How votes translate into reputation points
• How votes power the Popular sort and trending sidebar
• The one-vote-per-item rule and how to undo a vote

Voting on Topics and Replies

Every topic and every reply has an upvote button (thumbs up) and a downvote button (thumbs down). The net vote score (upvotes minus downvotes) is displayed between them.

To vote: Click the upvote or downvote button. The score updates instantly. No page reload.

To undo a vote: Click the same button again. The vote is removed and the score returns to its previous value.

To change your vote direction: Click the opposite button. Jetonomy removes your previous vote and applies the new one in a single action. The score adjusts correctly.

You must be logged in to vote. If you click a vote button while logged out, Jetonomy sends you to the WordPress login page and returns you to the same topic once you sign in.

Note: You cannot vote on your own posts or replies. The vote buttons are visible but disabled with a tooltip explaining why.

Note: When a space admin disables voting on a space, vote controls are removed from the interface entirely, not just greyed out. Members will not see the upvote or downvote buttons on any post or reply in that space.

Where Vote Scores Appear

Topic listing page - Each topic card shows the net vote score. This is how members quickly identify high-quality discussions without opening them.

Single topic page - The topic's vote score appears prominently alongside the title.

Reply cards - Every reply in a thread shows its vote score. In Q&A spaces, this score directly determines the Best sort order, making it easy to find the most helpful answer.

Vote scores are updated in real time as you vote. You never need to reload the page to see the current score.

How Votes Affect Reputation

When you receive votes on your content, your Jetonomy reputation score changes. Reputation is displayed on your public profile and powers your trust level progression.

Event	Reputation change
Your post is upvoted	+10
Your reply is upvoted	+5
Your reply is accepted as an answer (Q&A)	+15
Your post or reply is downvoted	-2
Your post is deleted by a moderator	-20

These are the defaults. Every value is admin-configurable per site under Jetonomy → Settings → Permissions → Reputation Points - positive numbers reward, negative numbers penalize, and any row you leave alone keeps its default. See Permissions Settings → Reputation Points for the full table and how to change a value.

Reputation is calculated and stored in real time. The moment someone votes on your content, your reputation score updates. There is no batch processing.

Casting a downvote does not cost you any reputation points. Downvotes are free for voters.

How Votes Power Content Discovery

Votes are not just cosmetic. They feed two core discovery features:

Popular sort - On the space listing page, the Popular sort orders topics by their net vote score. High-vote topics stay visible longer. New topics start at zero and rise based on community reaction.

Trending sidebar - The community home page and individual space pages show a trending sidebar highlighting the topics with the highest recent vote velocity, meaning they received the most votes in a short window. A post with 20 upvotes in 2 hours outranks one with 100 upvotes spread over a month.

In Ideas spaces, vote scores are the primary ranking signal on the roadmap view. Ideas with the most votes appear first, giving product teams a clear priority signal.

The One Vote Per Item Rule

Each member can cast exactly one vote per post and one vote per reply. The database enforces this with a unique constraint. There is no way to vote twice on the same item.

Toggling (undoing) and changing direction both work correctly within this constraint. At any moment, your vote on a given item is either +1, -1, or nothing.

If you vote on a topic in the listing view, then open the topic and vote again, you are interacting with the same vote record. The second click undoes the first vote.

What's Next?

Learn how to bookmark topics for quick access and how to follow spaces to get notified about new posts.

Bookmarks & Following →

Bookmarks and following are how members stay connected to the content they care about. Bookmarks are a personal reading list. Following a space is a subscription to that space's activity. Together they make sure your community members never lose track of an important discussion.

What You Will Learn

• How to bookmark a topic and access your bookmarks later
• How to remove a bookmark directly from the My Bookmarks page
• How to follow a space and what that means for notifications
• How auto-subscription works when you post or reply
• How to manage your subscriptions and turn off notifications

Bookmarking Topics

How to Bookmark

Open any topic and click the bookmark icon in the topic action bar (next to the share and report buttons). The icon fills to indicate the bookmark is saved. Click it again to remove the bookmark.

Bookmarking is instant and does not require a page reload. There is no confirmation dialog.

Accessing Your Bookmarks

Two ways to get there, both show the same list:

• The Bookmarks tab on your profile at /community/u/your-username/
• A dedicated standalone page at /community/bookmarks/ (new in 1.4.1)

Both list every topic you have bookmarked, most recent first. Each item shows the topic title, the space it belongs to, the author, and when it was posted. Click any item to go directly to the topic.

Bookmarks are private - other members cannot see your bookmark list. The standalone page requires sign-in and is excluded from search engines so the URL itself never reveals what you've saved.

Removing a Bookmark from the Bookmarks Page

Each card on the My Bookmarks page carries a bookmark icon button in the top-right corner. Clicking it removes the bookmark immediately - no confirmation dialog. The card fades out and disappears from the list so the page always reflects your current bookmark state.

The same toggle works in reverse too: if you accidentally remove a bookmark, re-open the topic and bookmark it again from the topic action bar.

Tip: Use bookmarks as a reading queue - bookmark topics you want to read later, then clear them as you go. The Bookmarks tab gives you a clean list without any algorithm reordering it.

Following Spaces

How to Follow

Visit any space and click the Follow button in the space header. The button changes to Following immediately.

Following a space subscribes you to new post notifications from that space. Every time a new topic is published in a space you follow, you receive a notification in your notification bell.

Unfollowing

Click Following in the space header to toggle it off. The button returns to Follow and you stop receiving new post notifications from that space.

Following a space does not make you a member of the space. In Open spaces, you can follow without joining - you will receive notifications but you will not be listed as a member and cannot post until you join.

What You Get Notified About

When you follow a space, you receive notifications for:

• Every new topic published in that space (including by authors you do not know)

You do not receive notifications for replies to topics in followed spaces unless you are also subscribed to those individual topics. Following is space-level; subscriptions are topic-level.

Topic Auto-Subscription

When You Create a Topic

When you publish a new topic, you are automatically subscribed to it. You will receive notifications for:

• Every new reply to your topic (including threaded sub-replies)
• When your topic is answered and accepted (Q&A spaces)
• When your topic's idea status changes (Ideas spaces)

When You Reply to a Topic

When you post a reply to any topic, you are automatically subscribed to that topic. You will receive the same notifications as if you had subscribed manually.

Unsubscribing from a Topic

Open the topic and click the ... menu at the top of the page, then select Unsubscribe. You will stop receiving notifications for new replies on that topic.

You can re-subscribe at any time using the same menu.

Managing All Your Subscriptions

Go to your profile's Settings page at /community/u/your-username/edit/ and open the Notifications section.

Here you can:

• See a list of all spaces you follow with a one-click unfollow option
• See topics you are subscribed to (the list shows the 20 most recent)
• Set your notification preference for email delivery (immediate, daily digest, or never)

Note: Daily and weekly email digests are a Jetonomy Pro feature. In the free plugin, email notifications are sent immediately for each event or not at all - based on your notification settings.

What's Next?

Learn how to save work-in-progress posts as drafts and schedule topics for future publication.

Drafts & Scheduled Posts →

Not every post is ready to publish the moment you start writing it. Drafts let you save work-in-progress posts and come back to them later. Scheduled posts let you write now and publish at a specific date and time automatically.

What You Will Learn

• How to save a post as a draft
• Where to find and manage your drafts
• How to schedule a post for future publication
• How the draft/schedule split-button UI works
• How scheduled posts are published and what happens if the window is missed

Saving a Draft

When you are composing a new topic and want to save your progress without publishing:

1. Write your title and content as usual.
2. Click the arrow next to the main Post button to expand the split-button menu.
3. Select Save as Draft.

Your draft is saved immediately and you are returned to the space listing. No notification is sent to other members. The topic does not appear in the space listing.

Tip: Press Ctrl+Enter (Windows/Linux) or Cmd+Enter (Mac) to trigger the composer's primary action without reaching for the mouse. This clicks the split-button's current primary button - for a new post that submits it; while editing a draft it runs whichever action the button currently shows.

Finding Your Drafts

Two ways to get there, both show the same list:

• The Drafts tab on your profile at /community/u/your-username/
• A dedicated standalone page at /community/drafts/ (new in 1.4.1)

Your drafts are listed in order of last-modified time, most recent first. The standalone page requires sign-in and is excluded from search engines, so unfinished work never leaks. Each draft shows:

• The post title (or "Untitled Draft" if you have not written a title yet)
• The space it is intended for
• When you last saved it

Click any draft to reopen the full composer with your saved content. Make your changes, then publish or save again.

Drafts are private. Only you and site admins can see your drafts.

Drafts and Post Counts

Draft posts do not count toward any community statistics until they are published:

• They do not increment the space's post count.
• They do not appear in the space listing.
• They do not appear in search results.
• They do not appear on your public profile's Posts tab.

The moment a draft is published, either manually or via scheduled publishing, all of the above update immediately.

Scheduling a Post

You can schedule a post to publish automatically at a specific future date and time:

1. Write your title and content.
2. Click the arrow next to the Post button to expand the split-button menu.
3. Select Schedule.
4. A date and time picker appears. Choose when you want the post to go live.
5. Click Schedule Post.

The post is saved with a Scheduled status. It does not appear publicly until the scheduled time.

Scheduled posts appear in your Drafts tab with a "Scheduled" label and the publish date/time displayed. You can click into a scheduled post to edit the content or change the publish time at any point before it goes live.

To cancel a scheduled post and convert it back to a draft, open it and click Unschedule.

How Scheduled Publishing Works

Jetonomy publishes scheduled posts through Action Scheduler - the same background queue that powers WooCommerce - which runs its own queue runner rather than relying purely on page views. The check runs every hour. (WP-Cron remains a legacy fallback for older installs.)

This means a post scheduled for 9:00 AM may publish at any point during the following hour rather than exactly on the minute.

If a post's scheduled time is missed (for example, because the queue did not run during a low-traffic period), Jetonomy will publish it on the next run. It never silently drops a scheduled post.

The Split-Button UI

The publish button in the post composer is a split button:

• Left side: The primary action (defaults to Post Now for new posts, Update for existing drafts).
• Right side (arrow): Opens the options menu with Save as Draft, Schedule, and any other contextual actions.

The left side updates based on context. When you are editing a draft, the left side shows Publish Now and the right side shows options to reschedule or keep as draft.

What's Next?

Learn the full set of moderation tools available to space moderators: moving, merging, splitting, pinning, closing, and deleting topics.

Topic Management →

Space moderators have a full toolkit for organizing, curating, and controlling discussions. Every action in this guide requires moderator permission on the space where the topic lives - or site-wide admin access.

What You Will Learn

• How to move a topic to a different space
• How to merge duplicate topics
• How to split a reply into a new topic
• How to pin and unpin topics
• How to close and reopen topics
• How to delete topics

Who Can Use These Tools

All moderation actions described here require one of the following:

• Space Moderator role in the space where the topic lives
• Space Admin role in that space
• WordPress Administrator (can moderate any space)

Regular members do not see moderation options in the menus, even if they are the topic author. Topic authors can edit and delete their own posts, but not pin, close, move, merge, or split them.

Moving a Topic to a Different Space

Use this when a topic was posted in the wrong space - for example, a bug report in a General Discussion space that belongs in a Support space.

1. Open the topic.
2. Click the ... menu at the top right of the topic.
3. Select Move Topic.
4. A modal appears with a searchable space picker. Type to filter spaces by name.
5. Select the destination space.
6. Click Move.

The topic disappears from the original space immediately and appears at the top of the destination space's listing. Its URL changes to reflect the new space slug. The old URL redirects to the new one automatically.

All replies, votes, bookmarks, and subscriptions move with the topic. Nothing is lost.

Tip: If you move a Q&A topic from a Q&A space into a Forum space, the accepted answer marking is preserved in the database, but the "Accepted" badge may not render in the Forum space depending on your display settings.

Merging Duplicate Topics

Use this when two members post the same question or idea in the same space. Merging moves all replies from the source topic into the target topic and deletes the source.

1. Open the topic you want to remove (the duplicate).
2. Click the ... menu and select Merge Topic.
3. A modal appears with a search field. Search for the target topic by title.
4. Select the target topic.
5. Click Merge.

All replies from the duplicate are appended to the target topic's reply list in chronological order. The source topic is permanently deleted - it is not moved to trash. A moderator note is added to the target topic indicating that replies were merged from another topic.

Warning: Merging cannot be undone. Verify you have selected the correct target topic before confirming.

Splitting a Reply Into a New Topic

Use this when a reply inside a topic starts a new conversation that deserves its own thread.

1. Find the reply you want to split.
2. Click the ... menu on that reply.
3. Select Split to New Topic.
4. A modal appears asking for the new topic title.
5. Enter the title and click Split.

Jetonomy creates a new topic in the same space with your chosen title. The selected reply becomes the first post content of the new topic. All sub-replies (direct children of that reply) move with it.

The original reply is removed from the source topic. A moderator note appears in the source topic: "A reply was split into a new topic: [title with link]."

Pinning and Unpinning Topics

Pinned topics appear at the top of the space listing, above all other topics, regardless of which sort tab is selected (Latest, Popular, or Unanswered). Use pinning for space rules, important reference threads, or a "start here" topic. Pinning here affects only this space - to feature a post across the whole community, see Community Announcements (Pro, admins only).

1. Open the topic.
2. Click the ... menu and select Pin.

The topic moves to the top of the listing immediately and shows a green Pinned badge - on both the listing row and the topic's own header - so members can see at a glance that it is pinned.

To unpin, open the same menu and select Unpin.

Each space allows up to 3 pinned topics by default. Once the limit is reached, pinning another topic returns "You can pin up to 3 topics in a space. Unpin one first." The cap keeps the top of the space scarce and meaningful; developers can change it with the jetonomy_max_space_pins filter.

Closing Topics

Closing a topic prevents new replies while keeping all existing content visible and readable. Use this when a question has been answered, a discussion has run its course, or a thread is becoming unproductive.

1. Open the topic.
2. Click the ... menu and select Close Topic.

Closed topics show a banner: "This topic is closed. No new replies can be added."

The reply composer is hidden for regular members. Moderators and admins can still reply to closed topics.

To reopen a topic, click the ... menu and select Reopen Topic.

Deleting Topics

Deleting a topic moves it to trash. It disappears from the space listing and is no longer accessible to members. The space's post count decrements.

1. Open the topic.
2. Click the ... menu and select Delete Topic.
3. Confirm the deletion in the prompt.

Deleted topics can be recovered by a site admin from Jetonomy → Content in the WordPress admin - filter by status "Trash" to find them. A trashed topic can be restored or permanently deleted.

Permanent deletion removes the topic, all replies, all votes, all bookmarks, and all associated notifications from the database. It cannot be undone.

Note: When you delete a topic, the topic author's reputation is reduced (a default of 20 points) to reflect the removed content. The penalty amount is admin-configurable under Settings → Permissions → Reputation Points.

What's Next?

Return to the Spaces & Categories section to learn about managing space membership and access rules.

Membership & Join Policies →

Two features that give you finer control over individual topics - mark sensitive topics private so only you and moderators can see them, and use colored prefixes to classify topics at a glance in the space listing.

What You Will Learn

• How to mark a topic as private and who can read it
• How to enable topic prefixes for a space
• How to create, edit, and color prefixes
• How prefixes appear in the space listing and topic page
• When to choose a private topic over a private space

Private Topics

A private topic is visible only to its author and to space moderators. Other members of the space cannot see it in the listing, cannot find it through search, and cannot open its URL directly - they receive a "not found" response instead.

Use private topics for:

• Support requests that include account details, order numbers, or personal information
• Reports of abuse or harassment where naming the other member in public would escalate the situation
• Personal asks to a space owner that do not need a full private message thread
• Sensitive billing or legal questions where a full support ticket is too formal

Enabling Private Topics on a Space

Private topics are an opt-in feature per space. The space owner turns them on from Jetonomy → Spaces → (your space) → Settings → Posting.

1. Toggle Allow private topics on.
2. Save.

If the setting is off, the Private toggle does not appear in the new post composer and members cannot create private topics in the space.

Creating a Private Topic

When the feature is enabled for a space, a Private toggle appears at the bottom of the new post composer. Turn it on before submitting and your topic is flagged as private.

Private topics show a Private badge next to the title on the topic page. The badge is visible only to you and to moderators (other members cannot see the topic at all).

Who Can See Private Topics

Role	Can see private topics?
Topic author	Yes
Space moderators	Yes
Space owner	Yes
WP admins	Yes
Other space members	No
Logged-out visitors	No

A moderator can reply to a private topic, mark it resolved, or escalate it to a full support ticket using whatever workflow your community has. The topic author is notified of replies the same way they would be on a normal topic.

Note: Private topics are different from private spaces. A private space is hidden entirely - a member either has access to everything in it or nothing at all. A private topic is a one-off exception inside an otherwise public space. Pick private spaces for ongoing confidential work (staff lounges, paying customer lounges) and private topics for one-off sensitive conversations.

Topic Prefixes

Prefixes are colored labels that appear in front of topic titles in the space listing. They let members classify topics at a glance - Bug, Question, Solved, Announcement, Discussion, and so on.

Prefixes are configured per space by the space owner. Different spaces can have entirely different prefix sets - a support space might use Bug, Question, Solved, while a marketing space might use Idea, Campaign, Report.

Enabling and Creating Prefixes

Go to Jetonomy → Spaces → (your space) → Settings → Prefixes.

1. Toggle Enable topic prefixes on.
2. Click Add Prefix.
3. Type a short label (up to 20 characters).
4. Pick a color from the palette, or enter a custom hex value.
5. Save.

Repeat for each prefix you want. Re-ordering a prefix in the admin changes its order in the composer picker. Prefixes you no longer need can be deleted - topics that used a deleted prefix revert to having no prefix.

Using a Prefix When Creating a Topic

When prefixes are enabled for a space, a Prefix dropdown appears next to the title field in the new post composer. Members pick one prefix per topic, or leave it blank.

If the space is configured with Require prefix enabled, the composer rejects the submission unless a prefix is selected.

Where Prefixes Appear

• In the space listing next to the topic title
• On the topic page, in the topic header above the title
• In search results
• In notification emails that reference the topic
• In the admin moderation queue

Filter the space listing by prefix by clicking any prefix label - the listing re-renders to show only topics with that prefix.

Prefix Color Guidelines

• Use high-contrast colors for critical prefixes (Bug in red, Announcement in blue)
• Use muted colors for passive prefixes (Discussion in grey)
• Avoid using green except for Solved or Done - green is a strong "resolved" signal
• Avoid using red except for critical prefixes - red grabs attention

What's Next?

Return to Creating Topics for a full walkthrough of the new post composer, or continue to the next discussion guide.

The composer is the box you type in when you create a new post or reply. It works like a modern community tool, not a plain comment form. Members can @mention each other, see at a glance which threads have new replies, and find out who runs a space and who on staff is replying. This guide covers each of those features and how they behave for the member.

What You Will Learn

• How @mention autocomplete works in posts and replies
• What the "New" pill on the topic card means and when it clears
• How the "Managed by" sidebar surfaces space admins and moderators
• Where role pills appear and what they tell members
• How link previews turn a pasted URL into a rich card
• How members add images, and which capability gates uploads
• How the composer's formatting toolbar and markdown shortcuts work

@mention Autocomplete

Type @ anywhere in the composer and Jetonomy opens a dropdown of matching people. Keep typing to narrow the list, then click a result or press Enter to insert the mention.

The inserted mention is a clickable link to the user's profile, and the moment your post or reply is published, Jetonomy fires a notification to the mentioned member. They see it in the bell menu and, if they have email notifications on, in their inbox.

Where It Works

Surface	Mentions supported
New post composer	Yes
Reply composer	Yes
Edit post / edit reply	Yes
Private message composer (Pro)	Yes
Quick reply on a topic card	Yes

Who Shows Up in the Dropdown

The dropdown is scoped to people the current user shares at least one space with. This keeps the list relevant on large communities and avoids leaking member names across private spaces. Within that scope, results are ordered by:

1. Recent contributors in the current space (they are most likely to be relevant)
2. Other members of the current space
3. People you share other spaces with

If you start typing a name that does not match anyone in your shared spaces, the dropdown shows "No matches" rather than searching the whole site.

Walkthrough: Mentioning a Member in a Reply

1. Open any topic and start a reply.
2. Type @ followed by the first few letters of the person's name or username.
3. The dropdown appears under your cursor with up to 10 matching members.
4. Use the arrow keys to highlight a name, or click directly.
5. Press Enter (or click) to insert the mention.
6. Publish the reply. The mentioned member receives a notification within seconds.

Notes on Privacy

• Mentions in a private space still notify the mentioned member, but the linked post is only visible to people who can read that space.
• Mentioning a member who has muted you still inserts the link, but no notification is sent.
• Site admins can disable mention notifications globally in Jetonomy → Settings → Notifications.

"New" Pill on Unread Threads

The space listing shows a card for each topic. When a topic has replies you have not read yet, a small "New" pill appears on the card.

The pill is intentionally subtle. It uses the --jt-accent design token, so it picks up your theme's brand color and matches dark mode automatically.

When the Pill Appears and Clears

Event	Pill state
Someone replies to a thread you previously read	Pill appears
You open the thread	Pill clears immediately
You scroll past the thread without opening it	Pill stays
The original poster edits their post (no new replies)	Pill does not appear
You are not signed in	Pill never appears (read state is per-user)

The pill is driven by the same read-status table that powers the unread indicator in the bell menu. There is no separate setting to toggle it. If you do not want unread tracking at all, disable read tracking in Jetonomy → Settings → Performance.

Mobile Behavior

On mobile the pill sits at the top-right of the card, sized for thumb readability without crowding the title. It uses the same touch target as the rest of the card, so tapping anywhere on the card opens the thread and clears the pill.

"Managed by" Sidebar Card

Every space page now shows a "Managed by" card in the sidebar. The card lists the space admin(s) and moderator(s) with their avatars and a small role badge next to each name.

What the Card Shows

• Up to 5 staff members per space, sorted with admins first, then moderators
• Each entry shows: avatar, display name, role badge
• Hovering an entry reveals a "View profile" link
• If the space has private messaging enabled (Pro), a "Message" link appears as well

If a space has more than 5 staff, the card shows the first 5 and a "See all staff" link that opens the full member list filtered to staff only.

Why This Helps Members

Members often want to ask a question, report a problem, or appeal a moderation action but don't know who to talk to. The "Managed by" card answers that question on every space page, without forcing members to dig through settings or member lists.

For owners, this surfaces your community staff and gives them visibility. Members are more likely to recognise and trust moderators they see consistently.

Customizing the Card

The card is rendered from templates/partials/managed-by-card.php. You can override it in your theme at theme/jetonomy/partials/managed-by-card.php to change the layout, hide certain roles, or add extra links.

Role Pills on Posts and Replies

In addition to the sidebar card, admins and moderators now have role pills next to their name on every post and reply they make. The pill is small, accessible, and uses theme tokens for color.

Role	Pill label	Pill style
Community Admin	"Admin"	Filled, accent color
Space Moderator	"Mod"	Outline, accent color
Member	(no pill)	n/a

The pills are visible to everyone, including signed-out visitors. They make it obvious when an answer comes from staff vs from another member, which matters for support spaces and Q&A spaces where members weigh staff replies more heavily.

Link Previews

Paste a URL on its own line in a post or reply and Jetonomy automatically fetches the page's metadata and renders a rich preview card beneath it, the same style of card you see when you share a link on LinkedIn or Twitter. Members get context (title, description, thumbnail, site name) without leaving the thread.

How It Works

When a link sits alone on its own line (not inline inside a sentence), Jetonomy calls GET /jetonomy/v1/link-preview?url=... and renders the result as a card. The card shows:

• Thumbnail image (when the page provides one)
• Page title
• Short description
• Site name and favicon

The preview endpoint pulls metadata from Open Graph and Twitter Card tags, so it covers almost any site with social tags (news outlets, blogs, GitHub, LinkedIn, Instagram, Facebook, and more). For the major sanctioned oEmbed hosts (YouTube, Vimeo, TikTok, Spotify, SoundCloud, Reddit, and the rest of the WordPress oEmbed registry) it returns a true rich embed instead of a static card.

Behavior and Limits

• Up to 3 preview cards render per post or reply, so a message full of links does not turn into a wall of cards.
• Results are cached on the server (roughly 12 hours for a successful fetch, a few minutes for a failed one), so a 200-reply thread does not refetch the same link 200 times.
• Mentions (@name) and tag links never turn into preview cards, only standalone web URLs do.

Developers can customize how link previews are fetched and rendered - see Developer Notes at the end of this guide.

Media Uploads

The composer lets members add images to posts and replies in three ways:

• Toolbar button - click the image button in the composer toolbar to open a file picker.
• Drag and drop - drag an image straight from your desktop onto the editor.
• Paste - paste a screenshot or copied image directly from your clipboard.

Uploads go to POST /jetonomy/v1/media, which stores the file as a standard WordPress attachment and returns its URL so the image drops into the editor inline. Every uploaded image is given alt text automatically (derived from the file name) for accessibility and SEO, and members can supply their own alt text.

Who Can Upload

In practice, most members who can post or reply can also attach images. Members who can already upload to your WordPress media library can attach images, and members earn the ability to upload automatically once they reach Trust Level 1, even if their WordPress role would not otherwise allow it. So a brand-new member may not be able to attach an image on their very first day, but gains it as soon as they reach Trust Level 1.

Developers who need the exact capability list can find it under Developer Notes.

The Formatting Toolbar

The composer is a single rich-text editor with a small formatting toolbar - there is no separate "plain text" vs "WYSIWYG" mode to choose between. The toolbar buttons are: bold, italic, inline code (</>), link, blockquote, and image upload.

Members who prefer to type can also use common markdown shortcuts (**bold**, *italic*, `code`, > quote) directly in the editor. The toolbar and the markdown shortcuts produce the same formatted result.

Paste handling, image uploads, and @mention autocomplete all work the same way regardless of whether you click a toolbar button or type the markup yourself.

For more on the content editor and its fields, see Creating Topics.

Developer Notes

These details are for developers extending the composer. Site owners and members do not need them.

Link preview filters

The link preview pipeline is fully filterable:

Filter	Purpose
jetonomy_link_preview_providers	Add or reorder host-specific providers (e.g. a custom intranet URL rewriter) ahead of the defaults
jetonomy_link_preview_data	Final mutation of the preview data right before it is cached and returned
jetonomy_link_preview_cache_ttl	Override the cache lifetime, in seconds
jetonomy_link_preview_user_agent	Override the user agent used when fetching the page (some corporate firewalls only allow specific agents)

Media upload capabilities

Uploading is gated by capability. A member can upload media if they have any one of:

• upload_files - the standard WordPress capability (Author and above)
• jetonomy_upload_media - the Jetonomy role-map capability, granted to the Contributor role and automatically granted at Trust Level 1
• jetonomy_create_posts or jetonomy_create_replies - anyone who can post or reply

Uploads go to POST /jetonomy/v1/media, which stores the file as a standard WordPress attachment and returns its URL.

What's Next?

Learn how Jetonomy's in-product modal toolkit replaces native browser dialogs with accessible, themeable confirmations.

Modals and Confirmations

Jetonomy 1.4.0 introduced an in-product modal toolkit that replaces the native browser confirm, alert, and prompt dialogs across the community. Native browser dialogs look like operating system pop-ups, cannot be themed, and don't follow modern accessibility patterns. The Jetonomy modals are themed, keyboard-accessible, and localised. The 1.4.2 retag completed full translation coverage for the button labels.

What You Will Learn

• What the modal toolkit replaces and why
• Where you'll see Jetonomy modals in the community
• How the modals handle accessibility and keyboard navigation
• How button labels translate for non-English sites
• How dark mode and theme colors are picked up automatically
• How to override the modal styling in your theme

What the Toolkit Replaces

JavaScript has three built-in dialog functions:

• window.confirm("Are you sure?") returns true / false
• window.alert("Done.") shows an info message
• window.prompt("Reason?") asks for a text input

These look like system pop-ups. They sit outside your theme, look different on every operating system and browser, can't be styled, and don't return focus to the right element when dismissed. Screen readers treat them inconsistently, and keyboard navigation is at the mercy of the browser.

Jetonomy now uses its own modal toolkit for every "Are you sure?" prompt across the plugin. The modals look like your community, behave consistently, and play nicely with screen readers and keyboards.

Where You'll See Jetonomy Modals

Anywhere the community needs to confirm an action or collect a short answer:

Action	Modal type
Delete a post or reply	Confirm
Remove a flag without taking action	Confirm
Ban or silence a member	Prompt (asks for duration / reason)
Lift a ban	Confirm
Move a topic to another space	Prompt (asks for target space)
Split a reply into a new topic	Prompt (asks for new topic title)
Pin or unpin a topic	Confirm
Mark all notifications read	Confirm
Trash a category	Confirm
Approve or reject pending content	Confirm
Cancel an unsaved edit	Confirm

The pattern is consistent: destructive actions always require a confirmation, prompts that need an answer always show a clear input field with sensible defaults.

Modal Types

The toolkit exposes three modal types:

• Confirm - two buttons (Cancel / Confirm). For yes/no decisions
• Alert - one button (OK). For one-way info or success messages
• Prompt - text input plus two buttons (Cancel / Submit). For collecting a short answer

Each type uses the same overlay and box, so the visual style is uniform across the community.

Accessibility

The toolkit is built to WCAG 2.1 AA. Every detail that screen reader users and keyboard users rely on is wired up:

Feature	Behaviour
Keyboard open	Focus moves to the first focusable element in the modal
Tab cycling	Focus stays trapped inside the modal until it closes
Escape key	Dismisses the modal, equivalent to clicking Cancel
aria-labelledby	Points to the modal title element
aria-describedby	Points to the modal body text
role="dialog"	Set on the modal box
aria-modal="true"	Tells assistive tech the rest of the page is inert
Focus return	When the modal closes, focus returns to the element that opened it
Overlay click	Closes the modal (configurable, off for destructive prompts)

Screen reader users hear the modal title and body when it opens. Keyboard users can tab through the controls without escaping the dialog. Mouse users can dismiss by clicking the overlay, except on destructive prompts where overlay dismiss is intentionally disabled to prevent accidental data loss.

Reduced Motion

If the visitor's operating system has "Reduce motion" enabled, the modal skips its slide-in and fade animations. The dialog still opens and closes; it just appears and disappears instead of animating. This respects vestibular accessibility preferences without compromising functionality.

Localisation

All button labels translate through the standard WordPress translation pipeline:

English label	Used in
Cancel	Every modal
Confirm	Confirm modals
OK	Alert modals
Submit	Prompt modals

Modal titles and body text are localised by the calling code (e.g. "Delete this post?" is translated by the delete action that opens the modal). The toolkit itself only contributes the four button labels above.

The 1.4.2 retag completed full translation coverage for every label. Before that retag, English fallbacks could leak into translated locales for one or two of the buttons. Sites running a translated locale (French, German, Spanish, Arabic, etc.) now see fully translated buttons everywhere.

Dark Mode

The modal box and overlay both use Jetonomy design tokens. That means:

• Dark theme active → modal renders dark automatically
• Light theme active → modal renders light
• Theme brand color → primary button picks it up
• Theme border radius → modal corners match

No per-theme configuration required. If your theme defines a custom --jt-bg or --jt-accent, the modal picks it up.

Styling Override

Site owners who want a custom look can override the modal styles in their theme stylesheet. The relevant classes are:

Class	Element
.jt-modal-overlay	The backdrop behind the modal
.jt-modal-box	The modal container
.jt-modal-title	The title heading inside the modal
.jt-modal-body	The body text or prompt input wrapper
.jt-modal-actions	The button row at the bottom
.jt-modal-button	Both buttons (Cancel / Confirm)
.jt-modal-button--primary	The primary (right-hand) button
.jt-modal-button--secondary	The Cancel (left-hand) button

Example: dimming the overlay further for a more cinematic feel.

.jt-modal-overlay {
  background: rgba(0, 0, 0, 0.7);
}

Example: making the modal a bit wider on desktop.

@media (min-width: 768px) {
  .jt-modal-box {
    max-width: 560px;
  }
}

We recommend overriding tokens (e.g. --jt-bg, --jt-radius) at the modal level rather than rewriting properties directly, so dark mode and theme switching keep working.

Developer Note

The toolkit exposes three global functions for any custom JavaScript that integrates with Jetonomy. Each returns a Promise.

The message is always the first argument; an options object follows.

// Yes/no confirmation
const confirmed = await window.jetonomyConfirm( 'This cannot be undone.', {
  title: 'Delete this post?',
  confirmLabel: 'Delete',
  danger: true,
} );

// One-button info dialog
await window.jetonomyAlert( 'Your changes are live.', {
  title: 'Saved',
} );

// Text input prompt
const reason = await window.jetonomyPrompt( 'Tell our moderators what is wrong.', {
  title: 'Why are you reporting this?',
  placeholder: 'Reason',
} );

The danger: true flag styles the confirm button in red and disables overlay-click dismiss. Useful for delete confirmations and account actions.

These are pure JS globals; you don't need to import anything if jetonomy is already enqueued on the page.

What's Next?

Learn how the activity log tracks every audit-worthy event in your community.

Activity Log

Members normally start a topic from inside a space. But you can also drop a "start a topic" box onto any WordPress page, post, or landing page - so a visitor can begin a discussion without first navigating into the community. Jetonomy gives you two ways to do this, and both produce the same box: a Gutenberg block and a shortcode.

What You Will Learn

• Where the embedded composer is useful
• How to add it with the Compose Topic block (Gutenberg)
• How to add it with the [jetonomy_compose_topic] shortcode (Classic editor and page builders)
• The difference between "picker" mode and "fixed" mode
• What logged-out visitors see

When to Use It

The embedded composer is handy when you want members to start a discussion from outside the community pages, for example:

• A "Ask the community" box on your homepage or a landing page
• A support page that drops members straight into your Support space
• A product page that invites feedback into an Ideas space

Adding It with the Block (Gutenberg)

1. Edit any page or post in the WordPress block editor.
2. Click the + (Add block) button.
3. Search for Jetonomy Compose Topic and insert it.
4. In the block sidebar, choose how the box behaves (see Picker vs Fixed Mode below).
5. Publish or update the page.

Adding It with the Shortcode

If you use the Classic editor, a widget, or a page builder (Elementor, Divi, Bricks, WPBakery), use the shortcode instead. It produces an identical box.

[jetonomy_compose_topic mode="picker"]
[jetonomy_compose_topic mode="fixed" space_id="5"]

The block and the shortcode are interchangeable - either surface works and they render the same composer, so pick whichever fits your editor.

Picker vs Fixed Mode

The composer has two modes, set with the mode attribute (block sidebar control or shortcode attribute):

Mode	What it does
Picker (default)	Shows a space dropdown so the member chooses which space their topic lands in. Only spaces where the member is allowed to post appear in the list.
Fixed	Locks the box to one space - no dropdown. Use this on a page that is clearly about a single topic area (e.g. a Support page that always posts into the Support space). Set the space with space_id (the Space ID to post into control in the block).

If you choose Fixed mode but the space is missing or the member cannot post in it, the box quietly falls back to Picker mode rather than showing an error.

Limiting the Post Types

The types attribute controls which kinds of topic the box can create. By default it allows topic,question,idea. Remove any you do not want to offer on that page. (The actual post type a member ends up creating still follows the space type - see Creating Topics.)

What Logged-Out Visitors See

If a visitor is not signed in, the box does not show a form. Instead it shows a "Sign in to start a new topic" prompt that returns them to the same page after they log in. There is no exposed form for signed-out visitors, so you can safely place the composer on a public page.

Related

• Creating Topics - the full new-post composer, field by field
• Search & Filters - help members find existing discussions before they start a new one
• For the full attribute reference and developer details, see Shortcodes, Widgets & Blocks

Every public space in Jetonomy publishes an RSS 2.0 feed. Members can subscribe in any feed reader and receive new discussions as they are published, without visiting the community.

What You Will Learn

• The URL format for a space's RSS feed
• Which spaces publish a feed and which do not
• How feed readers auto-discover the feed
• What each feed item contains

Feed URL

Each public space serves its feed at:

/community/s/{slug}/feed/

Replace {slug} with the space's URL slug - the same segment that appears in the space URL at /community/s/{slug}/. For example, the "Announcements" space at /community/s/announcements/ publishes its feed at /community/s/announcements/feed/.

If your community uses a custom base slug (configured under Jetonomy → Settings → General), replace community with that slug.

Which Spaces Publish a Feed

A feed is only served when two conditions are both true:

1. The community visibility is set to Public (the global setting under Jetonomy → Settings).
2. The space itself is Public - meaning an anonymous visitor can read it.

Private spaces and Hidden spaces do not publish a feed. Requesting /community/s/{slug}/feed/ for a private or hidden space returns a 404, not a feed. This ensures that gated content never leaks through a feed URL that gets shared or cached by an aggregator.

Auto-Discovery

When a visitor or browser extension loads a public space page, Jetonomy adds a <link> tag to the HTML <head> that points to the feed:

<link rel="alternate" type="application/rss+xml" title="Space Name - RSS" href="/community/s/slug/feed/" />

Feed readers and browser extensions that support auto-discovery (most do) detect this tag automatically. Members can subscribe by pasting the space URL into their feed reader - they do not need to know the /feed/ URL in advance.

Auto-discovery is only emitted on public spaces. Private and hidden space pages do not emit the <link> tag.

What Each Feed Contains

Each feed includes the 20 most recently published topics in the space, newest first. There is no pagination - feeds are a rolling snapshot of recent activity.

Each item in the feed includes:

Field	Value
Title	The topic title
Link	The canonical URL of the topic
Publication date	When the topic was published (in RFC 822 format)
Author	The member's display name
Description	A plain-text excerpt of the topic body (approximately 55 words)

Replies are not included in the feed. The feed covers top-level topics only.

Developer Notes

The feed respects the jetonomy_space_feed_posts filter, which lets developers modify the list of posts before the XML is rendered:

add_filter( 'jetonomy_space_feed_posts', function ( array $posts, object $space ): array {
    // Remove posts by specific authors, add extra items, etc.
    return $posts;
}, 10, 2 );

What's Next?

Learn about the Community Media page where site administrators can review and manage member uploads.

Community Media →

Jetonomy's search finds content across your entire community in real time - topics, spaces, and tags - and lets you narrow results with powerful filters so members always land on exactly what they need.

What You Will Learn

• How to run a full-text search from anywhere in the community
• What the filter pills do and how to use them
• How advanced filters refine results by date, author, tag, and sort order
• How to show and hide the filter bar
• How developers can extend search filters with a custom hook

Running a Search

The search bar sits in the community navigation, visible on every page. Type any keyword and press Enter or click the search icon. Jetonomy searches across:

• Topic titles and content
• Space names and descriptions
• Tag names

Results appear on the search results page at /community/search/. Each result card shows the content type, the space it belongs to, the author, the date, and a short excerpt with your search term highlighted.

Tip: Every word you type is required (AND), matched as a prefix - searching email digest finds posts containing both email... and digest.... Short words (under 4 characters) are ignored, so lead with the distinctive terms.

Filter Pills

At the top of the results page, four filter pills let you narrow by content type instantly:

Pill	Shows
All	Every matching result
Posts	Topic results only
Spaces	Space results only
Tags	Tag results only

Click any pill to filter. The URL updates so you can share a filtered search link with your team.

Advanced Filters

Click the Filters disclosure to expand the advanced filter bar. It auto-expands whenever any filter is already active. These filters stack - you can combine them in any combination.

Date Range

Set a Date from and / or Date to date to restrict results to a window. Jetonomy filters by the post's original publish date, not its last reply date.

Author

Type a name or username to filter results to a specific author. Jetonomy resolves it to the matching member when you submit the search (there is no live typeahead). This is useful for reviewing a particular member's contributions or finding your own older posts.

Tag

Type a tag name to restrict results to posts that carry that tag. Combining author and tag filters is a fast way to find all posts by a specific member on a specific topic.

Sort Order

Option	Orders by
Relevance	Full-text match score (default)
Newest	Most recently published first
Most Voted	Highest net vote score first

Relevance is the default because it surfaces the best textual match. Switch to Newest when you know you are looking for a recent discussion. Switch to Most Voted when you want the community's highest-rated answer on a topic.

Collapsing the Filter Bar

Click Filters again to collapse the bar. Your active filters remain applied even while the bar is collapsed.

For Developers: Extending Search Filters

To modify the search query itself, use the jetonomy_search_query_args filter. It receives the assembled query arguments (q, space_id, date_from, date_to, author_id, tag_slug, sort) and must return the array.

add_filter( 'jetonomy_search_query_args', function( $args ) {
    // Restrict the query to a specific space.
    if ( ! empty( $_GET['space_id'] ) ) {
        $args['space_id'] = absint( $_GET['space_id'] );
    }
    return $args;
} );

To render extra controls in the filter bar, hook the jetonomy_search_filters action. It is a do_action (it returns nothing) fired just after the filter form, with three arguments: the query string $q, the active $filter pill, and an array of the current filter values.

add_action( 'jetonomy_search_filters', function( $q, $filter, $filters ) {
    // Echo your own markup for an extra filter control here.
}, 10, 3 );

See the Hooks Reference for the full parameter list.

What's Next?

Learn how tags work across spaces and how members can browse tag pages to find related content.

Tags →

Related Pro Features

• SEO Pro - per-space meta, schema.org markup, OG/Twitter cards, and sitemaps so search engines surface your community.

Tags connect related discussions across your entire community. A member searching for help with "payments" can click the payments tag and instantly see every relevant topic - no matter which space it lives in.

What You Will Learn

• How to add tags when creating a topic
• How tag pills work on topic listings
• How tag pages bring together content from multiple spaces
• How to start a new discussion directly from a tag page
• How the Popular Tags sidebar section helps members discover content
• Why consistent tagging improves search and community quality

Adding Tags to a Topic

When creating or editing a topic, the Tags field appears below the content editor. Type one or more tag names separated by commas - for example python, django, architecture.

Reuse existing tag names whenever possible - reusing tags makes the tag page more useful for everyone who follows that topic, and matching an existing name (rather than a typo) keeps related posts together.

Tip: In Q&A spaces, good tags are the fastest route to an answer. A question tagged with "payments" and "stripe" will appear on both tag pages, doubling its chance of being seen by someone who can help.

Tag Pills on Topic Listings

Every topic card in a space listing shows its tags as small pills below the title. Clicking a tag pill takes you directly to that tag's page - you do not leave the flow to reach it.

Tags in listings are a fast way to browse by topic without running a search. If a space covers multiple subjects, tag pills help members navigate without scrolling through unrelated posts.

Tag Pages

Every tag has a dedicated page at /community/tag/tag-slug/. The tag page shows all published topics across all spaces that carry that tag, sorted by Latest (newest first) by default.

Members can switch the sort to Popular to find the best content on that topic - Popular orders by net vote score.

Tag pages are publicly accessible by default. If your community is private, tag pages respect the space access rules - topics in private spaces are not shown on tag pages to members who do not have access to those spaces.

Start a Discussion from a Tag Page

Logged-in members see a Start a discussion tagged [tag name] button in the tag page header. Clicking it opens the composer in the most active space for that tag with the tag already filled in - one click from browsing a topic to contributing to it.

The button only appears when the tag has at least one existing post, so it always points to a space where the conversation is already happening.

Popular Tags Sidebar

The Popular Tags section in the community sidebar lists the most frequently used tags across your community (up to 15), each linking to its tag page with a post count. It appears automatically - there is nothing to configure.

Developers can hide it with the jetonomy_show_sidebar_popular_tags filter:

add_filter( 'jetonomy_show_sidebar_popular_tags', '__return_false' );

To inject custom markup (an ad, a banner, a related-tags block) directly around the Popular Tags section, hook the jetonomy_sidebar_before_popular_tags or jetonomy_sidebar_after_popular_tags actions. Each receives the current space object, or null when the sidebar renders outside a space:

add_action( 'jetonomy_sidebar_after_popular_tags', function ( $space ) {
    // Echo your own markup below the Popular Tags list here.
} );

Headless and app consumers can read the same tag list over REST: GET /jetonomy/v1/tags returns tags ordered by popularity (or alphabetically with ?sort=alphabetical), with a limit of up to 100. See the Hooks Reference for the full parameter list.

How Tags Improve Your Community

Tags work across space boundaries. A tag named "onboarding" can tie together a tutorial in your Guides space, a question in your Q&A space, and a feature idea in your Ideas space. Members following that tag see the full picture regardless of which space each post lives in.

Encouraging consistent tag use - especially in high-traffic spaces - pays dividends in search quality. Jetonomy's full-text search treats tags as a search signal, so well-tagged posts surface higher in relevant queries.

Note: Tags are shared across all spaces. There is one global tag namespace. A tag created in your Support space appears on the same tag page as the same tag used in your Ideas space.

Admin Tag Management

Members create tags on the fly as they post, but admins get a dedicated management screen for the whole global tag namespace at Jetonomy → Tags in the WordPress admin. Managing tags here requires the jetonomy_manage_settings capability.

The page lists every tag with its post count and gives you these controls:

Action	What it does
Add New Tag	Create a tag directly from the admin (name, optional slug) without having to post first
Edit	Rename a tag or change its slug. The change applies everywhere the tag is used
Delete	Remove a single tag. You can force-delete a tag even when posts are still attached to it
Bulk Delete	Tick multiple tags, choose Delete from the bulk-action dropdown, and click Apply to clear several at once

The list also has a search box and a per-page picker, and it paginates so it stays fast even on communities with thousands of tags.

Use this screen to clean up duplicate or misspelled tags (for example merging "stripe" and "Stripe" by deleting the stray one), retire tags that are no longer relevant, or pre-create the canonical tags you want members to reuse. Because the namespace is global, an edit or delete here affects every space at once.

What's Next?

Learn how trending surfaces the discussions your community is talking about right now, and how to place a trending list anywhere on your site.

Trending →

Trending surfaces the discussions that are catching fire right now, so members always see what the community is talking about today - not just the all-time greatest hits. It is one of the three ways members discover content in Jetonomy, alongside search and tags.

What You Will Learn

• Where members see trending content out of the box
• How trending is calculated (recent engagement, not lifetime score)
• How to surface a trending list anywhere on your site with the Trending block or shortcode
• How to scope trending to a single space and change the time window

Where Members See Trending

Two trending surfaces ship with Jetonomy, and they answer slightly different questions.

The sidebar Trending widget (automatic)

Every community page shows a Trending card in the sidebar with the top five topics. It appears automatically - there is nothing to configure. When a member is viewing a space, the card shows that space's top topics; everywhere else it shows the community-wide top topics. This card ranks by net votes (then reply count) and respects privacy, so private topics never leak to members who cannot access them.

The Trending block and shortcode (you place it)

When you want a "what's hot this week" list on a landing page, the community home, or any WordPress page or post, use the Trending Topics block or the [jetonomy_trending_posts] shortcode. Unlike the sidebar card, this list ranks by a time-decayed hot score so genuinely active recent discussions rise to the top instead of old topics that simply accumulated a lot of votes over time.

How Trending Is Calculated

The Trending block and shortcode score each topic on recent engagement, not its lifetime total. A topic's hot score combines its votes and replies, then decays as the topic ages, so a discussion that picked up ten replies yesterday outranks one that collected the same activity months ago. Only topics published within the time window (7 days by default) are considered.

This is by design: trending is meant to answer "what is the community talking about right now", which is exactly what brings members back day after day.

Placing a Trending List on a Page

Using the block

1. Edit any page or post in the WordPress block editor.
2. Click the + inserter and search for Trending Topics.
3. Drop the block in. It renders a live, ranked list of hot topics with rank numbers.
4. Adjust the block settings in the sidebar - number of topics, a specific space, the time window, and whether to show the header.

Using the shortcode

Paste [jetonomy_trending_posts] into any page, post, or text widget. The block and the shortcode share the same render path, so you get identical output either way - use whichever fits your page builder.

[jetonomy_trending_posts count="10" window="14"]

Attributes

Block setting	Shortcode attribute	What it does	Default
Number of topics	count	How many topics to list	5
Space	space_id	Limit trending to a single space (0 = whole community)	0 (all spaces)
Time window	window	How many recent days to score, in days	7
Show header	showHeader (block only)	Show or hide the "Trending" heading	On

If there are no qualifying topics in the window yet, the block shows a friendly "No trending discussions yet" message rather than an empty box.

What's Next?

Learn how Jetonomy's trust system automatically identifies your most reliable members and gives them more capabilities over time.

Trust Levels & Reputation →

For Developers

• Block name: jetonomy/trending. Shortcode: [jetonomy_trending_posts]. Both call the same render path, so block/shortcode output is identical.
• The hot score is computed in Post::list_trending( $limit, $space_id, $window_days ).
• The sidebar Trending card can be hidden with the jetonomy_show_sidebar_trending filter, and you can inject markup around it with the jetonomy_sidebar_before_trending / jetonomy_sidebar_after_trending action hooks (each receives the current $space or null). See the Blocks & Shortcodes reference and the Hooks Reference.

Jetonomy's trust system automatically promotes reliable members to higher privilege levels as they earn reputation - so you spend less time manually managing who can do what, and your most active members get recognized for their contributions.

What You Will Learn

• What the six trust levels are and what each one unlocks
• How members earn reputation points
• How automatic promotion works
• How to adjust thresholds in your admin settings
• How trust badges appear on member avatars

The Six Trust Levels

Jetonomy has six trust levels, numbered 0 through 5. Every new member starts at Trust Level 0. Levels 1 through 3 are earned automatically when a member meets the configured requirements. Levels 4 and 5 are not earned automatically - they are granted manually by an admin.

Promotion to levels 1-3 is based on a combination of activity stats, not a single reputation number. A member must meet every requirement listed for a level to reach it.

Level	Name	Default Requirements
TL0	Newcomer	Automatic on signup
TL1	Member	5 posts, 3 days active, 10 replies received
TL2	Regular	30 posts, 20 days active, 50 reputation
TL3	Trusted	100 posts, 60 days active, 200 reputation
TL4	Leader	Manually granted by an admin
TL5	Moderator	Manually granted by an admin

What Each Level Unlocks

Trust levels expand what a member can do without moderator intervention.

Capability	TL0	TL1	TL2	TL3	TL4	TL5
Create topics	Yes	Yes	Yes	Yes	Yes	Yes
Post replies	Yes	Yes	Yes	Yes	Yes	Yes
Flag content	Yes	Yes	Yes	Yes	Yes	Yes
Upload images	No	Yes	Yes	Yes	Yes	Yes
Edit / delete own posts	No	Yes	Yes	Yes	Yes	Yes
Daily post and rate limit lifted	No	Yes	Yes	Yes	Yes	Yes
Skip CAPTCHA	No	No	Yes	Yes	Yes	Yes
Create new spaces	No	No	Yes	Yes	Yes	Yes
Recategorize and rename others' topics	No	No	No	Yes	Yes	Yes
Moderate content and manage members	No	No	No	No	Yes	Yes
Manage settings, categories, and analytics	No	No	No	No	No	Yes

Each level adds to the one below it - a Trusted member (TL3) keeps everything TL1 and TL2 unlocked and gains the recategorize/rename abilities on top. Note that the higher levels are not just lifted limits: TL2 members can start their own spaces, TL3 members can tidy up the category and titles of any topic, and TL4/TL5 members effectively act as community staff (moderation, member management, and - at TL5 - settings, categories, and analytics).

Space moderators and WordPress admins always have full capabilities regardless of trust level.

Note: "Rate limit lifted" at TL1 refers to the per-day posting caps that apply to brand-new (TL0) accounts - 3 topics, 10 replies, and 5 votes per day by default. Those caps and how to tune them are covered in Anti-Spam Protection → Rate Limiting for New Members.

How Members Earn Reputation

Reputation is updated in real time whenever a qualifying event occurs.

Event	Points
Your topic is upvoted	+10
Your reply is upvoted	+5
Your reply is accepted as an answer (Q&A)	+15
Your idea is moved to Planned/Shipped	+20
A flag you submitted is confirmed	+5
Your topic or reply is downvoted	-2
Your post is reported	-10
A moderator deletes your content	-20

Every point value is editable at Jetonomy → Settings → Permissions → Reputation Points - adjust any action's score without touching code.

Reputation points accumulate on your public profile. The leaderboard ranks members by reputation score - see the Leaderboard doc for details.

Automatic Promotion

A cron job runs twice daily to evaluate all members against the current requirements for levels 1-3. Any member who meets every requirement for the next level is automatically promoted.

Promotion is silent - members are not notified by default. You can add a welcome notification using the jetonomy_trust_level_changed action hook if you want to acknowledge promotions.

Demotion works the same way. If a member's reputation falls below a threshold (for example, because posts were deleted), they are automatically moved back to the appropriate level on the next cron run.

Tip: You can set a member's trust level directly from Jetonomy → Users in the WordPress admin. Find the user and click Change Trust Level, then pick the level. This is a manual override that sets the level immediately - useful for elevating a known expert or correcting an edge case.

The Jetonomy → Users page is the central place to manage individual members: each row shows the member's trust level, post and reputation stats, and per-row controls to Change Trust Level and to Ban / Unban (covered in Banning Members).

Configuring Thresholds

Go to Jetonomy → Settings → Permissions to adjust the promotion requirements. Each of the three earned levels (1, 2, and 3) has its own row with four inputs: posts, days active, reputation, and replies received. A member must meet every value in a row to reach that level. Changes take effect on the next cron run.

Levels 4 and 5 have no requirement inputs - they are granted manually from Jetonomy → Users and cannot be earned automatically.

Lower requirements make promotion faster and more accessible. Higher requirements make higher trust levels a meaningful achievement. There is no right answer - tune these to the pace and size of your community.

Note: Setting a requirement to 0 removes it as a gate for that level. For example, setting a level's reputation requirement to 0 means members can reach it on activity stats alone.

Trust Badges on Avatars

Each trust level has a colored badge that appears on a member's avatar across topic listings, reply cards, and their profile page. The badge uses the data-jt-tl attribute so you can restyle it in your theme using CSS if needed.

Level	Badge Color
TL0	Grey
TL1	Blue
TL2	Green
TL3	Teal
TL4	Purple
TL5	Gold

Why Trust-Based Moderation Beats Manual Role Assignment

In a traditional forum, you manually decide who is a "trusted" member. That does not scale. With Jetonomy's trust system, your community self-selects. Members who contribute quality content earn their way to higher levels automatically. You only need to intervene in edge cases - banning bad actors or manually elevating a known expert to a higher level.

For Developers

Trust and moderation events fire WordPress action hooks you can listen to in a small custom plugin or your theme's functions.php - for example to send a welcome message when a member is promoted, or to log every resolved flag to an external system:

• jetonomy_trust_level_changed - fires when a member's trust level goes up or down.
• jetonomy_flag_resolved - fires when a moderator marks a flag valid or dismisses it.
• jetonomy_sidebar_auth_card - lets you add content to the community sidebar.

The full signatures (parameters and when each one runs) are in the Hooks Reference in the developer guide.

What's Next?

Learn how members can flag content for review and how flagged content reaches the moderation queue.

Flagging & Reporting Content →

Flagging lets any logged-in member report content that breaks your community rules. It is the first step in the moderation pipeline - members surface problems, and your moderators review and act.

What You Will Learn

• How to flag a topic or reply
• How to report an entire member account
• How to block a member from the mobile app or the REST API
• What information a flag captures
• What the reason categories mean and where they come from
• Who can flag content and what the restrictions are
• What happens to flagged content before a moderator reviews it
• How flags flow into the moderation queue

How to Flag Content

Every topic and every reply has a ... (more actions) menu. Open it and click Report. A prompt dialog appears asking why you are reporting the content. Type a brief description of the problem - for example, "This contains spam links" or "This is abusive toward another member" - and confirm.

The flag is saved immediately and you receive a confirmation message. The text you type is stored as the flag's description; the member-side report files every flag under the Other reason category, and moderators see that category alongside your description when they review it.

Tip: A good flag reason helps moderators act faster. "Spam" alone works, but "Contains a link to a commercial site unrelated to this community" gives the moderator everything they need without having to investigate.

Who Can Flag Content

Any logged-in member can flag a topic or reply, regardless of their trust level. There is one restriction: you cannot flag your own content.

The flag button is not visible to guests (logged-out visitors). If you want guests to be able to report content, you will need a custom solution - the built-in flagging system requires authentication.

There is no daily limit on flags per member. A member who finds multiple pieces of problematic content can flag all of them.

Reporting a Member

Flagging is not limited to individual posts and replies - a member can also report an entire user account. This is for cases where the problem is the person rather than one piece of content (for example, a member sending unwanted messages or repeatedly causing trouble across many topics).

To report a member, open their profile page (/community/u/their-username/) and click the Report button next to the Message button. A prompt asks why you are reporting the user; type a brief reason and confirm. As with content flags, you cannot report your own account, and the control only appears to logged-in members.

A user report creates a flag the same way a content report does - it is recorded against that member's account, captures your reason text and your name as the reporter, and surfaces in the moderation tools for a moderator to review and act on (for example, by banning the member if the report is justified).

Blocking a Member (1.8.0+)

Blocking hides a member's replies from your own view without removing them for anyone else - useful when you want to stop seeing someone's content without waiting on a moderator. As of 1.8.0, blocking is available from the mobile app and the REST API.

You can report the member in the same action - blocking and filing a report travel together in one request, so members do not need to submit them separately.

If the blocked member's reply has other replies nested underneath it, only their own content is hidden; the innocent replies in that nested thread stay visible.

Note: Blocking is a personal, per-viewer preference. It does not stop the blocked member from posting, and moderators and other members still see everything as normal. To remove someone's ability to post at all, a moderator needs to ban them.

What a Flag Captures

When a flag is submitted, Jetonomy records:

• The content or member being flagged (a post, a reply, or a user account, with its ID)
• The member who submitted the flag
• The reason category and the reason text they entered
• The timestamp

Moderators see all of this information when they review the flag in the moderation queue.

Reason Categories vs Free Text

When a moderator opens the queue, each flag shows a reason category - one of Spam, Offensive, Off-topic, Harassment, or Other. The built-in Report button that members click always files under the Other category and stores their typed description, so most member-submitted flags you see will be tagged Other with a free-text note.

The other categories (Spam, Offensive, Off-topic, Harassment) come from automated and advanced paths - the REST API, WP-CLI, and Jetonomy Pro's moderation automation - which can file a flag with a specific structured reason. So if you see category chips other than Other in your queue, those flags were raised by an integration or automation rule, not chosen by a member in the standard report dialog.

What Happens to Flagged Content

Flagging alone does not change the visibility of a post or reply. The content stays live and readable by all members until a moderator reviews it and takes action. This is intentional - hiding content automatically on a single flag would allow abuse of the flagging system.

A moderator can then mark the flag Valid (confirming the content breaks the rules, which trashes it) or Dismiss it (marking it unfounded, leaving the content live). See the Moderation Queue guide for the full review workflow.

Note: If the same piece of content receives multiple flags from different members, all flags are grouped under that content item in the moderation queue. Moderators see the total flag count and each individual reason.

Preventing Flag Abuse

Jetonomy does not currently auto-penalize members who submit flags that moderators consistently dismiss. If you have a member who is abusing the flagging system, handle it by adjusting their trust level or banning them from Jetonomy → Users in the WordPress admin.

What's Next?

See how flagged content and posts pending approval appear in the moderation queue, and learn how moderators take action.

Moderation Queue →

The moderation queue is your single dashboard for everything that needs human review - posts waiting for approval, flagged content, and items caught by spam filters. You can action everything from one page without digging through individual topics.

What You Will Learn

• How to access the moderation queue
• What types of content appear in the queue
• What actions you can take on each item
• How per-space moderation differs from global moderation
• How Akismet-held content appears in the queue
• Where to ban a member when content-level actions are not enough

Accessing the Moderation Queue

Go to Jetonomy → Moderation in your WordPress admin. The page is also accessible from the frontend at /community/mod/ - WordPress Administrators and users with the jetonomy_moderate capability can access both routes.

The queue shows a count badge on the admin menu item whenever there are items waiting for review.

What Appears in the Queue

The queue is split into four tabbed views, each with a count of how many items it holds:

Pending Posts

These are topics submitted in a space with Require Post Approval enabled. They are not visible to other community members until a moderator approves them.

Each pending item shows the full content, the author, the space it was submitted to, and how long it has been waiting. Items are ordered oldest first so nothing sits in the queue unnoticed.

Automated checks can also route content here. Jetonomy Pro's AI spam detection and moderation rules can place a post or reply into this held "pending" state for review rather than publishing it outright.

Pending Replies

The same as Pending Posts, but for replies awaiting approval in spaces that require it. Replies get their own tab so you can clear topics and replies independently.

Flags

These are live topics and replies that members have flagged for review. Flagged content stays visible in the community until a moderator acts. Each item shows the content, the flag reason(s), how many unique members flagged it, and the timestamp of the most recent flag.

Banned Users

A list of members who are currently banned, with the option to lift each ban. See Banning Members for the full ban workflow.

Available Actions

Actions differ between the pending tabs and the Flags tab.

On Pending Posts and Pending Replies, each item has three buttons:

Action	What it does
Approve	Publishes the pending post or reply so the community can see it
Spam	Marks the content as spam and moves it to trash; updates Akismet's spam training if Akismet is active
Trash	Moves the content to trash without marking it as spam

On the Flags tab, each flag row has two buttons:

Action	What it does
Valid (Trash)	Confirms the flag was justified - the content is trashed and the flag resolved
Dismiss	Marks the flag unfounded - the content stays live and the flag is resolved

Tip: Use Spam rather than Trash when content is clearly commercial spam. This trains Akismet for your site, making future auto-detection more accurate.

Spam and Trash ask for confirmation. Both actions remove content, so clicking either one opens a confirmation dialog before anything is deleted - individually per row and for the bulk action across selected rows. Approve does not prompt, since it only publishes. This guards against a misclick trashing a legitimate post.

The flag counter updates live. When you resolve a flag (Valid or Dismiss), the resolved row is removed and the "N pending" flag badge decrements immediately, without a page reload. When the last flag is cleared, the badge disappears. You always see the true outstanding count without refreshing.

Per-Space vs Global Moderation

The queue shows content from all spaces by default. Use the Space filter dropdown at the top of the queue to narrow to a single space. This is useful when you have dedicated space moderators - a moderator for your Support space only needs to see Support space items.

Space moderators who do not have global admin access see only their own spaces' items when they visit /community/mod/. They do not see content from spaces they do not moderate.

Fixed in 1.4.1: moderators of multiple spaces now see every queue they own when they visit /community/mod/. Earlier versions could redirect a multi-space moderator away from the dashboard if access checks ran in the wrong order. If you have moderators who report "I can see one space's queue but not the others," update to 1.4.1 and the dashboard will load all of them.

Akismet Integration

If the Akismet Anti-Spam plugin is active and configured on your site, Jetonomy automatically passes new posts and replies through Akismet before saving them. If Akismet marks content as spam:

• The post or reply is saved with a Spam status (not Pending)
• It does not appear in the community

Spam-flagged content is set to a Spam status rather than surfaced as a dedicated tab in the moderation screen. The four moderation tabs are Pending Posts, Pending Replies, Flags, and Banned Users.

Note: Akismet integration requires the Akismet plugin to be installed, activated, and connected with a valid API key. Jetonomy does not bundle Akismet - it integrates with it automatically when present.

Banning Members

Approve, Mark as Spam, and Trash all act on individual pieces of content. When a member is repeatedly disruptive, content-level actions are not enough and you need to act on the person instead. The Banned Users tab here shows everyone who is currently banned, with an Unban control on each row.

Banning is a subsystem of its own - three ban types, durations, auto-expiry, and the Jetonomy → Users admin page - covered in full in its own guide.

Banning Members →

What's Next?

Learn about Jetonomy's built-in anti-spam tools - reCAPTCHA, Turnstile, and rate limiting - that reduce how much reaches the moderation queue in the first place.

Anti-Spam Protection →

Related Pro Features

• Advanced Moderation - automated content rules that act before items ever reach the queue.

Spam is the fastest way to kill a community's quality. Jetonomy has multiple layers of protection that work silently in the background - your real members never know they are there.

What You Will Learn

• How to enable reCAPTCHA v3 or Cloudflare Turnstile
• Where to enter your API keys in the admin settings
• How trusted members are automatically exempted from CAPTCHA
• How Akismet integration catches spam that passes CAPTCHA
• How rate limiting protects against new-member spam floods

Choosing a CAPTCHA Provider

Go to Jetonomy → Settings → Anti-Spam to configure your CAPTCHA provider.

Jetonomy supports two providers:

Provider	Type	User friction
Google reCAPTCHA v3	Score-based, invisible	None - runs in background
Cloudflare Turnstile	Challenge-based, invisible	None - usually auto-passes

Both are invisible to real users. reCAPTCHA v3 assigns a bot-likelihood score and blocks low-scoring submissions. Cloudflare Turnstile analyzes browser signals and shows a challenge only when it cannot verify the user automatically.

Choose Cloudflare Turnstile if your community has members who are privacy-conscious or who block Google services. Both providers have free tiers sufficient for most communities.

Setting Up reCAPTCHA v3

1. Go to google.com/recaptcha and create a v3 site.
2. Add your domain to the allowed domains list.
3. Copy the Site Key and Secret Key.
4. In Jetonomy → Settings → Anti-Spam, select reCAPTCHA v3, paste both keys, and click Save.

Setting Up Cloudflare Turnstile

1. Log in to your Cloudflare dashboard and go to Turnstile.
2. Add a site and set the widget mode to Invisible.
3. Copy the Site Key and Secret Key.
4. In Jetonomy → Settings → Anti-Spam, select Cloudflare Turnstile, paste both keys, and click Save.

Note: After saving, Jetonomy automatically loads the CAPTCHA script on the post and reply forms. You do not need to add any code to your theme.

Trusted Members Skip CAPTCHA

Members at Trust Level 2 and above never see or trigger a CAPTCHA check. Jetonomy bypasses the verification entirely for them - the API call is never made.

This means your most active, trusted members post without any friction while new accounts get verified. As members earn reputation and cross the TL2 threshold, they transition out of CAPTCHA checks automatically.

Akismet Integration

If the Akismet plugin is active on your site, Jetonomy sends every new post and reply through Akismet's spam detection API as a second layer of protection. Content that passes CAPTCHA but that Akismet marks as spam is held in the moderation queue rather than published.

See the Moderation Queue guide for how to review Akismet-held content.

Akismet and CAPTCHA work independently. You can run both at the same time for maximum protection, or use either one alone.

AI-Powered Spam Detection (Pro)

Jetonomy Pro's AI extension adds a third layer: posts and replies publish instantly, then a background reviewer scores each one for spam probability on a schedule (the AI is never in the posting path). Posts above the configured threshold are moved to the moderation queue with a reason the model generated. Posts below it stay published as normal.

This catches the kinds of spam that pattern matching and Akismet miss - subtly rewritten affiliate spam, contextually wrong replies designed to pad posting history, and coordinated attacks that use clean accounts.

Run the detection through any supported provider - OpenAI, Anthropic, a custom endpoint, or self-hosted Ollama (which keeps all content on your own server). See AI Integration for setup.

AI spam detection stacks on top of CAPTCHA, Akismet, and rate limits - not instead of them. Each layer catches different threats.

Rate Limiting for New Members

Trust Level 0 members (brand-new accounts) are subject to posting rate limits regardless of CAPTCHA:

Content type	Default limit
Topics per day	3
Replies per day	10
Votes per day	5

Limits reset after 24 hours. Members at Trust Level 1 and above are exempt from all rate limits.

You can adjust the default thresholds at Jetonomy → Settings → Permissions. Setting a limit to 0 disables it for that trust level.

Tip: Rate limiting is your best defense against coordinated spam from many new accounts. Even if a bot farm passes CAPTCHA, each account can only post 3 topics before hitting the daily limit.

Rate Limit Settings

These rate limits live alongside the trust system. The per-day caps shown above are the Trust Level 0 defaults; every trust level above TL0 is exempt. See Trust Levels for how a member graduates out of rate limiting by earning their way to TL1, and where the "Rate limit lifted" capability fits in the wider trust ladder.

What's Next?

When spam prevention is not enough and you need to act on a specific member, the next guide covers banning.

Banning Members →

Approving, marking as spam, and trashing all act on a single piece of content. Banning acts on the person. When a member is not just posting one bad item but is repeatedly disruptive - or is a confirmed bad actor - you ban the account so they cannot keep posting. This guide covers the three ban types, how long a ban lasts, and where to manage bans.

What You Will Learn

• Where to ban and unban members
• The three ban types and when to use each
• How ban durations work, including automatic expiry
• How to lift a ban early
• Who is allowed to ban members

Where to Manage Bans

You ban and unban members from the Jetonomy → Users page in the WordPress admin. The page lists every community member with their trust level and stats, and gives each row a Ban / Unban control (plus a quick Silence link). Currently banned members also appear on the Banned Users tab of the Moderation Queue, where you can lift each ban.

Banning requires the jetonomy_moderate capability - the same capability that gates the moderation queue itself. WordPress administrators and Trust Level 4+ members have it by default.

The Ban Dialog

Clicking Ban on a member's row opens the Ban User dialog with three choices:

Ban Types

Jetonomy supports three levels of restriction so the response fits the situation:

Type	Effect
Global Ban	The member is blocked from posting anywhere in the community
Space Ban	The member is blocked from a single space but can still participate elsewhere
Silence	The member can still read everything but cannot post or reply anywhere

Tip: The Silence quick-link on each user row opens this same dialog pre-set to the Silence type with a 7-day duration - a fast way to cool down a heated member without a full ban.

Duration

Pick how long the ban lasts from the Duration selector:

Duration	Effect
Permanent	The ban stays in place until you lift it manually
1 Day	Lifts automatically 1 day after it is applied
7 Days	Lifts automatically 7 days after it is applied
30 Days	Lifts automatically 30 days after it is applied

Time-limited bans lift themselves automatically when they expire, so you do not have to remember to unban a member after a cooling-off period.

Reason

The dialog has an optional Reason field. The reason is stored with the ban for your own records - it does not change how the ban behaves. Recording why you banned someone makes it easy for you or another moderator to understand the history later.

Bans Apply to the API and the App Too

A ban is not just a front-end block. Jetonomy checks account status on every REST write - creating posts and replies, voting, registering a push device, and every other mutation - so a banned member is rejected no matter how they connect. That includes Application Password and mobile-app sessions, which authenticate outside the normal WordPress login flow. A banned account cannot post around the ban by switching to the app or calling the API directly; the write is refused with a "banned" error before anything is saved.

The same gate also stops members who have not confirmed their email (pending verification) from writing through the API until they finish signing up.

Lifting a Ban Early

To remove a ban before it expires, click Unban on the member's row (on the Users page or the Banned Users tab). The restriction is cleared and the member can participate again immediately.

When to Ban vs. Act on Content

Reach for a ban only when content-level actions are not enough:

• A single bad post - use Trash or Mark as Spam from the Moderation Queue.
• A member causing trouble in one space - use a Space Ban so they keep their access elsewhere.
• A member you want to cool down, not remove - use Silence (they can still read).
• A member who keeps coming back - use a Global Ban, permanent or timed, to stop the behavior at the source.

What's Next?

Learn how in-app notifications keep your members engaged and informed about replies, mentions, and votes.

Notifications →

Notifications keep your community members in the loop without requiring them to check back manually. Every relevant activity (replies, mentions, votes) surfaces instantly in the notification bell so members always know when something needs their attention.

What You Will Learn

• How the notification bell works and where it appears
• Every notification type and when each one fires
• How to mark notifications as read
• How to view, filter, and delete notifications on the full notifications page
• How the verification reminder email nudges members who never confirmed their address
• Where members set their personal notification preferences

The Notification Bell

The notification bell icon appears in the community navigation bar on every page. When you have unread notifications, a red badge shows the count. The count updates automatically. You do not need to refresh the page.

Click the bell to open a dropdown showing your most recent notifications. The dropdown lazy-loads its content when you click, keeping page load times fast.

Each notification in the dropdown shows:

• The notification type (icon)
• A summary of what happened (for example, "Sarah replied to your topic")
• The time it occurred
• A direct link to the relevant content

Clicking a notification in the dropdown marks it as read and navigates you to the relevant topic, reply, or profile.

Notification Types

Jetonomy fires a notification for each of the following events:

Jetonomy ships with ten notification types. The Channels column shows the default channels for each type; "In-app" means it appears in the bell, "email" means it also sends an email by default. Every type can be turned on or off per channel, both site-wide by an admin and per-member. See the Preferences section below.

Event	Who receives it	Channels (default)
Someone replies to your topic	Topic author	In-app, email
Someone replies to your reply (threaded)	Reply author	In-app
Someone mentions you with @username	Mentioned member	In-app, email
Your reply is accepted as an answer (Q&A)	Reply author	In-app, email
An idea's status changes (Ideas spaces)	Idea author	In-app, email
A new topic is posted in a space you follow	All followers of that space	In-app
You earn a badge (Jetonomy Pro)	The member	In-app
Your topic or reply receives a vote	Content author	In-app
A moderator reviews or acts on your content	Content author	In-app, email
A member requests to join a space you manage	Space managers	In-app, email

Note: The badge notification only fires on communities running Jetonomy Pro. Votes are reported through a single "vote on your post" notification (it covers both upvotes and downvotes).

These channels are the defaults that ship with Jetonomy. An administrator can change the site-wide default for any type under Jetonomy → Settings → Email, and each member can override their own preferences. The full default table lives in Email Notifications.

Marking Notifications as Read

Mark one as read: Click any notification in the dropdown. Navigating to it marks it read automatically.

Mark all as read: Click the Mark all as read link at the top of the dropdown. All notifications are cleared in a single action. The badge disappears immediately.

Unread notifications are highlighted with a subtle background tint in the dropdown so you can spot them at a glance.

The Full Notifications Page

The dropdown shows your most recent notifications, roughly the last 10 to 20 items depending on screen size. To see your full notification history, click See all notifications at the bottom of the dropdown or navigate directly to /community/notifications/.

The full page lists every notification you have received, loading 20 at a time with a Load More button at the bottom. A weekly background job marks unread notifications older than 30 days as read. Notifications are not auto-deleted from the database.

Filter Tabs

The page has a row of filter tabs across the top so members can focus on one kind of update at a time. Each tab shows a count badge of how many notifications match it, so you can see at a glance where the activity is.

Tab	What it shows
All	Every notification you have received
Unread	Only notifications you have not opened yet
Mentions	Notifications where someone @-mentioned you
Replies	Replies to your posts and to your replies
Votes	Upvotes and downvotes on your posts and replies
Badges	Badges you have earned (only shown when Jetonomy Pro is active)

Switching tabs reloads the list filtered to that type and keeps your place. The Badges tab appears only on communities running Jetonomy Pro, since badges are a Pro feature.

Deleting Notifications

Members can clear out notifications they no longer need, not just mark them read.

• Delete one: Open the ... actions menu on any notification row and choose Delete. The row is removed immediately.
• Bulk delete: Tick the checkbox on one or more rows. A toolbar appears at the top of the list showing how many you have selected, with Mark read and Delete buttons that apply to every selected row at once. A Select all on page checkbox selects the whole visible page in one tick.

Deleting is permanent for that member's own inbox. It does not affect anyone else's notifications or the underlying post or reply.

Note: Per-notification delete and the bulk-delete toolbar were added in 1.4.3.

The Verification Reminder Email

When a community requires email verification at signup (Jetonomy → Settings → Email), some members register but never click the verification link in their welcome email. Jetonomy sends those members a single follow-up reminder email nudging them to finish verifying, so they do not get stuck unable to participate.

• The reminder is sent once per member. It will never email the same person twice.
• It goes out a configurable number of hours after registration. Set the delay in jetonomy_settings.verification_reminder_hours. Setting it to 0 disables the reminder entirely.
• It respects each member's email opt-out, so anyone who has opted out of community email is skipped.
• It uses the same branded email template as your other Jetonomy emails, so the subject and body can be customised under Settings → Email → Email Templates.
• The reminder only runs while email verification is switched on. Turn verification off and there is nothing to remind about.

Per-User Notification Preferences

Each member can control which notification types they receive. Go to Profile → Edit Profile → Notifications (at /community/u/your-username/edit/).

Options are:

• In-app notifications on/off per type
• Email notifications on/off per type (see Email Notifications for the full email guide)
• A single Pause all email notifications toggle at the bottom of the same Notifications tab. Turning it on snoozes every email type at once while still showing web notifications in the community, so a member can step away from email without losing their per-type settings. Turning it back off restores their previous choices.

Members cannot disable notifications for direct mentions. The @mention notification is always delivered to ensure important communications reach their target.

Note: Administrators can set the default notification preferences that new members start with. Go to Jetonomy → Settings → Email to configure the defaults applied at signup.

What's Next?

Learn how to configure email notification delivery, set community-wide defaults, and understand which notification types support email.

Email Notifications →

Related Pro Features

Pro adds more ways to reach and message members:

• Private Messaging - one-to-one and group direct messages.
• Email Digest - scheduled activity summary emails.
• Web Push - browser push notifications.
• Reply by Email - reply to threads straight from your inbox.

Email notifications bring members back to your community even when they are not actively browsing. Jetonomy sends a notification email for every in-app event type, and both you and your members have control over which emails are delivered.

What You Will Learn

• Which notification types send email
• How to configure default email settings for new members
• How members control their own email preferences
• How one-click unsubscribe links work
• How Jetonomy sends email and how to use your own SMTP provider
• What email digest options are available in Jetonomy Pro

Which Notification Types Send Email

Every notification type that appears in the in-app bell can also send an email. The email mirrors the in-app notification - it names the event, shows a short excerpt of the content, and includes a direct link back to the relevant topic or reply.

Jetonomy ships with ten notification types. Each one sends email by default, or not, as shown below:

Notification type	Email sent by default
Reply to your topic	Yes
Reply to your reply	No
@mention	Yes
Answer accepted (Q&A)	Yes
Idea roadmap status changed	Yes
New post in followed space	No
Badge earned (Jetonomy Pro)	No
Vote on your post	No
Moderator action on your content	Yes
Space join request	Yes

The defaults above are what Jetonomy applies when a new member signs up. Administrators set these site-wide defaults in Jetonomy → Settings → Email; the full settings reference, including the matching web (in-app) defaults, lives in Email Settings. Each member can then override any type for themselves (see "How Members Control Their Preferences" below).

Tip: "New post in followed space", vote, and badge emails are off by default because they can occur frequently. A member who follows many active spaces would otherwise receive a high volume of email. Let members opt in rather than having to opt out.

Editable Email Templates (updated in 1.4.1)

Every notification email Jetonomy sends has an editable template - subject and body - at Jetonomy → Settings → Email → Templates. Change the wording to match your community's voice without writing any code.

Two improvements landed in 1.4.1 that are worth knowing about:

• Reset to default button on every template - one click restores the shipped subject and body. No more retyping if you change your mind or want to start over.
• Verification reminder template is now editable from the same screen. The reminder fires once per member, a configurable number of hours after sign-up (default 24), if they haven't clicked the verification link in their welcome email. Set the delay in jetonomy_settings.verification_reminder_hours, or set it to 0 to disable the reminder entirely. See the verification reminder section for the full behaviour.

Defaults now have a single source of truth so reset always restores the exact copy the plugin ships with - even if a future update changes the default wording, your reset still gets the version you'd see on a fresh install.

Template Placeholders

You can use these placeholders in any subject or body. They are replaced with the real values when the email is sent:

Placeholder	Replaced with
{site}	Your site name
{user}	The recipient's display name
{message}	The notification summary text
{type}	The notification type key
{url}	A direct link to the relevant content
{post_title}	The title of the related topic or idea
{actor_display_name}	The member who triggered the notification
{reply_excerpt}	A short excerpt of the reply
{space_title}	The space the activity happened in

Any placeholder with no value for a given event renders as an empty string, so it never shows up as literal {post_title} text in the email.

Configuring Default Settings

The community-wide defaults - which types email by default, the From name, the From address, email branding, and the editable templates - all live on the admin Jetonomy → Settings → Email screen. That screen is documented in full, with every setting key, default, and location, in Email Settings.

Changes to defaults apply only to new members who sign up after the change. Existing members keep their current preferences.

How Members Control Their Preferences

Each member can override the defaults from their profile settings at /community/u/their-username/edit/ under the Notifications tab. Every notification type has a separate toggle for in-app and email delivery.

Members can disable all notification emails at once with the Pause all email toggle. This is the equivalent of a temporary snooze - all preferences are preserved so they can turn email back on later.

One-Click Unsubscribe

Every notification email sent by Jetonomy includes an unsubscribe link in the footer. Clicking it immediately unsubscribes the member from that one notification type and shows a confirmation message.

No login is required to unsubscribe - the link contains a signed token that authenticates the action. This keeps unsubscribe rates low and means members who receive an email do not need to remember their password to opt out.

How Jetonomy Sends Email

Jetonomy uses WordPress's wp_mail() function to send all notification emails. This means it automatically works with any SMTP plugin you have installed - WP Mail SMTP, FluentSMTP, Postmark, Mailgun, or any other wp_mail compatible provider.

No additional configuration is needed in Jetonomy when you add an SMTP plugin - it just works.

Note: If you send high volumes of notification email, use a dedicated transactional email provider (Postmark, Mailgun, Sendgrid) rather than your hosting server's mail. Dedicated providers give you delivery tracking, bounce handling, and higher sending limits.

Email Digest (Jetonomy Pro)

PRO - This feature requires Jetonomy Pro.

The Email Digest feature bundles all notifications from a configurable time window into a single summary email. Members can choose daily or weekly digests instead of receiving individual emails for each event. This dramatically reduces email volume for active community members while keeping them informed.

What's Next?

Learn how member profiles work, what stats are displayed, and how members can edit their own information.

User Profiles →

Every member in your community has a public profile page that shows who they are, how much they contribute, and what they have been up to. Profiles build trust between members and give contributors the recognition they have earned.

What You Will Learn

• What a member profile page shows
• How online status works on profiles
• Which tabs are available and who can see each one
• How members edit their own profile
• How members delete their own account from the app or API
• Where reputation and trust level appear

The Profile Page

Every member has a profile page at /community/u/their-username/. Anyone can visit this page - no login is required unless your community is set to private.

Header Section

The profile header shows:

• Avatar - pulled from WordPress Gravatar by default. Members can upload a custom photo from the Edit Profile page and crop it square before it is saved.
• Display name - the name shown across all community activity
• Username - the login handle used in @mentions and the profile URL
• Bio - a short text description the member writes themselves
• Join date - when the member's account was created
• Online status - a green dot appears if the member was active in the last 5 minutes (see Online Status)

Stats Bar

Below the header, four stats appear at a glance:

Stat	What it shows
Reputation	Total reputation score earned
Posts	Number of published topics
Replies	Number of published replies
Trust Level	Current trust level badge and name

The trust level badge uses the same color coding as it does on reply cards - grey for TL0, scaling up to gold for TL5.

Profile Tabs

Posts

Lists every topic the member has published, paginated 20 per page, sorted newest first. Each item shows the topic title, the space it belongs to, the vote score, and the reply count.

Replies

Lists every reply the member has posted across all spaces, paginated 20 per page, newest first. Each item shows the reply excerpt, the topic it belongs to, and the vote score.

Votes

Shows the content this member has voted on. The tab is visible to the member themselves and to WordPress Administrators. Other members cannot see this tab - voting is semi-private.

Bookmarks

Lists the topics this member has bookmarked, at /community/u/their-username/bookmarks/. Like Drafts, this tab appears only on the member's own profile. Bookmarks are private to the member who saved them, so no one else (including administrators viewing the public profile) sees this tab. It gives members a quick personal reading list of posts they wanted to come back to. See Bookmarks & Following for how members save and manage bookmarks.

Drafts

Shows unpublished draft topics saved by this member. This tab is visible only to the profile owner and WordPress Administrators. Drafts are never exposed publicly.

Tip: Encourage active members to complete their bio. Profiles with a bio and a recognizable avatar get more replies - other members feel more comfortable engaging when they know who they are talking to.

Editing a Profile

Members can edit their own profile at /community/u/their-username/edit/. This page is accessible from the Edit Profile button on the profile page header.

Editable fields:

• Display name
• Bio
• Avatar - upload a JPG, PNG, GIF, or WebP. After choosing a non-GIF image, a crop dialog opens: drag to reposition, use the slider to zoom, then Crop and upload saves a square avatar (animated GIFs upload as-is to preserve animation). The "Remove photo" button reverts to the Gravatar.
• Notification preferences (email and in-app toggles per type)

WordPress Administrators can edit any member's profile from the standard WordPress Users admin as well.

Deleting Your Account (1.8.0+)

Members can permanently delete their own account from the mobile app or the REST API (DELETE /users/me). There is no web front-end button for this yet - it is available through the app and the API only.

Account deletion is permanent and cannot be undone from the community front end - make sure your app or client confirms with the member before sending the request.

Embedding Profiles on a Page

You do not have to send members to the full profile page to surface profile information. Two shortcodes let you drop a compact member card or a space member roster onto any WordPress page, post, or widget area. Both are shortcode-only - there is no matching Gutenberg block, so add them with a Shortcode block or directly in the editor.

Member profile card

[jetonomy_user_profile user_id="0"]

Renders a small card with the member's display name, trust level badge, a short bio excerpt, and their reputation and post count. Set user_id to a specific member's ID, or leave it as 0 (the default) to show the currently logged-in member's card - handy for a "your profile at a glance" panel on a members-only page.

Space member roster

[jetonomy_space_members space_id="5" count="20"]

Lists the members of one space, ranked by reputation. Drop it on a space landing page or an "About this community" page so visitors can see who is active.

Attribute	Default	What it does
space_id	0	The ID of the space whose members to list. Required - leave it unset and nothing renders.
count	10	How many members to show, highest reputation first.

Note: The roster attribute is count, not limit.

What's Next?

See how your top contributors rank against each other on the community leaderboard.

Leaderboard →

Related Pro Features

• Custom Badges - award badges automatically or by hand to recognize members.

The leaderboard turns quality participation into something visible and worth competing for. Your top contributors are recognized publicly, which encourages every member to engage more thoughtfully.

What You Will Learn

• How to find the leaderboard page
• What information is displayed for each member
• How the top 3 medal positions work
• How to add the leaderboard sidebar widget
• Why public recognition improves community quality

The Leaderboard Page

The community leaderboard is available at /community/leaderboard/. Any member - and guests, if your community is public - can view it. No login is required.

Members are ranked by total reputation score, highest first. The leaderboard updates in real time as reputation changes - there is no daily cache delay between earning reputation and appearing in the rankings.

How Reputation Is Earned

Reputation is what drives a member's position on the board. Members earn it through quality participation - upvotes on their topics and replies, and having an answer accepted on a question. Downvotes and moderator removals subtract from it. The exact point values are defaults you can adjust under Jetonomy → Settings, so you can tune what your community rewards. See Voting & Reputation for the full list of actions and their default point values.

Time Period Filter

The leaderboard page has a row of period pills at the top that scope which members appear:

Pill	What it shows
All time	Every member, ranked by reputation (the default)
This month	Only members active within the last 30 days, ranked by reputation
This week	Only members active within the last 7 days, ranked by reputation

The month and week filters narrow the board to recently active members - ranking is still by total reputation score within each window, not by reputation earned during that period.

What Each Row Shows

Every row on the leaderboard displays:

Column	Description
Rank	Position number (1, 2, 3...)
Avatar	Member's initials avatar - their first two initials, not the uploaded photo, so the board stays fast (no online status dot on the leaderboard)
Name	Display name, linked to their profile page
Reputation	Total reputation score
Posts	Total published topic count

Clicking a member's name goes directly to their profile page.

Top 3 Medal Positions

The first three positions on the leaderboard display a medal icon next to the rank number:

Position	Medal
1st place	Gold medal
2nd place	Silver medal
3rd place	Bronze medal

Medal icons draw the eye immediately when someone opens the leaderboard page. Being in the top 3 is a genuine achievement that members notice and compete for.

The Leaderboard Sidebar Widget

Add the Jetonomy: Leaderboard widget to any sidebar from Appearance → Widgets. The widget shows the top 5 members by reputation, listing each member's name and reputation score - a compact preview of the leaderboard without requiring members to visit the full page. (Its default heading text is "Top Members".)

Configuration options:

Option	Default	Description
Title	Top Members	Widget heading text
Count	5	Number of members to show (max 20)

The widget runs a single direct LIMIT query to fetch the top members by reputation.

Why the Leaderboard Improves Community Quality

Recognition is a powerful motivator. When members see their name on the leaderboard, they are more likely to write detailed answers, respond helpfully to new members, and keep coming back. Members who are close to moving up a rank are especially motivated - the leaderboard creates natural competition without requiring badges, gamification plugins, or manual awards.

Tip: Reference the leaderboard in your community welcome message or newsletter. "See who our top contributors are this month" gives members a reason to engage and something to aspire to.

What's Next?

Learn how the online status green dot works - when it shows, where it appears, and how Jetonomy tracks it efficiently.

Online Status →

The online status green dot shows which members are currently active in your community. It makes conversations feel more live and helps members know when is a good time to expect a quick reply.

What You Will Learn

• When the green dot appears on a member's avatar
• Where online status is displayed across the community
• Where it is intentionally not shown and why
• How Jetonomy tracks activity without overloading the database
• That no setup is needed - it works automatically

When the Green Dot Appears

A green dot appears on a member's avatar when they have been active in the community within the last 5 minutes. Active means any authenticated page load or interaction - visiting a topic, posting a reply, casting a vote, or navigating between pages.

After 5 minutes of inactivity, the dot disappears automatically on the next page load that renders it.

There is no manual "appear offline" or "appear online" toggle. Online status reflects real activity.

Where Online Status Appears

The green dot is shown in these locations:

Location	Shown
Reply cards (author avatar)	Yes
Member profile page (header avatar)	Yes
Sidebar Leaderboard widget	No (the widget lists names and scores only, no avatars)
Topic listing rows (author credit)	No
Search results (author credit)	No

Why Not on Topic Listing Rows

Topic listing pages can show dozens of topics, each by a different author. Rendering the online status for every author on that page would require checking multiple records in a single request - potentially 20 to 50 lookups per page view on an active community.

Jetonomy deliberately omits the online dot from listing rows to keep those pages fast. The detail-level contexts (reply cards, profiles, widgets) are the right place for presence information because you are already focused on a specific member.

How Activity Tracking Works

When a logged-in member loads any community page, Jetonomy records a timestamp on their user record. To prevent a database write on every single page view, updates are rate-limited: Jetonomy writes the timestamp at most once per minute per member.

If a member loads 10 pages in 30 seconds, Jetonomy writes to the database once. This keeps the wp_jt_user_profiles table write volume proportional to the number of unique active members, not the total number of page views.

The online status check itself (reading whether a member is active) is cached for 60 seconds using the WordPress object cache. On a page with 10 reply cards by different authors, Jetonomy makes at most a small batch of cache reads rather than 10 individual queries.

No Setup Required

Online status is automatic. There is no setting to enable, no API key to configure, and no JavaScript polling. It works the moment Jetonomy is activated.

Note: Online status is only tracked for logged-in members. Guests who browse your community are not tracked and do not show an online indicator.

What's Next?

Go back to other sections, or return to the main community setup guide.

User Profiles → | Leaderboard →

Since Jetonomy 1.4.0, every signed-in member has a personal page at /community/my-spaces/ that lists every space they run and every space they're a member of, in one place. It is the fastest way to jump back into a space you are active in without scrolling the home page.

What You Will Learn

• Where the My Spaces page lives and how to reach it
• The two sections shown on the page and what they mean
• What each row tells you at a glance
• Quick actions available per row
• What members see when they're brand new and have not joined any space yet
• The privacy semantics: who can see this page

Where The Page Lives

The page is always at /community/my-spaces/. It is signed-in only. Visiting the URL while signed out redirects to the login page and returns to My Spaces after a successful sign-in.

There are two built-in ways to reach the page:

• The My Spaces link in the header avatar menu (added automatically in Jetonomy 1.4.0+)
• The mobile drawer menu under "Community"

If your theme overrides the header template, the link may not appear automatically. The page itself still works at the URL.

The Two Sections

The page is split into two sections, stacked top to bottom.

Spaces You Run

The first section lists every space where you are a space admin or space moderator. These are the spaces you have authority over.

For each space, the row shows:

• The space icon and title
• A role badge ("Admin" or "Mod")
• The post count and member count
• Quick action buttons: Edit (admins only), Mod queue, Members

The whole card is a link to the space home, so there is no separate "Visit" button.

If you run no spaces, this section simply does not appear (empty sections are hidden). If you also belong to no spaces, the page shows a single combined empty state - see Empty State below.

Spaces You're In

The second section lists every space where you are a regular member. These are the spaces you have joined but do not moderate.

For each space, the row shows:

• The space icon and title
• An optional short description
• The post count and member count

The whole card is a link to the space home; member rows have no per-row action buttons.

If you have not joined any spaces yet, this section simply does not appear (empty sections are hidden).

What Each Row Tells You

Element	What it means
Icon	The Lucide icon picked by the space owner
Title	The space name; the whole card links to the space home
Role badge	"Admin" or "Mod" on the spaces you run; no badge for regular members
Description	An optional short description excerpt, when the space has one
Post count	Total published topics in the space
Member count	Total members in the space

Quick Actions

Action buttons appear only on rows in the "Spaces you run" section. Member rows have no action buttons - clicking the card opens the space.

• Edit appears only for spaces you administer. It opens the front-end Edit Space page covered in the previous article.
• Mod queue opens the space's moderation queue.
• Members opens the members tab where you can promote, demote, or remove members.

Empty State

Brand-new members often land on My Spaces before they have joined anything. When you neither run nor belong to any space, the page shows a single full-page empty state - "You are not in any spaces yet" with a Browse spaces button that goes to the community home.

Otherwise, empty sections are simply hidden: if you run spaces but belong to none as a regular member (or vice versa), only the section with content renders. There is no per-section "collapsed" placeholder and no "Create a space" button on this page.

Privacy

The My Spaces page is personal to the signed-in user.

• It requires sign-in. Signed-out visitors are bounced to login.
• It is excluded from search engine indexing via the noindex, nofollow meta tag.
• It is not visible to anyone else. There is no public URL that shows another user's space list.
• Membership in a Hidden space is shown on this page but is still not visible on the user's public profile.

If you want to see which spaces another user is in, you have to look at their public profile, which only shows public memberships.

Performance

The page loads all of your spaces with one indexed query per role bucket (the spaces you run, and the spaces you belong to). Space rows are hydrated once each, so there is no per-row N+1 query, and the per-card role label ("Admin" / "Mod") is served from a warmed cache.

Note: The page does not paginate. It loads every space you run and every space you belong to. For the typical member this is a handful of spaces; if you expect members to belong to hundreds of spaces, pagination here is a known gap rather than a shipped feature.

What's Next?

The My Spaces page is one entry into your community life. The full profile page covers the rest of what a member does: their posts, replies, votes, bookmarks, and drafts, alongside their reputation score and trust level. (#05-custom-badges-jtnmy) Pro extension.)

Your Profile Page →

Mobile App Overview

Jetonomy communities have a native iOS and Android app. Your members get a real mobile app for your forum - feed, topics, replies, votes, spaces, notifications, and (with Jetonomy Pro) messaging, reactions, polls, and badges - and it automatically shows your logo, color, and community name.

Requires Jetonomy 1.6.0 or newer for the per-site branding endpoint (/app/config). Older sites still work with default styling.

What you will learn

• What the mobile app is and how it connects to your site
• The two ways to ship it: the open-source app or your own branded app
• Where to set your branding and how members sign in

How it works

The app connects directly to your WordPress site over the Jetonomy REST API (jetonomy/v1). There is no middleman server and no separate account system - members sign in with your site, and your data stays on your site.

Member's phone  ->  Jetonomy App  ->  Your WordPress site (jetonomy/v1 REST API)

When the app opens your community it reads your branding from GET /wp-json/jetonomy/v1/app/config (logo, accent color, community name) and themes itself to match.

Two ways to ship it

Option	Best for	What members see
Open-source Jetonomy app	Trying it out, smaller communities, members who belong to several communities	A generic app they point at your site; it themes itself with your branding
Your own branded app	Established communities that want their own store presence	Your icon and name in the App Store / Play Store, published under your own developer accounts

Both use the same codebase. You set the in-app branding (logo, color, name) the same way in either case - see Brand Your App.

What members can do

• Browse the feed across spaces (Hot / New / Top), post topics and questions, reply, and vote
• Join forums, Q&A, and idea spaces; get notifications; search
• With Jetonomy Pro: private messaging, reactions, polls, custom badges, custom fields, and native push
• Belong to several communities and switch between them in one app
• Read offline - the last-seen content is available without a connection

Next steps

• Brand Your App - set your logo, color, and community name
• Connect Members - how admins and members sign in
• Get the App - use the open-source app or publish your own

The app is open source (GPL): github.com/vapvarun/jetonomy-app. Full step-by-step guides live in its wiki.

Brand Your App

The mobile app reads your branding straight from your WordPress settings, so you change it in wp-admin and the app updates itself - no rebuild needed. You control three things: your community name, your accent color, and your logo.

Requires Jetonomy 1.6.0 or newer. On older versions the app falls back to its default styling.

What You Will Learn

• Where to set the community name, accent color, and logo
• How the app reads them and what each one affects
• The difference between in-app branding and the phone home-screen icon

Set your community name

1. Go to Jetonomy -> Settings -> General
2. In Community Title, enter your community's name (for example, Course Academy)
3. Click Save Changes

This becomes the community name shown in the app, including on the sign-in screen.

Set your accent color

1. Go to Jetonomy -> Settings -> Appearance
2. Under Color Palette, open Accent and pick your brand color
3. Click Save Changes

The accent color themes the whole app - buttons, the active feed tab, links, and the compose button.

Add your logo

1. Still on Jetonomy -> Settings -> Appearance, find the Logo field
2. Paste the URL of your logo image
   • Tip: upload your logo under Media -> Add New, open it, and copy the File URL.
   • Best results: a transparent PNG at least 512px on its longest side
3. Click Save Changes

The logo appears on the app's sign-in screen.

How the app reads it

The app fetches these values from the public endpoint:

GET /wp-json/jetonomy/v1/app/config

which returns your app_name (Community Title), accent_color, and logo_url. The app re-reads it whenever it connects, so updates appear without shipping a new build.

In-app branding vs the home-screen icon

• In-app branding (logo, color, name) is what these settings control. It themes the inside of the app and works on the open-source app for every community.
• The phone home-screen icon and app name are baked into the app binary. They only change when you publish your own branded app - see Get the App.

Next steps

• Connect Members - how members sign in
• Get the App - use the open-source app or publish your own

Connect Members

There is no separate "connect your site" step. Everyone - you and your members - signs in to the app the same way, and WordPress decides who can do what. This page explains the sign-in flow and how roles work.

What You Will Learn

• How the site address is provided (typed vs baked in)
• How members create a secure Application Password
• How admin and member roles are handled automatically

The site address

• Open-source app: each person types your community's web address (for example, https://yourcommunity.com) once.
• Your own branded app: the address is baked in, so members never type it - they just open your app and sign in.

How everyone signs in - Application Passwords

The app authenticates with WordPress Application Passwords, a secure feature built into WordPress core. It is not the member's normal password, and it can be revoked at any time without changing their real password.

Each person creates their own:

1. Log in to your site's wp-admin
2. Go to Users -> Profile and scroll to Application Passwords
3. Enter a name like My Phone and click Add New Application Password
4. WordPress shows a code like abcd efgh ijkl mnop - copy it
5. In the app, enter the site address (if asked), the username, and paste that code

Application Passwords require your site to be served over HTTPS in production. Some security plugins disable them - if sign-in fails, confirm Application Passwords are enabled.

Admins vs members - automatic

The app reads each person's role from WordPress, so there is nothing extra to set up:

• Admins and moderators also get a Manage area in the app (moderation queue, flags, announcements, analytics).
• Members see the community (feed, topics, spaces, messages).

Being an admin in WordPress is the connection - no extra "register the app" action is needed.

Revoking access

Anyone can revoke a device from the same Users -> Profile -> Application Passwords screen, or sign out / remove the community inside the app. Revoking does not affect their account or their real password.

Next steps

• Get the App - use the open-source app or publish your own
• Brand Your App - set your logo, color, and name

Get the App

There are two ways to put the Jetonomy app in your members' hands: use the open-source app as-is, or publish your own branded app. Both use the same code and read your branding from WordPress.

What You Will Learn

• How to try the app on a phone without publishing
• What it takes to publish your own branded app
• The accounts and tools involved (and the no-EAS alternatives)

Try it first (no publishing)

The open-source app runs in Expo Go so you can see it before committing:

1. Install Expo Go (free) on a phone from the App Store / Play Store
2. On a computer with Node.js, run:

   git clone https://github.com/vapvarun/jetonomy-app.git
   cd jetonomy-app
   npm install
   npx expo start
   

3. Scan the QR code with Expo Go (Android) or the Camera app (iPhone)
4. Sign in with your site address + an Application Password

Publish your own branded app

This puts your app - your icon and name - in the App Store and Google Play under your own developer accounts.

You provide (one time):

• A free Expo account
• An Apple Developer account ($99/year) for the App Store
• A Google Play account ($25 one time) for the Play Store

Then build and submit (full walkthrough in the app repo):

npm i -g eas-cli
eas login
eas init
eas build --profile production --platform all
eas submit

Not technical? You only need to create the three accounts. A developer - or the Wbcom team as a one-time setup - can do the rest and hand you the live app.

Prefer not to use Expo's cloud (EAS)?

The app is built with Expo, but EAS (Expo's paid cloud build service) is optional. You can build for free with eas build --local on your own Mac, or run npx expo prebuild and build the native projects in Xcode and Android Studio, or use Fastlane / Codemagic / GitHub Actions. A Mac with Xcode is required for iOS, and the Apple and Google accounts are required to publish (Apple's rules, not Expo's).

Full guides

The app is open source (GPL): github.com/vapvarun/jetonomy-app. Detailed, non-technical step-by-step guides - branding, signing in, trying the app, building, and troubleshooting - live in the wiki.

Next steps

• Brand Your App - set your logo, color, and name
• Connect Members - how members sign in

Native Push Setup

Native push sends notifications to a member's phone even when the Jetonomy app is closed - a new reply, a mention, or a direct message shows up on the lock screen. It is delivered by the Web Push extension in Jetonomy Pro, which handles both browser push and native (Expo) push from the same settings.

Requires Jetonomy Pro with the Web Push extension enabled, plus Jetonomy 1.6.0 or newer for the mobile app. Native push also requires your site to be served over HTTPS.

What You Will Learn

• What native push needs before it can work
• Where to turn it on and set the notification title and icon
• How members' devices get registered (nothing manual for you)

Before you start

Native push relies on three things being in place:

1. Jetonomy Pro is installed and licensed.
2. The Web Push extension is enabled under Jetonomy -> Extensions.
3. Your site uses HTTPS. Push services reject insecure origins.

When the Web Push extension is active, the app's config endpoint (GET /wp-json/jetonomy/v1/app/config) reports features.native_push: true, and the app starts registering devices for push.

Turn on push and set the message

1. Go to Jetonomy -> Settings and open the Web Push tab
2. Tick Enable Web Push
3. VAPID Public Key - this is generated automatically the first time the extension runs and shown here read-only. You do not need to create or paste a key. (If it reports it could not be generated, your server needs OpenSSL with EC support.)
4. Default Notification Title - the title shown on push notifications. Defaults to your site name; change it to your community's name if you prefer.
5. Notification Icon URL - the small icon shown with the notification. Recommended: a 192x192 PNG. Leave it blank to fall back to the site favicon.
6. Click Save Web Push Settings

These same settings drive both browser push and native app push - there is no separate native-push screen to configure.

How members' devices get registered

You do not register devices by hand. When a member signs in on the Jetonomy app, the app sends its device push token to your site automatically:

POST /wp-json/jetonomy/v1/push/register-device

with the device's Expo push token and platform (ios or android). When a member signs out or uninstalls, the token is removed with a matching DELETE. From then on, notifications the member would see in-app are also delivered to their device.

In-app notifications vs native push

• In-app notifications always work - the bell and the notifications screen inside the app.
• Native push is the extra step that reaches the member when the app is closed. It only fires once the Web Push extension is enabled and saved, over HTTPS.

Next steps

• Brand Your App - set your logo, color, and name
• Connect Members - how members sign in
• Get the App - use the open-source app or publish your own

Activate your license, switch on the extensions you need, and understand which capabilities gate each Pro feature.

PRO - This section covers Jetonomy Pro.

What You Will Learn

• How to activate your Jetonomy Pro license
• How to enable and disable individual Pro extensions
• Which license tier unlocks which extensions
• Which WordPress capabilities gate each Pro feature

Activate Your License

Jetonomy Pro is a peer plugin to free Jetonomy. Install and activate free Jetonomy first, then install Jetonomy Pro - Pro shows an admin notice and stays dormant if the free plugin is not active.

1. Go to Jetonomy → Settings → License in your WordPress admin (License is a tab inside the free plugin's Settings page, not a standalone page).
2. Paste the license key from your purchase receipt.
3. Click Activate. Jetonomy validates the key against the store and shows your tier and expiry.

Your license drives automatic updates and tier checks. If a license is missing or expired, extensions still boot - but features that require a higher tier than your license carries are blocked at the gate.

Note: Free and Pro always ship the same x.y.z version. Keep both updated together so the contracts between them stay in sync.

Enable Extensions

Jetonomy Pro ships seventeen extensions. None of them do anything until you switch them on.

1. Go to Jetonomy → Extensions (the jetonomy-extensions page).
2. Each extension shows a card with its name, description, and a toggle.
3. Click Enable on the extensions you want. The toggle persists the choice to the jetonomy_pro_extensions option (an array of extension IDs).
4. Enabling an extension runs any one-time setup it needs (for example, creating its database tables) and registers its hooks, REST routes, and admin screens immediately.

Disable an extension at any time from the same page. Disabling stops the feature and unregisters its hooks; it does not delete the data the extension already stored.

License Tiers

Tier	Who it suits
Starter	A single community getting started with Pro features
Growth	A growing community that needs the full extension set across more sites
Agency	Builders running Pro across many client sites
Lifetime	One-time purchase with ongoing updates

All seventeen extensions are available on the paid tiers. Higher tiers raise the activation limits (number of sites) and support level rather than locking individual features behind a paywall. The exact site limits per tier are listed on your account page and on the pricing page.

Capabilities

Pro registers five capabilities that gate its features. Each maps to the WordPress roles shown below by default; you can reassign them with any role-editor plugin if your community uses custom roles.

Capability	Default roles	What it gates
jetonomy_manage_settings	Administrator	Access to the Pro settings pages (License, Extensions, integration and extension settings tabs)
jetonomy_manage_spaces	Administrator	Per-space Pro admin controls - SEO Pro metadata, custom-field tabs, and creating site-wide announcements
jetonomy_moderate	Editor, Administrator	The actions Advanced Moderation rules can take on matched content
jetonomy_vote	Subscriber, Contributor, Author, Editor, Administrator	Casting Reactions and voting in Polls
jetonomy_view_analytics	Administrator	Viewing the community Analytics dashboard

Note: Most Pro REST write routes are additionally gated by manage_options for admin operations, and by trust level for member operations (for example, Private Messaging and Poll creation require Trust Level 1 or higher). See the per-feature pages and the REST API reference for the exact permission on each route.

Data and Uninstall

Disabling an extension and deleting the plugin are two very different actions.

• Disabling an extension (from Jetonomy → Extensions) only unregisters that extension's hooks and stops its background work. Everything it already stored - its tables, options, and member content - stays in place, so re-enabling it later picks up exactly where you left off. Deactivating the whole Jetonomy Pro plugin leaves all Pro data untouched the same way.
• Deleting the plugin from the WordPress Plugins screen runs the uninstall routine. It removes Jetonomy Pro's database tables, Pro plugin options, Pro user meta (every jetonomy_pro_ key), and Pro scheduled tasks. Jetonomy Pro does not register its own WordPress capabilities - those belong to the free plugin and are cleaned up by its uninstall.

Only uninstalling removes stored data - and it is irreversible - so back up your database first if there is any chance you will want the data again.

What's Next?

Start with the engagement extensions members notice first.

Emoji Reactions →

Add expressive emoji reactions to every post and reply - so members can respond instantly without writing a full reply.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to enable Reactions for your community
• How to customize which emojis appear per space
• How members react to and change their reaction on a post
• How to read reaction counts from the REST API

Why Reactions Matter

A quick reaction lowers the bar for engagement. Members who would never write a reply will tap a rocket emoji or a heart. That micro-engagement adds up - you get richer signal on your best content and members feel heard without the pressure of composing a response.

How It Works

Every post and every reply in your community shows a reaction strip. Members click any emoji to react. Clicking a different emoji replaces the previous one - each member can hold exactly one reaction per piece of content at a time. Clicking the same emoji again removes the reaction entirely.

The reaction counts are displayed as chips directly below the post body. Each chip shows the emoji and the total count. Hovering a chip reveals the names of recent reactors.

Enabling Reactions

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Reactions and click Enable.
3. Reactions appear on all posts and replies immediately - no page-level configuration needed.

Tip: Enabling Reactions does not affect any existing posts. Historical content simply starts with zero reactions.

Default Emoji Set

Jetonomy ships with eight emoji reactions out of the box:

Emoji	Label	Use case
Like	Thumbs up	General agreement
Love	Heart	Enthusiasm, appreciation
Haha	Laughing face	Humor, something funny
Celebrate	Party popper	Wins, announcements
Thinking	Thinking face	Interesting, thought-provoking
Watching	Eyes	Following along, keeping an eye on it
Rocket	Rocket	Fast, shipped, love it
Dislike	Thumbs down	Disagreement

All eight are enabled globally by default. You can adjust which ones appear per space.

Per-Space Customization

Different spaces have different tones. A Support space might not need a Celebrate emoji, and a General Chat space might not need Dislike.

1. Go to Jetonomy → Spaces and open the space you want to customize.
2. Open the Reactions tab in the space settings panel.
3. Toggle individual emojis on or off for this space.
4. Save. The change takes effect immediately for all posts in that space.

REST API

The Reactions extension registers these endpoints under jetonomy/v1:

Method	Endpoint	Description
GET	/posts/{id}/reactions	Get the reactions and counts for a post
POST	/posts/{id}/reactions	Toggle your reaction on a post (add, replace, or remove)
GET	/replies/{id}/reactions	Get the reactions and counts for a reply
POST	/replies/{id}/reactions	Toggle your reaction on a reply

{id} is the numeric ID of the post or reply. A single POST toggles your reaction: sending a new emoji replaces your previous one, and sending your current emoji again clears it.

Example - toggle a reaction:

POST /wp-json/jetonomy/v1/posts/42/reactions
{
  "emoji": "rocket"
}

Reading reactions is open to any visitor; toggling a reaction requires the jetonomy_vote capability (logged-in members by default). See the REST API reference for full payloads.

What's Next?

Allow members to message each other privately, without leaving your community.

Private Messaging →

Let members send direct messages to each other - one-on-one or in small groups - without leaving your community.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to enable Private Messaging
• How members start conversations and send messages
• How unread counts and notifications work
• How to block users from messaging you
• How to use the REST API for conversations and messages

Why Private Messaging Matters

When members can message each other directly, your community becomes a platform - not just a forum. It reduces off-site communication, keeps relationships within your ecosystem, and gives you a richer, stickier product.

How It Works

Private Messaging adds a dedicated inbox at /community/messages/. Members can start a new conversation with any other member, or create a group conversation with up to 20 participants. Each conversation is a persistent thread - messages appear in chronological order, and new messages are loaded automatically via polling.

Enabling Private Messaging

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Private Messaging and click Enable.
3. A Messages link appears automatically in the community navigation bar.

No additional configuration is required to go live.

Starting a Conversation

Members start a new conversation in two ways:

• Click New Message from the Messages inbox at /community/messages/.
• Click the Message button on any member's profile page.

Both methods open a composer. Members type the recipient's name (autocomplete searches by display name and username), write their first message, and hit Send. The conversation thread opens immediately.

For group conversations, members add multiple recipients before sending. The group conversation shows all participants' avatars at the top of the thread.

Group Conversations

A conversation is either direct (1:1) or a group with multiple participants. Add several recipients in the composer to start a group thread, and every participant sees the same shared history.

Group threads keep a complete record. When a member leaves a group, their past messages stay in place attributed to them with a "left the conversation" note - Jetonomy does not delete the messages, so the thread always reads coherently. Creating a direct message to someone you already have a 1:1 thread with reuses that existing thread instead of starting a duplicate.

Archive, Leave, and Mute

Each of these is a per-member setting - your choice never changes the conversation for the other participants.

• Mute - silences notifications for a conversation while keeping it in your inbox. New messages still arrive; you just are not pinged. Unmute from the same menu.
• Archive - hides a conversation from your main inbox to keep it tidy. Archived conversations stay fully intact and reappear (or can be reopened) when there is new activity; nothing is deleted.
• Leave - removes you from a group conversation. You stop receiving its messages, but the thread and your past messages remain for everyone still in it. Leaving applies to group conversations.

Unread Counts and Notifications

A red badge on the Messages nav icon shows the total number of unread conversations. The count updates every 30 seconds via polling. It drops to zero when a member opens and reads the conversation.

Jetonomy also sends a notification to the recipient's bell icon when a new message arrives. Members who have email notifications enabled for private messages receive an email notification as well.

Tip: Members control their messaging email notifications in Profile → Notification Settings. Admins cannot override individual user preferences.

Blocking Users

Any member can block another from sending them messages:

1. Open a conversation with the person.
2. Click the ··· menu in the thread header.
3. Select Block [username].

Blocked users cannot send new messages to the member who blocked them. Existing conversation history is preserved but no new messages are delivered. The blocked user sees a generic "Unable to send message" error - they are not told they are blocked.

Admins can view and clear blocks in Jetonomy → Users → [username] → Messaging.

Note (1.8.0+): This is separate from the community-wide blocking a member can do from the mobile app or REST API (see Blocking a Member), which hides a member's replies across the whole community rather than just messaging. As of 1.8.0, the two work together: Private Messaging also honors a community-wide block, so you cannot start or continue a conversation with someone you have blocked, or who has blocked you, even outside this menu.

REST API

Private Messaging adds endpoints under jetonomy/v1:

Method	Endpoint	Description
GET	/conversations	List your conversations (paginated, filterable)
POST	/conversations	Start a new direct or group conversation
GET	/conversations/{id}	Get conversation details and participant list
PATCH	/conversations/{id}	Update your settings on the conversation (mute)
GET	/conversations/{id}/messages	List messages (cursor-based pagination)
POST	/conversations/{id}/messages	Send a message
GET	/conversations/unread-count	Your total unread conversation count (30s cache)
POST	/conversations/{id}/mute	Mute or unmute the conversation for you
POST	/conversations/{id}/archive	Archive or unarchive the conversation for you
POST	/conversations/{id}/leave	Leave a group conversation
POST	/conversations/{id}/block	Block or unblock the other participant (direct only)

All endpoints require authentication, and member operations on a conversation require you to be a participant. Starting a conversation and sending messages require Trust Level 1 or higher (admins and moderators bypass this). See the REST API reference for full payloads.

Example - start a conversation:

POST /wp-json/jetonomy/v1/conversations
{
  "recipients": [45, 67],
  "message": "Hey, wanted to follow up on your question about onboarding."
}

Example - get messages with cursor pagination:

GET /wp-json/jetonomy/v1/conversations/12/messages?after=msg_abc123&per_page=20

Site-Owner Oversight (Conversations Admin Page)

New in 1.5.0. Site administrators get a dedicated Jetonomy → Conversations page in the WordPress admin sidebar for messaging oversight - useful for abuse investigations, GDPR requests, and verifying that messaging is healthy on a large community. The page is visible to administrators only (it requires the manage_options capability).

• Conversations list - every conversation with its ID, type (direct or group), participants, message count, and last activity, most recently active first and paginated at 50 per page so it stays fast even with tens of thousands of threads.
• Thread detail - click any conversation to read its full message history. Messages are shown newest first, paginated at 50 per page, each with the sender's display name (shown as "Deleted user" if the account no longer exists), a plain-text excerpt of the message (up to 300 characters), and the sent timestamp.
• Purge - permanently delete a conversation and all of its messages and read-state rows. The button asks for confirmation ("Permanently delete this conversation for all participants?"); on confirm the conversation is removed, you return to the list with a "Conversation purged" notice, and the deletion fires the jetonomy_pro_conversation_purged action so audit tooling can record it.

Purging is irreversible and bypasses the participants' own archive/leave state - reserve it for moderation and compliance situations. It does not notify participants, does not touch their accounts or trust levels, and does not remove any posts or replies they made in public spaces.

Privacy: Site owners can read members' private conversations from this page. State this in your site's privacy policy so members understand your platform's moderation and compliance position.

What's Next?

Add polls to any topic to gather community input and drive decisions.

Polls →

Attach a poll to any topic and let your community vote - perfect for decisions, feedback, and feature prioritization.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to enable Polls
• How to attach a poll when creating or editing a topic
• How members vote, change their vote, and remove it
• How poll results are displayed
• How poll creators close a poll

Why Polls Matter

Asking a question in text is passive. Attaching a poll turns the same question into an action - members click an option in seconds instead of writing a response. You get quantified signal, higher engagement on that post, and a result the whole community can see at a glance.

Enabling Polls

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Polls and click Enable.
3. A + Add Poll button appears at the bottom of the post composer.

Creating a Poll

When writing a new topic, click + Add Poll beneath the content editor.

The poll builder lets you:

• Write up to 20 options (minimum 2 required).
• Choose Single choice (members pick one) or Multiple choice (members pick several).
• Optionally set a Close date - the poll stops accepting votes automatically at that date and time.

The poll is attached to the topic and saved together when you click Post. You cannot attach a poll to a reply - only to top-level topics.

Tip: You can add or remove a poll from an existing topic by editing the post. Removing a poll permanently deletes all votes cast on it.

How Members Vote

The poll appears below the post body, before any replies. Each option is displayed as a labeled button.

• Single choice - clicking an option records your vote immediately. You see the results as percentage bars as soon as you vote.
• Multiple choice - checkboxes appear. Select all the options you want and click Vote.

After voting, members can change their vote by clicking a different option. Clicking your current selection a second time removes your vote entirely.

Members who have not voted see the options. Members who have voted see the live results. This design keeps undecided members from being anchored by early results.

Reading Results

Results display as horizontal percentage bars with the option label, the percentage, and the raw vote count. Bars fill in proportion to the leading option.

The total vote count appears below the bar chart. If the poll has a close date, a countdown shows how much time remains.

Closing a Poll

The topic author and any space moderator can close a poll at any time:

1. Open the topic.
2. Click the ··· menu on the poll card.
3. Select Close Poll.

Once closed, the poll shows a Closed badge and no further votes are accepted. Existing results remain visible. A closed poll can be re-opened by the same users using the same menu.

Note: If you set a close date and later want to extend it, edit the post and update the date in the poll settings.

Multi-Select Voting

A poll is either single choice or multiple choice, set when you build it:

• Single choice records exactly one option per member. Voting for a different option moves the vote.
• Multiple choice lets each member pick several options at once. Each option toggles independently - a member can hold any number of selections, and clicking a chosen option a second time clears just that one.

Because of this, the total vote count on a multiple-choice poll can be higher than the number of voters - one member can contribute several votes.

Polls Admin

Enabling the extension adds a Polls submenu under the Jetonomy admin menu (jetonomy-pro-polls). It lists every poll in your community with its post, type, total votes, and close state, so you can review and close polls without opening each topic.

REST API

Polls registers these endpoints under jetonomy/v1:

Method	Endpoint	Description
POST	/posts/{post_id}/poll	Create a poll on a post
GET	/posts/{post_id}/poll	Get a poll's options and live vote counts
POST	/polls/{id}/vote	Cast a vote - pass option_id for single choice or option_ids (array) for multiple choice
DELETE	/polls/{id}/vote	Remove your vote(s) from the poll
PATCH	/polls/{id}	Update a poll (for example, change the close date)

Creating a poll and voting require the member to be logged in; poll creation additionally requires the right to post in the target space. See the REST API reference for full request and response payloads.

What's Next?

Collect structured information about your members with custom profile fields.

Custom Profile Fields →

Add structured fields to member profiles - collect the information that matters to your specific community.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to create and manage custom profile fields
• Which field types are available
• How to set visibility and required status
• How members fill in their fields
• How to read and update field values via the REST API

Why Custom Fields Matter

A generic WordPress profile has a bio and a website URL. That is not enough for most communities. A developer community needs a GitHub handle. A healthcare community needs a specialty. A SaaS community needs a company name. Custom Fields lets you define exactly the information that makes members useful and findable in your community.

Enabling Custom Fields

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Custom Fields and click Enable.
3. A Custom Fields item appears under the Jetonomy admin menu.

Creating a Field

1. Go to Jetonomy → Custom Fields.
2. Click Add Field.
3. Fill in the field settings:

Setting	Description
Label	Displayed on the profile and in the edit form
Field Key	Unique slug used in the REST API (auto-generated, editable)
Type	See field types below
Required	If on, members cannot save their profile without filling this in
Visibility	Who can see the field value
Description	Optional helper text shown below the input

4. Click Save Field.

Field Types

Type	Best for
Text	Short single-line answers (job title, company, username)
Textarea	Longer free-form text (bio supplement, expertise description)
Number	Numeric values (years of experience, team size)
Email	Contact email address
URL	Website, GitHub, LinkedIn, portfolio links
Select	Predefined options as a dropdown, single choice (country, role, industry)
Checkbox	Yes/no toggle (newsletter opt-in, open to work)
Radio	Predefined options as radio buttons, single choice
Date	A calendar date (joined date, availability)

For the Select and Radio types, you define the options in the field editor - one per line. Select renders a dropdown; Radio renders a set of radio buttons.

Visibility Options

Each field has one of three visibility settings:

Visibility	Who sees the value
Public	Anyone, including logged-out visitors
Members only	Logged-in community members
Private	Only the member themselves and admins

Private fields are still editable by the member but do not appear on their public profile. They are accessible to admins via the admin Users page.

How Members Fill In Fields

Members edit their custom fields at /community/u/{username}/edit/ under the Profile Details section. Required fields show a red asterisk. Saving the profile validates all required fields before updating.

Tip: Guide members to complete their profiles right after joining by linking to the edit profile page in your welcome notification or email digest.

REST API

Custom Fields adds field-aware parameters to the existing profile and post endpoints:

Method	Endpoint	Description
GET	/users/{id}	Profile response includes custom_fields object
GET	/users	List response includes custom_fields on each member
PATCH	/users/{id}	Pass custom_fields: { field_key: value } to update
GET	/posts/{id}	Post response includes custom_fields if any post-level fields are configured
GET	/posts	List response includes custom_fields on each post
GET	/custom-fields	List all defined fields and their settings
POST	/custom-field-values	Set a single field value on a target object (user or post)

Example - read a profile with custom fields:

GET /wp-json/jetonomy/v1/users/45

{
  "id": 45,
  "name": "Priya Sharma",
  "custom_fields": {
    "company": "Acme Corp",
    "github_username": "priyasharma",
    "open_to_work": true
  }
}

Example - update custom fields:

PATCH /wp-json/jetonomy/v1/users/45
{
  "custom_fields": {
    "company": "New Horizons Ltd"
  }
}

Members can only update their own fields. Admins can update any member's fields.

Setting one value at a time: if you want to set a single field on a single object rather than sending the whole custom_fields object, POST /custom-field-values with the field key, the target object type and ID, and the value. This is the lightweight path used by the edit-profile form and is handy for partial updates from custom tooling.

How fields surface in output: once a field is configured, its value is embedded automatically in the relevant REST responses - the custom_fields object on /users and /posts (and their list endpoints) - and rendered on the matching frontend surface (the member profile for profile fields, the post for post fields), subject to the field's visibility setting. You do not register a separate read endpoint per field; the value rides along with the object it belongs to.

See the REST API reference for full payloads.

Upgrading From Older Versions

If you are on Jetonomy 1.4.1 or newer, custom field values are returned automatically on the /jetonomy/v1/posts and /jetonomy/v1/users endpoints, so any tool reading the API sees every field you have configured. On older versions the values were saved to the database but did not appear in API responses - update both the free and Pro plugins together to read custom fields over the API.

What's Next?

Recognize and reward your most engaged members with custom badges.

Custom Badges →

Design your own badges, set the conditions that earn them, and watch members compete to collect them.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to create a badge with a name, icon, and tier
• How to set auto-award conditions
• How to award badges manually as an admin
• How badges display on member profiles

Why Custom Badges Matter

Trust levels and reputation points are invisible to casual members. Badges are visible, collectible, and shareable - they give members a concrete goal to aim for. A "100 Posts" badge tells the community this member is active. A "Top Answerer" badge signals expertise. Badges convert passive lurkers into active contributors.

Enabling Custom Badges

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Custom Badges and click Enable.
3. A Badges item appears under the Jetonomy admin menu.

Creating a Badge

1. Go to Jetonomy → Badges.
2. Click Create Badge.
3. Fill in the badge details:

Field	Description
Name	Displayed on the badge and in the award notification
Description	One sentence explaining how to earn it
Icon	Upload a 64×64 PNG or SVG icon
Tier	Bronze, Silver, or Gold - controls the border color on profile

4. Set the award conditions (see below).
5. Click Save Badge.

Award Conditions

Auto-Award

Auto-awarded badges evaluate all members on a regular schedule and grant the badge automatically when the conditions are met. Choose from built-in criteria:

Criteria	Example threshold
Total posts	10, 50, 100, 500 posts
Accepted answers	5, 25, 50 accepted answers
Total replies	25, 100, 250 replies
Upvotes received	10, 50, 200 upvotes on any content
Days as member	30, 180, 365 days since joining
Reputation	100, 500, 1000 reputation points
Trust level	Trust level 1 through 5
Spaces joined	3, 10, 25 spaces joined

Set the threshold for each criteria you want to use. You can combine multiple criteria with all (the member must satisfy every condition) or any (one is enough) to earn the badge.

Note: Auto-evaluation runs automatically - a recurring job every 6 hours (via Action Scheduler, with a WP-Cron fallback), plus event-driven re-evaluation that fires when a member's posts, replies, votes, reputation, or trust level change. There is no manual "evaluate now" button.

Manual Award

Some badges should not be automated - "Staff Pick", "Most Helpful in July", or "Community Founder" are judgment calls. For these, leave all auto-award criteria blank and award manually:

1. Go to Jetonomy → Users and open the member's profile.
2. Click Award Badge.
3. Select the badge from the list and add an optional private note.
4. Click Award.

The member receives a notification immediately and the badge appears on their profile.

Badge Tiers

Badges have three visual tiers that appear as border colors on the badge icon:

Tier	Color	Suggested use
Bronze	Warm bronze	Entry-level milestones (first post, 7-day streak)
Silver	Cool silver	Mid-tier milestones (100 posts, 10 accepted answers)
Gold	Bright gold	Elite milestones (500 posts, Top Contributor of the year)

Tiers are visual only - they do not affect permissions or trust levels.

Badge Display

Badges appear on member profile pages in a dedicated Badges section. Members who have earned no badges see an empty state that lists a few featured badges to work toward - this passively encourages engagement.

The three most recently earned badges also appear in the member's hover card, which pops up when anyone hovers their username throughout the community.

REST API

Custom Badges registers these endpoints under jetonomy/v1:

Method	Endpoint	Description
GET	/badges	List all defined badges and their settings
POST	/badges	Create a badge
PATCH	/badges/{id}	Update a badge
DELETE	/badges/{id}	Delete a badge
POST	/users/{id}/badges	Award a badge to a member

Badges can be created, edited, and awarded entirely through REST, so you can automate awards from your own tooling or grant a badge as part of an external workflow. Listing badges is open to any logged-in member; creating, editing, deleting, and awarding require manage_options. See the REST API reference for full payloads.

What's Next?

Get a data-driven view of your community's health with the Analytics Dashboard.

Analytics Dashboard →

Understand what your community is doing, where it is growing, and who is driving it - all from a single admin dashboard.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to access the Analytics dashboard
• Which metrics are tracked and what they mean
• How to use the date range filter
• How to export data as CSV

Why Analytics Matter

You cannot grow what you cannot measure. The Analytics dashboard turns raw community activity into actionable metrics - so you know which spaces need attention, who your power users are, and whether engagement is trending up or down before it becomes a problem.

Enabling Analytics

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Analytics and click Enable.
3. An Analytics item appears under the Jetonomy admin menu.

Analytics begin recording from the moment you enable the extension. Historical data before activation is not backfilled.

Navigating the Dashboard

Go to Jetonomy → Analytics. The dashboard opens on the last 30 days by default.

Date Range Filter

Use the date range picker at the top right to select any custom range. Preset shortcuts:

• Last 7 days
• Last 30 days
• Last 90 days
• This month
• Last month

All charts and tables update instantly when you change the range.

Overview Metrics

The top row shows four headline numbers for your selected range:

Metric	What it means
Total Posts	New topics created in the period
Total Replies	New replies created in the period
Active Members	Unique members who posted, replied, or voted
Growth Rate	Percentage change vs the previous equal-length period

Below the headline row, a line chart shows daily post and reply volume over the selected range. Spikes are easy to spot - hover any point to see the exact date and count.

Counting semantics (improved in 1.5.0): the daily totals count published content and stay accurate through the whole content lifecycle. A post created as pending counts on the day it was created once a moderator approves it; trashing a published post removes it from its original day's total (never producing negative days); restoring adds it back. Earlier versions counted at creation only, so moderated or trashed content slowly drifted the totals.

Top Spaces

A ranked table shows your most active spaces sorted by total posts + replies in the period. Columns include post count, reply count, unique contributors, and engagement rate (replies per post).

Use this view to find spaces that are thriving - and spaces that have gone quiet and may need a prompt or a featured topic.

Top Contributors

A ranked table of your most active members sorted by total contributions (posts + replies + accepted answers). Each row shows the member's avatar, display name, trust level, and contribution breakdown.

Tip: Use this list to identify members to invite into a moderator role, feature in a community spotlight, or send a personal thank-you.

Engagement Metrics

The engagement section shows:

Metric	What it means
Avg. replies per post	How much discussion each new topic generates
Vote activity	Total upvotes and downvotes cast
Accepted answers	Q&A spaces only - rate of questions getting resolved
New member joins	Community growth over the period

Moderation Stats

The moderation section shows flagged content volume, auto-moderation rule triggers (if Advanced Moderation is enabled), and moderator response time. A high flag volume combined with slow response time signals you need more moderators.

CSV Export

Click Export CSV in the top right of any table to download a full data export for the current date range. Exports include all rows - not just the visible page.

Exported files are compatible with Excel, Google Sheets, and any BI tool. Column headers match the on-screen labels exactly.

Dual-Path Aggregator (1.4.1, observation only)

In 1.4.1 a second analytics path runs quietly alongside the existing direct-query reader. It's an event-driven aggregator that writes to a new internal table (jt_pro_analytics_aggregate) on every relevant community event, instead of querying core tables every time the dashboard loads.

The aggregator is in a 7-day observation window. Your dashboards still read from the original direct-query path in 1.4.1 - there is no public-facing behaviour change yet. The point of the observation window is to verify that the two paths agree before flipping the default.

Verify Dual-Path admin toggle

Go to Jetonomy → Analytics. The Pro Analytics page now has a Verify dual-path toggle. Turn it on and every metric on the page is shown twice - once from the direct-query reader, once from the aggregator - with a drift percentage between them. Use this if you want to spot-check the aggregator's accuracy before we promote it to default.

GET /jetonomy/v1/analytics/diff-report

For programmatic comparison, the same data is available at:

GET /wp-json/jetonomy/v1/analytics/diff-report?range=30d

{
  "range": "30d",
  "metrics": [
    { "key": "total_posts", "direct": 1284, "aggregated": 1284, "drift_pct": 0 },
    { "key": "active_members", "direct": 312, "aggregated": 311, "drift_pct": -0.32 }
  ]
}

Helpful if you want to ship a custom monitoring panel during the observation window.

What's Next?

Reduce your moderation workload by automating common moderation decisions.

Advanced Moderation Rules →

Define rules that catch bad content automatically - before it ever appears in your community.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to enable Advanced Moderation Rules
• How to create keyword, regex, link-limit, and spam-score rules
• What actions each rule can take on matched content
• How to scope rules to a specific space or apply them globally
• How to read rule trigger statistics

Why Auto-Moderation Matters

Manual moderation does not scale. A single moderator reviewing every post works fine at 10 posts per day - it fails at 1,000. Auto-moderation rules handle the obvious cases automatically so your human moderators can focus on edge cases that require judgment.

Advanced Moderation complements the free trust level system. New members with Trust Level 0 are already rate-limited. Auto-moderation rules add a content layer on top of that.

Enabling Advanced Moderation

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Advanced Moderation and click Enable.
3. A Moderation Rules tab appears under Jetonomy → Moderation.

Creating a Rule

1. Go to Jetonomy → Moderation → Rules.
2. Click Add Rule.
3. Configure the rule:

Setting	Description
Name	Internal label - members never see this
Pattern type	Keyword, Regex, Link limit, or Spam score
Pattern	The word, phrase, regex, or threshold to match
Action	What happens when the rule triggers
Scope	Global (all spaces) or a specific space
Active	Enable or disable the rule without deleting it

4. Click Save Rule.

Pattern Types

Keyword

Matches any post or reply body that contains the exact word or phrase (case-insensitive). Use comma-separated values to match any of several words with a single rule.

Example: buy now, click here, limited offer

Regex

Full regular expression matched against the post body. Use this for patterns a keyword list cannot capture - phone number patterns, URL shortener patterns, or obfuscated spam.

Example: \b(\+?1[-.\s]?)?\(?\d{3}\)?[-.\s]?\d{3}[-.\s]?\d{4}\b

Note: Regex patterns are evaluated server-side using PHP preg_match(). Test your regex at regex101.com before adding it to a live rule.

Link Limit

Triggers when a post or reply contains more than a set number of links. New spammers often post content with 5-10 outbound links. A limit of 3 catches most of these while allowing legitimate "here are some resources" posts.

Spam Score

Jetonomy calculates a spam probability score (0-100) for each post based on content patterns, account age, and posting frequency. Set a threshold - any post above that score triggers the rule.

A threshold of 80 is a good starting point. Lower it only if you are seeing spam slip through.

Rule Actions

Action	What happens
Flag	Content publishes normally and is added to the mod queue with a flag
Hold	Content is held as Pending and does not appear until a moderator approves it
Block	The post is rejected and the member sees an error message
Spam	Content is marked as spam and hidden immediately

Choose the least restrictive action that solves the problem. Use Flag for borderline content, Hold for likely-bad content, and Block or Spam for clearly harmful content.

Rule Scope

Global rules apply to every post and reply across all spaces. Use these for site-wide policies - prohibited words, adult content, competitor spam.

Space-scoped rules apply only within a specific space. Use these for space-specific norms - a Support space might block all links to prevent fishing attacks, while General Chat allows them freely.

Rule Statistics

The rules list shows a Triggered count for each rule - how many times it has fired since the rule was created. Click a rule to see a breakdown by action, by space, and a timeline chart.

Use this data to tune your rules. A rule that triggers 500 times in a week and sends everything to Spam probably needs a higher threshold - it is catching legitimate content.

REST API

Advanced Moderation manages rules under jetonomy/v1:

Method	Endpoint	Description
GET	/moderation/rules	List all moderation rules
POST	/moderation/rules	Create a rule
PATCH	/moderation/rules/{id}	Update a rule
DELETE	/moderation/rules/{id}	Delete a rule
GET	/moderation/rules/{id}/stats	Get a rule's trigger statistics

All routes require manage_options. See the REST API reference for full payloads.

What's Next?

Re-engage members who have not visited recently with automated email digests.

Email Digest →

Send a curated summary of community activity to members' inboxes - daily or weekly - so they never feel out of the loop.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to enable and configure the Email Digest
• What content appears in each digest
• How members control their digest frequency
• How to send a test digest as an admin

Why Email Digest Matters

Most community members are not daily visitors. They join, participate a few times, and drift away - not because they lost interest, but because they forgot. A well-timed email digest brings them back. It shows them what they missed and gives them a reason to click.

Enabling Email Digest

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Email Digest and click Enable.
3. Go to Jetonomy → Settings → Email Digest to configure sending times and content rules.

Configuring the Digest

Send Schedule

Set when the digests go out:

Digest type	Default send time
Daily	8:00 AM (site timezone)
Weekly	Monday, 8:00 AM (site timezone)

You can change both send times in the Email Digest settings. Times use the timezone set in Settings → General → Timezone in WordPress.

Digest Content

The digest compiles:

• Top posts - the most-upvoted new topics since the last digest
• Active discussions - posts with the most replies in the period
• Spaces you follow - activity in spaces the member has joined or bookmarked
• Replies to your topics - new replies on topics the member created or commented on
• 🏆 Badges earned (new in 1.4.1) - every badge the member earned during the digest window
• 🗳️ Polls voted on (new in 1.4.1) - every poll the member participated in during the window

You can toggle each content section on or off in the digest settings. At least one section must remain on.

How the new sections work: badges and polls are tracked in a per-user buffer that's capped at 100 events with a 30-day TTL. The buffer is cleared only after a successful send, so opted-out members never accumulate state, and a missed send doesn't lose the activity.

Tip: Keeping "Replies to your topics" on is the single most effective setting. Members always care more about activity on their own posts than about the broader community.

Member Notification Preferences

Each member controls their own digest frequency from Profile → Notification Settings → Email:

Option	What it means
Instant	Individual emails per event (free behavior)
Daily digest	One email per day summarizing activity
Weekly digest	One email per week summarizing activity
None	No community emails

Members who select Daily or Weekly stop receiving per-event notification emails. The digest replaces them - they are not sent in addition to them.

New members default to Daily digest. You can change this default in the Email Digest settings.

Admin Test Send

Before going live, send yourself a test digest to check formatting and content:

1. Go to Jetonomy → Settings → Email Digest.
2. Scroll to the Test Send section.
3. Enter an email address (pre-filled with your admin email).
4. Click Send Test Digest.

The test digest uses real community data from the last 7 days. If your community is new and has little activity, the digest may look sparse - that is expected.

Digest Statistics

The Email Digest settings page shows send statistics for the last 90 days:

Stat	Description
Digests sent	Total number of emails delivered
Preference breakdown	How many members are on daily vs weekly vs none

Open rates and click rates are available if you use a supported ESP adapter (SendGrid, Mailgun, SES, or Postmark) - basic wp_mail delivery does not provide tracking data.

REST API

Email Digest exposes endpoints under jetonomy/v1:

Method	Endpoint	Description
GET	/users/me/digest-preferences	Read the current member's digest frequency and section choices
PATCH	/users/me/digest-preferences	Update the current member's digest preferences
POST	/admin/digest/test	Send a test digest (admin)
GET	/admin/digest/stats	Read digest send statistics (admin)

Members manage their own preferences; the /admin/* routes require manage_options. See the REST API reference for full payloads.

What's Next?

Connect your community to external tools like Slack, CRMs, and Zapier using outbound webhooks.

Outbound Webhooks →

Automatically send community events to any external URL - connect Jetonomy to Slack, Zapier, your CRM, or any custom pipeline.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to create and manage webhook endpoints
• Which community events you can subscribe to
• How to test a webhook before going live
• How to read the delivery log to debug failures

Why Webhooks Matter

Jetonomy lives inside WordPress - but your business does not. Your team lives in Slack. Your sales data lives in a CRM. Your analytics live in a data warehouse. Webhooks close that gap. Every time something happens in your community, Jetonomy can push that data wherever you need it - in real time, with zero polling.

Enabling Webhooks

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find Outbound Webhooks and click Enable.
3. A Webhooks item appears under the Jetonomy admin menu.

Creating a Webhook

1. Go to Jetonomy → Webhooks.
2. Click Add Webhook.
3. Fill in the endpoint settings:

Setting	Description
URL	The HTTPS endpoint that will receive the POST request
Events	Which community events trigger this webhook
Secret	Optional signing secret for verifying payload authenticity
Active	Toggle the webhook on or off without deleting it

4. Click Save Webhook.

Available Events

Subscribe to any combination of these events:

Event	Fires when...
post.created	A new topic is published
post.updated	A topic is edited
post.deleted	A topic is deleted or trashed
reply.created	A new reply is posted
reply.updated	A reply is edited
reply.deleted	A reply is deleted or trashed
vote.cast	A member votes on a post or reply
answer.accepted	A Q&A answer is accepted
member.joined	A new user joins the community
member.left	A member leaves a space
member.banned	A member is banned
user.registered	A new user account is created
trust_level.changed	A member is promoted or demoted
flag.created	Content is flagged by a member
flag.resolved	A flag is resolved by a moderator
moderation.action	A moderator approves, spams, or trashes content

You can create multiple webhooks pointing to different URLs with different event subsets - for example, one webhook for Slack (post events only) and one for your CRM (member events only).

Payload Format

Every webhook delivers a JSON body with this structure:

{
  "event": "post.created",
  "timestamp": "2026-03-26T08:14:32Z",
  "site_url": "https://yoursite.com",
  "data": {
    "post_id": 1024,
    "title": "How do I reset my password?",
    "author_id": 45,
    "author_name": "Priya Sharma",
    "space_id": 3,
    "space_slug": "support",
    "url": "https://yoursite.com/community/s/support/t/how-do-i-reset-my-password/"
  }
}

The data object varies by event type. All events include event, timestamp, and site_url.

Verifying Payloads

If you set a secret, Jetonomy includes an X-Jetonomy-Signature header with each request. The value is an HMAC-SHA256 signature of the raw request body, signed with your secret.

Verify on your server:

$signature = hash_hmac( 'sha256', $raw_body, $your_secret );
$expected   = 'sha256=' . $signature;
$received   = $_SERVER['HTTP_X_JETONOMY_SIGNATURE'];

if ( ! hash_equals( $expected, $received ) ) {
    http_response_code( 401 );
    exit;
}

Testing a Webhook

Before you point a webhook at a production system, send a test:

1. Open the webhook in Jetonomy → Webhooks.
2. Click Send Test.
3. Jetonomy sends a sample ping event to your URL and shows the HTTP response code and body inline.

Use a tool like webhook.site to inspect the full request during development.

Delivery Log

Every delivery attempt is logged. Go to Jetonomy → Webhooks → [webhook name] → Delivery Log to see:

• Timestamp of each attempt
• HTTP response code
• Response body (first 500 characters)
• Whether the delivery succeeded or failed

Failed deliveries are retried up to three times with exponential backoff (5 min, 30 min, 2 hrs). After the third failure, the delivery is marked as permanently failed and no further retries are attempted.

Tip: If you see consistent failures, check that your endpoint returns a 2xx response within 10 seconds. Jetonomy times out at 10 seconds and treats the delivery as failed.

Use Case Examples

• Slack notifications - Post a message to a Slack channel whenever a new topic is created in your community.
• CRM sync - Push member.joined events to HubSpot or Salesforce to trigger a welcome sequence.
• Zapier - Connect any event to thousands of apps via a Zapier webhook trigger - no custom code needed.
• Analytics pipeline - Stream all events to a data warehouse like BigQuery or Amplitude for long-term retention and custom analysis.

Upgrading From Older Versions

On Jetonomy 1.4.1 and newer every event in the list above fires reliably for real community activity. If you configured webhooks on an older version and saw zero deliveries despite real activity, update both the free and Pro plugins together to 1.4.1 or later - your existing webhooks start delivering without any reconfiguration.

What's Next?

Send browser push notifications to members even when they are not on your site.

Web Push Notifications →

Reach members with browser push notifications - even when they have closed your site.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to generate VAPID keys and enable Web Push
• How members subscribe to push notifications
• Which events trigger a push notification
• Which browsers are supported

Why Web Push Matters

Email notifications have open rates around 20-30%. Browser push notifications have open rates above 60% because they appear immediately on the member's screen - no inbox, no subject line, no waiting. For time-sensitive events like a reply to your question or a mention from a teammate, push gets the message there instantly.

Enabling Web Push

Web Push requires a VAPID key pair to authenticate your server with browsers.

1. Go to Jetonomy → Settings → Web Push.
2. Click Generate VAPID Keys. Jetonomy creates a public/private key pair and stores them in your WordPress options table.
3. Toggle Enable Web Push to on.
4. Click Save.

Important: VAPID keys are generated once. If you regenerate them, all existing push subscriptions are invalidated and members must subscribe again. Only regenerate if you believe your private key has been compromised.

Service Worker Registration

Jetonomy automatically registers a service worker (/community/sw.js) on every community page. You do not need to create or configure the service worker - this happens at extension activation.

The service worker handles:

• Receiving push messages from the Jetonomy server
• Displaying the browser notification
• Opening the correct URL when the notification is clicked

Note: Every push payload is encrypted per RFC 8291 (aes128gcm content encoding) before it leaves your server, so browsers and push services accept it and its contents are never readable in transit.

Looking for push on a native iOS or Android app instead of the browser? The same extension registers app devices for native push - see Native push setup.

Member Subscription

The first time a logged-in member visits any community page after you enable Web Push, a Enable push notifications prompt appears at the top of the page. Clicking Enable triggers the browser's native permission dialog.

Members who grant permission are subscribed automatically. Their subscription is stored in the Jetonomy database and associated with their account.

Members can unsubscribe at any time from Profile → Notification Settings → Push Notifications → Off.

Note: The browser permission prompt can only be triggered by a user action (a click). Jetonomy waits for the member to interact with the prompt banner before requesting permission - it never requests permission automatically on page load.

Notification Events

Push notifications are sent for the same events that trigger bell notifications, based on each member's preferences:

Event	Who receives a push
New reply on your topic	Topic author
New reply in a topic you follow	Followers
You are mentioned	Mentioned member
Your answer is accepted	Answer author
New message received	Message recipient (Private Messaging Pro)
Badge awarded	Badge recipient

Members control which of these events trigger a push in Profile → Notification Settings.

Browser Support

Web Push works on all major modern browsers without any app installation:

Browser	Desktop	Mobile
Chrome	Yes	Yes (Android)
Edge	Yes	Yes (Android)
Firefox	Yes	Limited
Safari	Yes (macOS 13+)	Yes (iOS 16.4+)

Tip: Safari on iOS requires members to add your site to their Home Screen before push notifications work. This is an Apple platform limitation - not a Jetonomy limitation.

REST API

Web Push registers these endpoints under jetonomy/v1:

Method	Endpoint	Description
POST	/push/subscribe	Register the current member's browser push subscription
DELETE	/push/subscribe	Remove the current member's push subscription
GET	/push/vapid-key	Fetch the public VAPID key the browser needs to subscribe
GET	/push/service-worker.js	Serve the service worker script

Subscribe and unsubscribe require the member to be logged in; the VAPID key and service worker are served for the page to register push. See the REST API reference for full payloads.

What's Next?

Let members reply to community topics directly from their email client.

Reply by Email →

Let members reply to community discussions directly from their email client - no login required for that one reply.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How Reply by Email works end to end
• How to configure the inbound email endpoint
• How emails are parsed and turned into replies
• How to test the feature and handle parsing errors

Why Reply by Email Matters

Every step between "I got a notification" and "I posted a reply" loses members. Reply by Email removes all those steps. The member reads the notification in their inbox, types a reply directly, hits Send, and the reply appears in the community - without opening a browser or logging in. Removing that friction increases reply volume noticeably.

How It Works

1. Jetonomy sends a notification email for a new reply or mention.
2. The email contains a Reply to this post call to action with a unique reply-to address.
3. The member replies to that email.
4. The inbound email is delivered to your configured endpoint.
5. Jetonomy parses the email, strips quoted content, and creates a community reply attributed to that member.

Each reply-to address is unique to the member and the topic - it encodes an authentication token so no login is required.

Configuration

Reply by Email requires an inbound email endpoint - a URL that receives incoming emails from your email provider. Most email providers (SendGrid Inbound Parse, Mailgun Inbound Routes, Postmark Inbound, or Amazon SES with SNS) can forward inbound email as an HTTP POST to a URL.

Step 1: Get Your Inbound Endpoint URL

1. Go to Jetonomy → Settings → Reply by Email.
2. Copy the Inbound Endpoint URL. It looks like:

https://yoursite.com/wp-json/jetonomy/v1/email/inbound

Step 2: Configure Your Email Provider

Point your email provider's inbound parsing feature at the Jetonomy endpoint URL. The exact steps vary by provider - follow your provider's documentation for "inbound email parsing" or "inbound routing."

Set up a dedicated inbound domain or subdomain for replies. Example: reply.yoursite.com. Your provider resolves inbound mail sent to *@reply.yoursite.com and forwards the parsed payload to your Jetonomy endpoint.

Step 3: Enter Your Reply Domain

Back in Jetonomy → Settings → Reply by Email, enter the reply domain (e.g. reply.yoursite.com) and click Save.

Jetonomy now generates per-user, per-topic reply addresses using that domain.

Email Parsing

Jetonomy parses the incoming email using these rules:

1. Strip quoted content - Lines that begin with > (standard email quoting) are removed. The reply contains only the new text the member typed.
2. Plain text preferred - If the email has a plain text part, Jetonomy uses that. If not, it strips HTML and uses the text content.
3. Basic formatting preserved - Line breaks are preserved. Links in the plain text body are converted to Markdown links.
4. Attachments ignored - Image and file attachments in reply emails are not processed in v1.0.

The parsed reply text goes through the same wp_kses_post sanitization as any other reply before it is saved.

Parsing Rules Configuration

You can adjust how Jetonomy handles edge cases:

Setting	Default	Description
Min reply length	5 characters	Rejects replies shorter than this (catches accidental sends)
Max reply length	10,000 characters	Truncates anything longer
Strip signatures	On	Removes common signature separators (-- , Sent from my iPhone, etc.)

Security

Each reply-to address contains a signed token that ties the email address to a specific WordPress user and topic. Jetonomy verifies the token before creating any reply. An attacker who intercepts or guesses a reply address cannot post as another member - the token is cryptographically bound to the user ID.

Tokens expire after 30 days. Notification emails older than 30 days cannot be replied to by email.

Testing Reply by Email

1. Go to Jetonomy → Settings → Reply by Email.
2. Click Send Test Email to send a sample notification to your admin email address.
3. Reply to that email with any text.
4. Return to the admin and click Check Last Inbound to see the parsed result.

What's Next?

Remove all Jetonomy branding and present the community as entirely your own.

White Label & Branding →

Remove all Jetonomy branding and present your community as entirely your own product.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How to enable White Label
• How to remove Jetonomy branding from the frontend and admin
• How to set a custom admin menu label and icon
• How to rebrand transactional emails and digests

Why White Label Matters

You built your community. Your members know your brand - not the plugin powering it. White Label means your community looks like yours from every angle: the frontend pages, the admin sidebar, and the notification emails. This is especially important for agencies delivering client projects and for SaaS products embedding community features under their own brand.

Enabling White Label

1. Go to Jetonomy → Extensions in your WordPress admin.
2. Find White Label and click Enable.
3. A Branding tab appears under Jetonomy → Settings.

Removing Frontend Branding

Go to Jetonomy → Settings → Branding.

Setting	Default	What it controls
"Powered by Jetonomy" footer	Shown	Remove the attribution link from the community footer
Jetonomy logo in community nav	Shown	Replace with your own logo or hide entirely
Custom CSS injection	Empty	Add CSS that loads on every community page

Upload your own logo (SVG or PNG, max 400×100 px) to replace the Jetonomy logo in the community navigation bar. Leave the logo field blank to show no logo at all.

Tip: Use the Custom CSS injection field to apply brand-specific color overrides without editing any theme files. The CSS injects after Jetonomy's own stylesheet so your values always win.

Admin Menu Customization

By default, the Jetonomy admin menu item is labeled "Jetonomy" with the Jetonomy logo icon.

In Jetonomy → Settings → Branding → Admin Menu:

• Menu label - Change to any string (e.g. "Community", "Forum", "My Community").
• Menu icon - Enter any Dashicons class (e.g. dashicons-groups) or leave blank to use the default.

The label change applies to the top-level menu item and the browser window title on all Jetonomy admin pages.

Email Branding

White Label also affects transactional emails and digests. In Settings → Branding → Email:

• From name - Defaults to your site name. Change to any value.
• Email footer - Replaces the default Jetonomy email footer with your own text or HTML.
• Logo in emails - Upload a logo displayed at the top of notification emails.

Branding Settings Reference

White Label stores its configuration in the jetonomy_pro_white_label option. The settings worth calling out:

Setting	What it does
header_logo_url	The logo actually displayed in the community header. This is the image members see at the top of every community page.
logo_url	The fallback / Open Graph logo. Used for social share cards (OG image) and anywhere a logo is needed but no header logo is set. Keep this set even if you customize the header separately.
accent_color	A global accent colour override. Recolours Pro-rebranded surfaces - including email accents - in one place so your brand colour is consistent across the community and its emails.
custom_css	Freeform CSS injected on every community page. It loads after Jetonomy's own stylesheet, so your rules always win - use it for brand colour and spacing tweaks without touching theme files.
sidebar_auth_card_html	Custom HTML for the community sidebar's sign-in / call-to-action card. When set, it replaces Jetonomy's default auth card with your own markup; leave it empty to keep the default card.
footer_text	Replaces the "Powered by Jetonomy" footer text.
email_logo_url	Logo shown at the top of notification and digest emails.

Tip: header_logo_url and logo_url are deliberately separate. Set header_logo_url for the on-page logo and logo_url for the share-card / fallback image - they are often different sizes and aspect ratios.

REST API

White Label exposes its settings under jetonomy/v1:

Method	Endpoint	Description
GET	/settings/white-label	Read the current white-label settings
PATCH	/settings/white-label	Save white-label settings

Both routes require manage_options. See the REST API reference for full payloads.

Upgrading From Older Versions

On Jetonomy 1.4.1 and newer every White Label setting applies on every surface - the header logo, footer text, email accent colour, email logos, the sidebar sign-in card, and the admin footer all rebrand on each render and send. On older versions the Branding settings saved but did not always take effect; update both the free and Pro plugins together so all branding applies.

What's Next?

Bring large language models into your community for smarter spam detection, auto-moderation, reply suggestions, and thread summaries.

AI Integration →

Bring large language models into your community - for smarter spam detection, auto-moderation, reply suggestions, and thread summaries - without sending data to a third party unless you want to.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• How the AI extension is organized (providers + features)
• Which AI providers Jetonomy supports, including self-hosted Ollama
• How to enable AI-powered spam detection, content moderation, reply suggestions, and thread summaries
• Where to monitor token usage and cost
• How to keep community content private by running models locally

Why AI Matters for Communities

Moderation is the single biggest burden on community owners. Every post and every reply is a potential spam attempt, abuse report, or duplicate question. At 50 topics a day, a human moderator can keep up. At 500, they cannot.

The Jetonomy Pro AI extension gives your community a language model that reads every new post and every new reply, flags the ones that need a human, and leaves the rest alone. It does not replace your moderators - it filters what they see so they can focus on judgment calls instead of the obvious cases.

Supported Providers

Jetonomy's AI layer is built on a pluggable adapter pattern. Four providers ship out of the box:

Provider	Hosted by	Best for
Ollama	You - runs on your own server	Privacy-sensitive communities, GDPR, full data control
OpenAI	OpenAI	Fastest time to value, best general quality
Anthropic	Anthropic (Claude)	High-quality moderation, long context windows
Custom	You	Self-hosted vLLM, LM Studio, or any OpenAI-compatible endpoint

You can register more than one provider and assign different features to different providers - for example, run moderation through Ollama locally while using OpenAI only for summaries of long threads.

Tip: If you already run Ollama on the same server as WordPress, the AI extension uses it over localhost - no network hop, no API key, no data leaves your machine.

Multi-Provider Fallback Chain

Every AI feature can be assigned a primary provider plus an optional fallback chain. If the primary provider errors mid-request (rate limit, timeout, 5xx), Jetonomy automatically retries the next provider in the chain before surfacing an error to the admin.

Typical setup: Ollama (primary) → OpenAI (fallback) → Anthropic (second fallback). You get privacy-first moderation with a safety net for the moments when the local model is restarting or overloaded.

The chain is configured per feature at Jetonomy → Settings → AI Integration → Advanced. Requests that succeed via the fallback chain are logged with a fallback_used flag so you can spot providers that are flapping.

Monthly Spend Caps

Every cloud provider (OpenAI, Anthropic, Custom) can be given a monthly spend cap in USD. Once usage crosses the cap in the current billing window, Jetonomy stops dispatching requests to that provider and surfaces a clear admin notice explaining what happened and when the cap resets.

Spend caps protect you from a runaway loop - a broken summary trigger, a spam wave that hits the reply-suggestion endpoint - draining your account. Self-hosted Ollama has no cap UI because it has no per-request cost.

Caps are evaluated against the usage log (wp_jt_pro_ai_usage), not the provider's invoice, so the cap reacts immediately. Expect a 2 - 3% variance versus your invoice at the end of the month because Jetonomy's estimate uses published token rates.

AI-Powered Features

Each feature can be toggled independently from Jetonomy → Settings → AI Integration.

How Review Runs

AI review never sits between a member and the publish button. Posts and replies appear the instant they are submitted, with zero AI latency, so posting always stays fast. A background job then reviews the new content in batches on a schedule.

• Batched and scheduled. A recurring job (jetonomy_pro_ai_batch_review) sweeps everything posted since its last run and classifies many items in a single model call - the spam and content-moderation checks share one pass. On a quiet site the sweep exits without touching the API at all.
• Runs every 5 minutes by default. The interval is filterable via jetonomy_pro_ai_review_interval (default 300 seconds, floored at 60 seconds).
• Trusted members are skipped. Staff and members at or above a trust level are never sent to the model. The exemption threshold is filterable via jetonomy_pro_ai_review_exempt_trust_level (default trust level 3).
• Throughput controls. Each sweep inspects up to jetonomy_pro_ai_review_batch_cap new posts and replies (default 60), classifying jetonomy_pro_ai_review_chunk_size items per model call (default 12). A failed model call is retried on the next cycle rather than dropped.

Both Spam Detection and Content Moderation below run together in this same background pass.

Spam Detection

Replaces the free plugin's pattern-based spam detector with a model-driven classifier. Posts and replies publish instantly - the AI is never in the posting path. The background reviewer then scores each new post and reply for spam probability and moves anything above the threshold to the moderation queue. Content below the threshold stays published as normal.

Works alongside Akismet and trust-level rate limits - AI spam detection is the third layer, not a replacement.

Content Moderation

Flags content that breaks rules you describe in plain English. You write a few sentences - "no political attacks, no personal insults, no harassment" - and the background reviewer reads each new post and reply against that policy.

Violations are sent to the moderation queue with a reason the model generated. Your human moderators make the final call, but they see a pre-filled explanation instead of a blank flag.

Moderation presets - Four tuned presets ship out of the box so you do not have to write a policy from scratch:

Preset	Tuned for
Community Forum	General discussion boards. Flags spam, harassment, obvious off-topic. Permissive on mild profanity and opinion-based disagreement.
Support Desk	Product and service support. Flags abusive language toward staff, solicitation, and off-topic promotion. Permissive on frustration.
Kids Safe	Under-13 communities. Aggressive filter - any profanity, sexual language, personal contact requests, or outside links flagged.
Academic	University and research communities. Flags plagiarism indicators, academic dishonesty keywords, and personal attacks. Permissive on technical debate.

Pick a preset as your starting point and customize from there. The preset fills the policy text field - you edit it - and the model uses your edited copy.

Reply Suggestions

When a member is composing a reply, Jetonomy can ask the model for a draft based on the topic context. The member can accept it, edit it, or ignore it. Draft replies are never sent without human approval.

Great for knowledge-base communities where most answers follow a pattern.

Thread Summaries

On long threads (30+ replies), Jetonomy can generate a short summary pinned at the top of the topic. New visitors read the summary instead of scrolling through every back-and-forth. Summaries regenerate when new replies meaningfully change the conversation.

Cached in the wp_jt_pro_ai_cache table so each summary is generated once per content state.

Enabling AI Integration

1. Go to Jetonomy → Extensions and enable AI.
2. Open Jetonomy → Settings → AI Integration.
3. Choose a provider. For Ollama, enter the base URL (usually http://localhost:11434) and the model name (for example, llama3.1:8b).
4. (Optional) Add a fallback provider and set a monthly spend cap at AI Integration → Advanced.
5. Turn on the individual features you want - Spam Detection, Content Moderation, Reply Suggestions, or Thread Summaries. Pick a Content Moderation preset if you enable moderation.
6. Save.

Each feature has its own Enable switch and an optional Provider Override, so you can, for example, run moderation locally on Ollama while sending summaries to OpenAI - see the per-feature toggles in the AI Integration settings tab above.

Usage Tracking and Cost

Every AI request is logged to the wp_jt_pro_ai_usage table with the model used, token counts, latency, and estimated cost.

AI Usage dashboard widget - A dedicated widget appears on the main Jetonomy admin dashboard as soon as at least one provider is connected. It shows at a glance:

• Requests today and this month
• Token usage by feature
• Estimated spend by provider (and percentage of the monthly cap consumed)
• Average response time
• Error rate and fallback-chain activations

A detailed breakdown lives at Jetonomy → Settings → AI Integration → Usage with per-day charts, per-feature filtering, and CSV export.

If a feature starts running hot (a new spam wave, an unexpected summary loop), you see it in the dashboard and can pause that feature without disabling the whole extension. The spend cap will also pause the provider automatically if the runaway is expensive enough to cross the cap.

Privacy and Self-Hosting

For communities that cannot send member content to a third-party API - legal, health, financial, enterprise internal - run Ollama on the same server. Jetonomy talks to the model over localhost only. No external network calls, no API keys, no data leaves your machine.

The wp_jt_pro_ai_log audit table records every model decision (feature, object, confidence, action taken) so you have a permanent record of what the AI did and why - useful for compliance reviews.

REST API

The AI extension registers three endpoints under jetonomy/v1:

Method	Endpoint	Description
GET	/ai/usage	Aggregated usage metrics for a date range
GET	/ai/usage/summary	Rolled-up usage summary for a date range
POST	/ai/suggest-reply	Request a reply suggestion - pass post_id in the JSON body

The two usage endpoints require an administrator (manage_options). /ai/suggest-reply requires any logged-in member and is rate-limited.

What's Next?

Give every Pro space its own SEO controls - custom meta titles, Open Graph images, schema, and sitemap rules.

SEO Pro →

Give every space its own meta titles, Open Graph images, Twitter Cards, schema markup, and sitemap rules - without touching your site-wide SEO plugin.

PRO - This feature requires Jetonomy Pro.

What You Will Learn

• Why community SEO is different from page/post SEO
• How to set per-space meta titles and descriptions
• How to control Open Graph and Twitter Card previews per space
• How Jetonomy outputs Schema.org structured data automatically
• How to include or exclude spaces from your sitemap
• How to customize robots directives and canonical URLs

Why Community SEO Is Different

Your posts and pages have one author, one publish date, and one body. A forum topic has dozens of authors, evolves over time, and the most recent reply is often the most important part. A Q&A thread is really a QAPage with an acceptedAnswer, not a blog post. A sitemap that treats every reply as a top-level URL pollutes your search index.

The free Jetonomy plugin already outputs baseline SEO - canonical URLs, Open Graph tags, Schema.org, and a sitemap provider for spaces and posts. SEO Pro is for when you need to override the defaults on a per-space basis, because different spaces have different audiences, different goals, and different search intent.

Per-Space Meta Title and Description

Every space gets a dedicated SEO tab in its settings panel. Inside that tab:

• Meta Title - defaults to the space name. Override for search engines only (the on-site title stays unchanged).
• Meta Description - defaults to the space description. Override with a keyword-rich summary written for search snippets.
• Meta Keywords - legacy field, not used by Google but some vertical engines still read it. Optional.

Both meta title and description support template tokens: {space_name}, {site_name}, {space_count}, {post_count}. For example, a meta title template of {space_name} - {post_count} discussions | {site_name} produces Python Help - 2,481 discussions | MyForum automatically.

Open Graph and Twitter Cards

SEO Pro lets you upload a custom Open Graph image per space - a 1200x630 image used when the space URL is shared on Facebook, LinkedIn, and Slack. It also lets you override:

• Open Graph title (defaults to meta title)
• Open Graph description (defaults to meta description)
• Twitter Card type (summary or summary_large_image)
• Twitter Card image

If you skip these fields, Jetonomy falls back to the meta title/description and uses the default OG image from your main settings.

Schema.org Structured Data

For every space and every post, Jetonomy Pro emits JSON-LD structured data:

• Space pages - DiscussionForumPosting with post count and date
• Topic pages (Forum) - DiscussionForumPosting with author, date, and answer count
• Topic pages (Q&A) - QAPage with acceptedAnswer (if marked) and suggestedAnswer entries
• Topic pages (Ideas) - CreativeWork with about (the idea)
• User profiles - Person with memberOf the space list
• Breadcrumbs - BreadcrumbList on every community page

You do not need to configure any of this. Enabling SEO Pro turns it on automatically. The free plugin emits a subset of these (basic DiscussionForumPosting and BreadcrumbList) - SEO Pro adds the richer types.

Sitemap Controls

Jetonomy core registers a sitemap provider for spaces and posts. SEO Pro adds:

• Include / exclude per space - mark a private support space as excluded from the sitemap with one click
• Priority per space - boost your flagship space above others in the sitemap XML
• Change frequency per space - hint at how often a space updates (always, hourly, daily, weekly, monthly)
• Maximum URLs per sitemap - split large sitemaps into chunks that search engines can crawl without timing out

All sitemap changes take effect on the next request - no flush needed.

Robots Directives and Canonical URLs

• Robots meta per space - set noindex, nofollow, noarchive, or any combination on a space-by-space basis. Useful for staff-only spaces that should not appear in search results.
• Custom canonical URL - override the default canonical URL on a space or topic. Useful when you syndicate content from an external blog and want Google to credit the original.
• robots.txt directives - add SEO Pro specific rules to your site's virtual robots.txt without touching a file.

Enabling SEO Pro

1. Go to Jetonomy → Extensions and enable SEO Pro.
2. Open any space in Jetonomy → Spaces.
3. Click the SEO tab inside the space settings panel.
4. Fill in the fields you want to override. Leave the rest blank to inherit the site defaults.
5. Save.

No site-wide settings page - SEO Pro is intentionally per-space, so you do not accidentally change defaults that other spaces depend on.

REST API

Method	Endpoint	Description
GET	/spaces/{id}/seo	Get the current SEO settings for a space
PATCH	/spaces/{id}/seo	Update the SEO settings for a space

Both endpoints require the manage_jetonomy capability or space-admin role.

Compatibility With Site-Wide SEO Plugins

SEO Pro does not replace Yoast, Rank Math, or All in One SEO. It handles the community area only - URLs under /community/ - and leaves your blog, pages, and WooCommerce products entirely alone. If a site-wide SEO plugin already writes og:title for a community URL, SEO Pro's tags take precedence on community pages.

What's Next?

Feature an important post at the top of every space across your whole community.

Site Announcements →