Loyalty is not a spike. A spike is weather: a launch, a season, a press hit, a Discord raid. Loyalty is the person who still answers a stranger in month eleven, who uses their own name when they disagree with staff, and who earned the right to post a link because they stopped looking like a spammer.
This is an identity / habit / progression article. It is not what to do when the hype fades — that piece owns cadence after a cliff, archive-versus-delete, and the empty-node reflex. It is not reward design — status versus access versus a shop you should postpone. It is not how to grow DAU. Those articles still apply. Stay here for the three things that make a member stay as themselves: a human identity in the room, a Tuesday habit, and a ladder that grants power slowly.
XenForo community practice is specific where it exists and silent where it does not. It is sharp on do not post casually as Admin and on user group promotions as the way you grow an Established member. It does not document a loyalty score, a “healthy” return rate, or a 90-day campaign. Discourse already shipped a ladder as trust levels. Treat everything below that is not one of those facts as operational practice — the kind you write on a staff page and revise after the first person asks why their links still hold.
Three parts, in order
Write the job before you name a rank.
| Part | What the member feels | What you actually do | What it is not |
|---|---|---|---|
| Identity | “I am a person here, not a ticket.” | Personal accounts. Staff without the nuclear badge when they are being members. Names that persist. | A display banner you sold in a shop |
| Habit | “I know where Tuesday happens.” | One or two rooms they belong to. A reason to open the site that is not a ping. | Another event, another empty child node |
| Progression | “The software noticed I stopped being new.” | Promotions that grant capability (links, conversations, less friction). Reversible if they go quiet. | Irreversible medals, points, a second currency |
If you skip identity, veterans perform for the badge and newcomers lurk. If you skip habit, promotions decorate ghosts. If you skip progression, everyone stays in the Registered sandbox until they leave, or you unlock everything on day one and the spam arrives with the regulars.
The onboarding catalog is the door. The 30-day calendar is the first month. Loyalty is what those two were for.
Identity: the Admin account is not a person
Community consensus on large XenForo boards is sharper than the manual. The root Admin account is a system actor: upgrade notes, structured warnings, the rare announcement that must be unmistakably official. It is not a joke account. It is not a debate account. When the badge that can suspend you is also posting memes in Off-topic, people stop disagreeing. They also stop believing that “Admin” is a human they could become.
Staff post as themselves, without the nuclear badge, when they are being members. Official warnings still go out from a staff identity the queue can search. The moderation-team article owns hiring and shifts. The large-queue article already said the same sentence about Admin. This article is why it is a loyalty rule, not only a safety rule.
Members copy what they see.
- If the only voice that gets answered is a staff badge, they will wait to be answered by a badge.
- If staff never lose an argument because the name is Admin, regulars will not invest in being right. They will invest in being loud or in leaving.
- If every “welcome” comes from Admin, the welcome is a system message. System messages do not create peers.
Practical split:
| Actor | Use it for | Never use it for |
|---|---|---|
| Admin (root) | Announcements that must be official, upgrades, legal/safety notices, the warning that is on the record | Jokes, takes, “just chatting,” winning a thread, first replies to new members |
| Staff personal account (Moderating / Administrative as secondary, Registered as primary) | Being a member. Mentoring. Disagreeing. The Tuesday reply | Silent bans from a meme account |
| Unbadged personal account (some large boards keep one) | Proof that the humans are still humans | Sockpuppeting a fight you started with the badge |
Official XenForo recommendation, again: every human — including staff — keeps Registered as primary. Moderating and Administrative are secondary. That is so the next add-on has one baseline, and so the public profile is a person with extra groups, not a different species.
Community sources also name Moderator Panel by Andrew and a Protected Users list so a junior moderator cannot ban an admin profile. That is an add-on, not a requirement. The stock version of the same idea: do not hand global ban permission to node mods, and do not leave Admin logged in on a shared machine.
Discourse’s version of the same identity rule is quieter: trust levels are on the person, not on a second “Admin” persona you use for jokes. TL4 is a manual inner circle in some rooms, not an auto-prize. Staff still reply as themselves. The nuclear tools sit on the same account, which is why you do not use them to win.
Names, avatars, and the profile that stays
Loyalty attaches to a recognisable person. That is not a theme setting. It is a few operational choices:
- Do not recycle display names so a new account can impersonate a regular who left. If the product lets you reserve or lock a name after a leave, use that. If it does not, write the social rule and enforce it.
- Custom fields that are actually identity — region, platform, “I work on X” — belong on the profile, not in a new node. The user-fields article owns the ACP. Here the job is: ask for things that help a stranger trust a reply, not for a second biography.
- Signature flex and purchased name colours are reward design. They do not make anyone stay. They make the room look like a shop.
A member who has been “the person who answers PostgreSQL questions” for two years is loyal. A member who has a gold banner and no Tuesday habit is decorated.
Habit: belonging is narrower than the tree
People do not become loyal to a forum index. They become loyal to one or two rooms they already understand, and to a small set of other humans in those rooms.
That is why the taxonomy article refuses empty shelves and why the return-loop article refuses a scavenger hunt. Loyalty work starts after those two are honest:
- A room the member already belongs to. Not twelve rooms they might belong to.
- A reason to open the site that is not “maybe someone replied to me.” What’s New, Latest, a watched list — pick one primary.
- Other people who would notice if they vanished. Not a staff dashboard. Peers.
You cannot buy (3). You can stop making (1) and (2) impossible.
Operational habits that create (3) without becoming the hype article:
- Staff reply as people in the living rooms. First useful reply to a new member should usually be a personal account, not Admin. The onboarding methods catalog already said welcome PM versus welcome thread. Loyalty is the second reply, a week later, from someone who is not onboarding them.
- Do not steal every interesting thread into a staff voice. If a regular started the useful answer, let them keep the social credit. Promotions and trust levels exist so that credit becomes capability.
- Keep the Tuesday slot small. One weekly thread that is allowed to be routine — “what did you ship,” “weekend report,” “unanswered from this week” — is habit. A new campaign every Monday is hype. When you are tempted to invent a campaign because the graph dipped, read the fade piece instead of this one.
- Watch list over spray. Teach members to watch the one room they care about. A board that mails everything trains people to mute everything.
Measure belonging with your own baseline, not with a number this article will not invent:
- Second session in seven days (that is still onboarding).
- A reply in month two in a room they posted in during month one (that is habit starting).
- A reply to someone they do not already know in month four (that is the loyalty you actually want).
If month four is only staff talking to regulars who already know each other, you have a club. Clubs can be loyal. They are not a community that will survive the next season unless you decide that is the product.
Progression: grant capability, not costume
This is the part people confuse with rewards. A trophy that says “one year” is status. A shop colour is economy. Progression is access: the software trusts you with a verb it did not trust you with last month.
XenForo’s stock tool for that verb is user group promotions. Official docs: they run on a schedule (hourly in community/admin practice), they look at criteria, they add a group, and they take the group back when the criteria fail. That reversibility is the point. A promotion is not a medal. It is a currently-true statement.
Community practice for a healthy ladder — the one the notebook actually names:
- Registered stays primary. Always. Promotions add secondary groups.
- Hold dangerous verbs at the door. Typical holds on Registered: Start conversations and posting external links (and often images, depending on your spam load). New accounts look like spam because spam is new accounts.
- Grant those verbs on Established (or whatever you name the group) when the account has been around, has posted, and is recently active.
- Let the promotion revoke. If they vanish for months, they lose the extra verbs until they are around again. That is not a punishment. That is how you stop a dormant account becoming a hijack vector with full conversation rights.
Do not invent thresholds in a tutorial. Use criteria you can defend on a staff page: a minimum number of posts, a minimum number of days registered, recently active so the hourly job does not promote ghosts. The groups-at-scale article owns Analyze, batch update, and the Never traps. This article owns the story those groups tell: you start in a sandbox, you become someone the room can hear.
The promotion, as a sequence (not as a number)
Official XenForo promotions live under Groups & permissions → User group promotions. Community and official practice agree on the shape even when they do not publish your numbers:
- Create the Established group (or your name). It is a secondary group. It is not a new primary. Give it the verbs you held at the door: Start conversations, permission to post links, and only then any extra you actually need.
- On Registered, leave those verbs off (or revoke them there). Do not use Never on Registered to fake a hold. Never is for a discipline group. A hold you want promotions to lift must be a No/unset that Established can Yes.
- Add a promotion: user is in Registered, is not already in a group that should skip this (staff, banned, validating), meets the days/posts/activity criteria you wrote down, recently active so the hourly pass ignores ghosts.
- Analyze a test account that should match and one that should not. Groups & permissions → Analyze permissions. If the test account can start a conversation from day one, the hold is not real.
- Wait one hourly pass on staging. Promotions are not instant. Do not “batch update” fifty people into Established to celebrate launch. That is how you skip the ladder for friends with extra steps.
Write the criteria on the same help page as the hold. “You can post links after the board has seen you around” is a loyalty sentence. “Error: you cannot use that BB code” is a bug report.
A worked shape (names are yours; the verbs are the practice):
| Group | How you get it | What it adds | Reversible? |
|---|---|---|---|
| Registered | Confirmed email | Read, post in public rooms, no conversations, links held | It is the baseline |
| Validating (optional) | Manual or queue | Same as Registered, posts go to approval | Yes — you remove it |
| Established | Promotion: days + posts + recently active | Start conversations, post links, maybe skip some approval | Yes — promotion drops it |
| Regular / Trusted (optional, later) | Promotion or manual | Less rate-limit friction, maybe a private “workshop” node | Prefer reversible |
| Moderating | A human hired you | Queue tools | Yes — you can unstaff someone |
Do not add a cosmetic group for every year. That is the ranks article. Do not add a paid lounge until the free ladder already produces people you would hire. Do not use Never on Registered to fake a ladder; Never is for discipline.
Discourse already has the ladder
Discourse trust levels are progression. TL0 is a sandbox (official: 1 image per post via newuser max embedded media; chat rate 20/30s). TL1 and up relax that (chat 40/30s; mods unlimited). TL3 can create tags by default (create tag allowed groups). TL3 is also the default for edit_all_topic_groups. TL4 is staff-adjacent in many rooms and should stay a manual decision.
Do not install a second ladder on top of trust levels because a XenForo muscle memory said you need “Established.” If you need a private workshop, use a group and a category wall. If you need a medal, you are back in reward design. The Discourse moderation / TL article owns the knobs. Loyalty here is: let the default ladder do the work, and do not let staff skip it for friends.
Skipping the ladder for friends is how loyalty dies in public. Everyone can see who got links on day one.
What staff identity teaches the room
Progression only works if the people at the top still look like members.
- Answer with the personal account. Then, if a warning is required, use the staff process. Mixing the two in one post — joke, then threat — is how you get a room that never jokes.
- Lose in public sometimes. A staff member who can say “I was wrong” in their own name is a loyalty engine. Admin cannot do that without making the site look wrong.
- Do not hoard the useful replies. If a regular wrote the canonical answer, link it, prefix it, feature it. That is how you mint the next Established without a ceremony.
- Promotions are silent by default. A banner that flashes “you are Established” every time someone hits a post count is a slot machine. A one-time notice plus the sudden ability to PM is enough. The software should feel like it noticed, not like it wants a round of applause.
The mod team piece is where you decide who holds the queue. Loyalty is what the rest of the membership sees of those people.
Onboarding is the first loyalty week
A loyal member was once a new account you did not scare.
Connect the door to the ladder so they are the same story:
- First session. One room, one first question, one human reply. Catalog of methods: onboarding. Calendar: 30 days.
- Holds they can understand. “New accounts cannot post links until they have been around” is a sentence you can put on the rules page. “Your post disappeared” is not.
- A visible next verb. They should know what Established (or TL1) will let them do. Capability is motivating. A mystery rank is not.
- No Admin welcome wall. A single welcome thread that regulars are allowed to own will outlive a hundred Admin PMs.
If week one is a quiz, a forced Discord join, and a banner shop, you selected for people who like quizzes, Discord, and shops. You did not select for people who will answer a stranger in month eleven.
What not to build (so this stays loyalty)
| Temptation | Why it feels like loyalty | What it actually is | Where it belongs |
|---|---|---|---|
| Points, credits, a name-colour shop | “They keep coming back to spend” | An economy. It trains shopping | Rewards, XF shop |
| A new rank every 50 posts | “They have a goal” | Costume. Goals without new verbs get ignored or farmed | Ranks ACP |
| A launch campaign every dip | “Energy” | Weather. You will teach people to wait for weather | Hype fades |
| More nodes for “their” topic | “They have a home” | Empty shelves. Homes are people | Taxonomy |
| Staff posting as Admin so it “looks official” | Authority | A room with one voice | This article, every week |
If nobody would change a Tuesday habit to earn the thing, it is not progression. If they would change a Tuesday habit only to buy the thing, it is not loyalty.
A 90-day loyalty loop you can staff
This is operational practice, not a notebook ritual. Adjust the days; keep the order.
Days 1–7 — identity and a hold.
Confirm email. Registered is primary. Links and conversations held. First reply from a personal staff or regular account. No Admin jokes. One room, not a tour of the tree.
Days 8–30 — habit slot.
A second session that is not a notification. Watch the room they posted in. Staff check unanswered in that room, not the whole site. Promotion criteria are visible on a help page so the hold does not feel like a bug.
Days 31–60 — first promotion window.
Hourly promotions can start adding Established for people who met days + posts + recently active. They may start conversations. They may post a link. Send at most one notice. Do not throw a party in Announcements.
Days 61–90 — peer test.
Look at who replied to a stranger. Those people are your next mentors and your next moderator candidates. Do not badge them yet. Ask them, on their personal account, whether they want more queue. Hiring is the team article. Noticing them is loyalty.
Every month after.
Revoke is allowed. Quiet accounts lose extra verbs. Staff still post as people. Empty shelves still get merged. No new costume rank because the graph was flat.
If you run Discourse, map the same loop onto TL0 → TL1 → TL2 and a manual look at who should be TL3. Do not auto-TL3 people you would not let recategorise the board.
What a loyal Tuesday actually looks like
Abstract “habit” is how this article becomes a poster. A loyal Tuesday is smaller:
- A regular opens What’s New or Latest, not the whole tree.
- They answer one stranger in the room they already belong to. Not a manifesto. A reply.
- They do not wait to see whether Admin will handle it.
- Staff, if they are on, reply in their own name or stay out because the regular already did the job.
If your board cannot describe that Tuesday without a campaign calendar, you do not have a loyalty problem yet. You have an empty-room problem or a hype problem. Fix those first. Then the Tuesday is allowed to be boring. Boring Tuesdays are the product.
Platform notes (short, so the story stays the story)
XenForo. Promotions: Groups & permissions → User group promotions. Criteria include the recently-active style checks the scale article already walked. Trophies are irreversible; do not use them as the ladder. Notices can explain the hold once. The root Admin account stays a system actor.
Discourse. Trust levels are the ladder. Watched words and the review queue are enforcement, not progression. Site Feedback is where people stay loyal to the product by complaining in-bounds. Do not add a parallel “Veteran” group that duplicates TL3.
Either. Private staff rooms are for staff. Loyalty happens in public, in a human name, in a room that still moves on a Tuesday.
A staff-identity audit (one afternoon)
Once a quarter, or after you hire someone, walk the public site as a stranger would:
- Open the last twenty posts in the living rooms. How many are from Admin? If the answer is more than “the announcements,” you have an identity leak.
- Open each staff profile. Is Registered still primary? Is the nuclear group a secondary? If someone has been “primary Admin” since 2019, fix the account before you write another welcome.
- Search the warning log. Do official warnings come from a staff identity you can filter, or from whichever personal account was angry?
- Read the last welcome. If it is an Admin PM with a shop link, rewrite it as a human reply in the room.
- List ten regulars you would notice if they vanished. If you cannot, you do not have a loyalty system. You have a broadcast.
None of those steps are in the official manual. They are how you find out whether the ladder and the badge rule survived contact with a busy month.
Checklist
- Root Admin (or the equivalent system account) does not post casually.
- Every human, including staff, has a personal identity with Registered (or the default member group) as primary.
- New accounts have holds you can explain in one sentence (conversations, external links).
- A promotion (or trust level) grants those verbs and can take them back.
- Staff first-replies to new members are not from the nuclear badge.
- There is a Tuesday habit that is not a campaign.
- You can name ten people who would notice if a regular vanished — without opening the ACP.
- You have not installed a shop to simulate any of the above.
Takeaways
- Long-term loyalty is identity + habit + progression. Costume and campaigns are other articles.
- The Admin account is not a person. Staff earn trust in their own name, without the badge that can suspend you.
- Habit is one or two rooms and a reason to open the site that is not a ping. Empty shelves and launch weather work against that.
- Progression is capability: XenForo promotions (revoke Start conversations / links on Registered, grant on Established, let them drop) or Discourse trust levels. Reversible beats a medal.
- If a tool does not change who they are in the room, what they do on a Tuesday, or what the software lets them do, it is not a loyalty tool.
The members you want in year three are already on the board, posting under their own names, waiting to see whether the humans in charge will do the same.