A parent support group runs on a different kind of trust from a hobby forum. Members write about their children, their sleep, their money and their mental load. Some of them will only post if they are sure that the wrong person cannot read it. So the first job is not choosing features. It is deciding who can see what, and then making the software enforce that decision on every screen where a post could appear.
This guide walks through that setup using BuddyNext as the community engine and Jetonomy for question-and-answer threads, both running on the Reign theme. BuddyNext is free to install from the Wbcom store, with an optional paid Pro licence. Jetonomy is free, with an optional paid Pro licence. Where a step needs Pro, it is labelled. If you want the broader overview of what a parenting site can contain, our earlier parenting community post covers the general feature list. This one is about the narrower, harder problem: privacy, age groups and moderation.
A note on scope. Nothing here is legal, clinical or safeguarding advice, and the plugins do not make a site compliant with any regulation. Rules about children’s data, online services for minors and professional duties differ by country and by who you are. Check the rules that apply to you and to your professional body before you launch, and have someone qualified review your terms and your moderation policy.
Decide the privacy model before you build anything
BuddyNext gives you three layers of privacy. Pick on purpose at each layer, because changing them later means telling members the rules changed.
Layer one: the whole site
Under BuddyNext > Members > Privacy & Data there is a Private community setting called “Require login to view the community”. When it is on, a visitor who is not signed in is sent to your login page instead of seeing the feed, the member directory, spaces or any other community page. The login, registration, password reset and email verification screens stay reachable so a new person can still sign up.
For a parent group this is usually the right default. The same tab has an indexing control with three levels: Everything, Public posts only, or Nothing. Choose Nothing if you do not want any community page suggested to search engines. Members can also switch off search engine visibility for their own profile.
If you are unsure whether a fully private site suits you, our guide to private versus public communities lays out the trade-offs, including what you give up in discoverability.
Layer two: the space
Every BuddyNext space is Open, Private or Secret. The documentation spells out the difference:
| Type | Listed in directory | How people join | Who can read the feed |
|---|---|---|---|
| Open | Yes | Join instantly, or request if you switch on approval | Anyone, including non-members |
| Private | Yes | Request to join, owner or moderator approves | Members only |
| Secret | No | Invitation only, and the member must accept | Members only |
Two details matter for a parent group. First, a non-member can open the About tab of a private space and read its description, house rules and moderator list, but not the feed. That is useful: a parent can see who runs the space and what the rules are before asking in. Second, posts in a Private or Secret space never surface on the public Explore feed or on the author’s profile for people outside the space, whatever audience the individual post carries. Space privacy wins over post privacy.
A workable split is one Open welcome space for introductions, rules and announcements, and Private spaces for anything personal. Reserve Secret for the moderator team’s own room, because a Secret space leaves the directory and search for everyone who is not a member.
Layer three: the individual post
Members choose an audience each time they post: Public, Followers, Connections or Only me, plus Space members for anything posted inside a space. You can set the community default under BuddyNext > Engagement > Social > Activity Feed. For a closed group, set the default to something narrower than Public, so that a tired parent who forgets to choose does not broadcast a post. The setting applies to new posts only, not to posts already published.
Members also control their own profile. Under Settings > Privacy they can limit who sees their profile, who can follow them, who can send connection requests and who can mention them, set a private account, and leave the member directory.
Build age groups that parents can actually use
Parents rarely want one big room. A parent of a newborn and a parent of a fifteen-year-old have almost nothing to say to each other on a Tuesday night. Splitting the community by child age keeps threads relevant, and it keeps the moderator workload predictable.
One space per stage
Create a Space for each stage you want to support, and give each a category so members can browse them. BuddyNext draws its onboarding interest chips from your space categories, so the categories you create are also what a new member sees and ticks when they sign up. Those interests influence ranking in the For You feed and in people and space suggestions, though they do not hide anything.
Keep the first version small. Three or four stages are easier to staff than eight. You can always split a busy space later.
Member types for the parent’s main stage
BuddyNext member types give each member one label, which appears as a coloured badge on their profile and card and works as a directory filter. You can mark a type as self-selectable, so parents choose it themselves on their profile edit page.
Two settings turn this into onboarding:
- Tick Let members choose this type for themselves on each stage type.
- On the matching space, turn on Auto-join new members and use Limit auto-join to member types to restrict it to that type. Auto-join is an owner-only setting, and members can leave at any time.
One limit to plan for: a member has at most one type. A parent with a toddler and a teenager has to pick one, so treat the type as their main stage and let them join the second space by hand. Do not describe it to members as a full record of their family.
There is also a caution about what you ask for. A stage label like “Toddlers” is enough. You do not need children’s names, birth dates or photos to run an age-based group, and every extra field you collect is something you must protect and justify. If you add profile fields, use the registration setting that shows only the fields you choose at sign-up, and keep it to what the community needs.
Who joins which space
For each stage space, decide on the join method deliberately:
- A welcome space can be Open, or Open with Require approval to join, which keeps the space readable but turns each join into a request.
- Stage spaces that handle personal stories fit Private, so every join is approved.
- If you want to bring a whole cohort in at once, a space invite link can be set to expire after 1, 7 or 30 days, or never, and capped at 1, 10, 100 or unlimited uses. People who use the link join straight away, so keep that for groups you have already vetted. A link does not waive email verification, and a banned person can never use it.
You can also run the whole site as invite-only or admin-approval under BuddyNext > Members > Registration & Login. Invite-only suits a group run through a clinic, a school or a charity that already knows its members, because you can bulk-send invitations from a CSV of up to 500 rows per upload. Invitations are tied to the email address and expire after 7 days by default.
Make room for questions people are embarrassed to ask
A lot of parenting questions are private in a different way: nothing is secret, but the person asking does not want their name on it. Two Jetonomy features address this, and one is free.
Private topics (free). In any Jetonomy space, a signed-in member can tick a checkbox so that a topic is visible only to its author and to space moderators. Other members cannot see it in the listing, find it through search or open the address. It is a good fit for a parent who wants to ask a moderator something personal without starting a public thread. Jetonomy’s own documentation lists reports of harassment as one use, since naming a member in public can make things worse.
Anonymous posting (Pro). With Jetonomy Pro you can let members post topics and replies as “Anonymous”. It needs two switches: the extension turned on site-wide under Jetonomy > Extensions, and Allow anonymous posts ticked on each space where you want it. Other members see “Anonymous” with a neutral silhouette. The real author is still stored, which is what keeps moderation, rate limits and reputation working, and only site administrators can reveal an author, with every reveal written to the activity log. Space moderators cannot reveal authors.
Be honest with members about that last point. Anonymous means anonymous to other members, not to the people who run the site. Say so in the space description, and decide in advance who your administrators are and when a reveal is justified.
Which tool should hold the conversation? BuddyNext spaces suit chatty, ongoing support. Jetonomy suits the “how did you get your baby to take a bottle” questions that deserve a lasting answer. BuddyNext can add a Discussions tab to a space using Jetonomy, installed from Platform > Add-ons, so a stage space can have both a live feed and a searchable question board. Our comparison of forums, Q&A and ideas boards helps when you are choosing the format for each room.
Moderation for a group where mistakes hurt
A sensitive group needs a moderation plan before the first post, and it needs more people than you expect. The tools are mostly free in BuddyNext. The harder part is deciding how you will use them.
Roles and who sees what
BuddyNext has community-wide roles (member, moderator, admin) and separate space roles (owner, moderator, member). Space owners and moderators approve join requests, invite and remove people, and can see reports for their own space in the space’s Moderation tab. Community moderators see reports from every space but do not see inside a Private or Secret space they have not joined. That separation is helpful when a stage space has its own volunteer moderators.
Reports, auto-hide and the queue
Any member can report a post, comment, message or profile, choosing one of seven fixed reasons and optionally adding up to 500 characters of notes. The person reported is not told who reported them. Reports on the same item merge into one row, and a reported direct message hides its content in the queue, so moderators can act without reading a private exchange.
Under BuddyNext > Automation > Controls you tune the safeguards. The ones most relevant here:
| Setting | What it does | Default |
|---|---|---|
| Auto-hide after N reports | Content is hidden and put “Under review” once it reaches N reports; reports from accounts younger than 7 days do not count | 5 |
| New member review threshold | Posts from new members publish but are also sent to the queue until the member reaches the threshold | Off |
| Banned words | Whole-word match, reject on post; a trailing * catches variants; spaces can add their own list |
Empty |
| Blocked link domains | Posts linking to a listed domain are rejected | Empty |
| Queue alert threshold | Emails admins daily when unreviewed items exceed this number | 20 |
Turn on the new member threshold. A brand-new account posting in a parent group on day one is the pattern you most want a human to glance at. The post still publishes, but the report lands in the queue. If you need content held until a moderator approves it, note that BuddyNext’s pre-moderation engine has no admin toggle and is only switchable by a developer filter, so plan for reactive moderation unless you have a developer.
Proportionate responses
For a post that is not against the rules but may upset readers, BuddyNext lets a moderator add a content warning to a reported post. It then shows blurred behind a label, with a Show anyway button. The available labels are NSFW, Spoilers, Violence and Strong language, so it will not describe every sensitive topic a parent group meets. If you need a different label, use a post prefix in a Jetonomy space instead, or ask members to put a warning in the title.
For people, the ladder runs warn, strike, suspend. The default is a warning at 2 strikes and an automatic suspension at 5, with automatic permanent bans off. A suspension takes a reason and a length, and the member can appeal from their account status page. Reversing a strike lowers the count. A per-space ban removes someone from one space only and blocks rejoining, and it also stops them from commenting, reacting or voting in that space. Our moderation guide goes deeper on escalation ladders and moderator burnout, and the community guidelines template gives you wording to start from.
Member-side controls
Parents also protect themselves. Every member can block, mute or restrict another member from the profile menu. A block works in both directions and stops direct messages. Mute is silent. Restrict keeps the person’s comments visible only to them and to you. Direct messages run on WPMediaVerse, where you can set who may message whom and a minimum account age in days before a new account can send a message. A minimum age on messaging is worth setting, since cold messages from new accounts are a common way for spam to reach members.
Write rules that fit the subject
Technology enforces what you write down, so write the rules first. A parent group usually needs these specific rules, whatever your wording:
- Do not post children’s full names, schools or identifying photos. This is a community rule you choose to set, and it is general practice rather than a platform requirement.
- No medical or legal instruction from members. Share experience, and tell people to ask their own professional.
- No judging another family’s choices. State this in the welcome space in plain terms.
- Reports are confidential, and moderators will not discuss one member’s report with another.
- What happens to a post that breaks a rule, and how a member appeals.
Put the rules in each space’s house rules field, which shows on the About tab even to people who have not joined a Private space. Post an announcement for the welcome message: a BuddyNext announcement pins to the top of every member’s home feed until the member dismisses it, and you can set it to expire.
A crisis and escalation note
Support groups sometimes meet people in real distress. This is general practice, not a clinical protocol, and the plugins do not detect risk or contact anyone for you.
- Decide before launch who on your team reads reports about someone at risk, and how quickly.
- Pin a post, and put in your house rules, a short note that the group is not an emergency service, with the emergency number and a recognised local support line for your country.
- Give moderators a short written script for the first reply, so no one improvises under pressure.
- Keep a private moderator space, Secret in BuddyNext, for handing a case between moderators, and record who handled what in the moderation log.
- Review your plan with a qualified professional who works with the families you serve.
Pre-launch checklist
| Step | Where | Free or Pro |
|---|---|---|
| Require login to view the community | BuddyNext > Members > Privacy & Data | Free |
| Set indexing to Nothing | Same tab | Free |
| Registration mode and email verification | BuddyNext > Members > Registration & Login | Free |
| Default post audience narrower than Public | BuddyNext > Engagement > Social > Activity Feed | Free |
| One Private space per age stage, with house rules | Space settings | Free |
| Self-selectable stage member types and auto-join | Member Types, then space Permissions | Free |
| Moderation safeguards and strike thresholds | BuddyNext > Automation > Controls | Free |
| Private topics in Jetonomy | Composer checkbox | Free |
| Anonymous posting in chosen spaces | Jetonomy > Extensions, then space Anonymous tab | Pro |
| Pinned crisis and rules post | Announcement | Free |
| Minimum account age for messaging | WPMediaVerse messages settings | Companion plugin setting |
The theme’s job is smaller than the plugins’ but worth checking. Reign handles the presentation of the BuddyNext and Jetonomy pages. Test the sign-up flow, a join request and a report on a phone before you invite anyone, since most parents will use one. The plugins overview and the free versus Pro comparison list exactly what each tier includes.
What the plugins do not do
Be plain with yourself and your members about the limits. The plugins offer privacy controls, data export and account deletion tools for members, and a cookie notice you can switch on. They do not give you age verification, parental consent flows, a legal basis for processing children’s data, or a safeguarding process. If you serve children directly, or collect information about them, those obligations sit with you. Get advice that fits your country and your profession, and keep your community’s collection of personal data as small as you can.
Frequently asked questions
Can I make the whole parenting community invisible to search engines?
Yes. Turn on “Require login to view the community” so logged-out visitors see only the login and sign-up screens, and set the search engine indexing control to Nothing. Members can also hide their own profile from search engines.
Can parents post without their name showing?
Only with Jetonomy Pro. Anonymous posting must be switched on in Jetonomy Extensions and then allowed on each space. Other members see “Anonymous”, but site administrators can reveal the real author, and each reveal is logged. In free Jetonomy, a private topic lets a member ask something that only they and the moderators can see.
How do I stop strangers posting in a group of parents?
Combine measures. Use invite-only or admin-approval registration, turn on email verification, make stage spaces Private so each join is approved, set the new member review threshold, and set a minimum account age for direct messages. No single setting is enough on its own.
Do the plugins make my group compliant with child privacy law?
No. They provide controls, such as private spaces, member data export and deletion, and consent notices, but compliance depends on your location, your audience and how you collect and use data. Check the rules that apply to you and to your professional body, and get qualified advice.
What should I do when a member posts something that suggests they are in danger?
Follow the plan you made before launch: a trained person reads it quickly, replies with your prepared message, and points to emergency and support services in the member’s country. The software will not detect or escalate this for you, so the process has to be human and written down.
How many moderators does a parent group need?
There is no fixed number. Give each stage space an owner and at least one moderator, so a single absence does not leave a Private space unattended, and keep a separate team for site-wide reports. Review the queue on a schedule, and use the queue alert threshold so a backlog reaches you by email.