✓ Established interest groups
✓ Volunteer community teams
✓ Member access and moderator handovers
— Launching a first creator offer
— Course production or LMS migrations
— Agency software resale
— Guaranteed community growth
Define the categories locally
Write which routine actions a moderator may take and which concerns must be escalated. Use the community’s actual rules and provider terms. Do not make a volunteer improvise legal, medical or safeguarding advice from a generic software guide. If a situation involves immediate danger, the relevant emergency or specialist route takes priority over ordinary community administration.
Limit the information transferred
Send only the context required to the authorised recipient. Avoid copying sensitive reports into broad committee chats or public transition boards. Preserve necessary evidence according to applicable obligations and the provider’s process. This publication does not determine a legal retention period or instruct moderators to conduct investigations beyond their role.
Make ownership of the next step visible
Record who received the escalation, what acknowledgement was observed and what remains unresolved. Forwarding a message is not proof that the recipient accepted responsibility or resolved the case. Explain the member-facing next step without promising confidentiality or an outcome that the actual process cannot guarantee.
A fictional boundary
A moderator receives a complaint about access and also an allegation requiring an owner’s review. The access question follows the ordinary support route; the allegation is handled separately through the appropriate restricted process. The moderator does not combine both into a public troubleshooting post. Distinct routes help preserve privacy and prevent a routine software fix from being misrepresented as resolution of the broader concern.
Before you close this task
State the distinction between acknowledging a report and accepting responsibility for its resolution. If no appropriate recipient has accepted the next step, retain the issue as unresolved and follow the community’s legitimate escalation process. Avoid reassuring language that promises investigation, confidentiality or enforcement beyond what the responsible organisation can actually provide.
Where the safety evidence stops
This guide draws on Mighty Networks administration, Mighty privacy policy, Mighty terms of use. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.
Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Mighty Networks administration — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty privacy policy — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty terms of use — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28