Skool moderator permissions: what to delegate and what to retain
The right role depends on the task. Managing conversations does not require full access to group settings.

Making someone a moderator is a permissions decision, not simply an informal recognition of their contribution. Before assigning the role, list the actual tasks: reviewing applications, handling reported content, deleting comments or running sessions. Compare that list with the official permissions. Our recommendation is to grant the least extensive role that safely supports the intended work rather than using administrator access as a convenient default.
Differences that affect daily work
| Role | Documented scope |
|---|---|
| Owner | Access to everything in the group. |
| Billing Manager | Full access, including billing. |
| Administrator | Access to everything except billing settings. |
| Moderator | Admissions, reported content, comments and invitations; no Classroom or Calendar settings. |
Official help specifies that moderators can approve or decline members, remove reported posts, delete comments and invite people. They can also run scheduled events and record calls, although they cannot access Classroom or Calendar settings. This distinction matters: helping deliver a session does not mean being able to configure the calendar or reorganise courses. Define responsibilities around those boundaries rather than assuming every team role has similar access.
Worked example: support during a workshop
A community brings in Elena to review applications, moderate comments and run an already scheduled workshop. The moderator role matches those documented tasks. If she also needs to create courses or change events, the owner must decide whether to expand her role or retain those actions with an administrator. Sharing an account is not a sensible workaround for that decision: each collaborator should work under their own identity.
Delegation checklist
- Document permitted tasks and situations requiring escalation.
- Define criteria for accepting members and handling reported content.
- Explain that inviting people can affect access, not merely send a notification.
- Agree who changes courses, events and group configuration.
- Review the role when responsibilities change or the collaboration ends.
To change a role, official guidance says to locate the person in Members and open Membership settings. We recommend pairing the change with a short internal procedure covering what to review, what to record and whom to notify. Technical permissions do not replace a consistent moderation policy, nor do they explain when a sensitive decision should be escalated.
Explore PowerUpSkool features to support your community operations.
ContinueSources and documentation
Frequently asked questions
Can a moderator change course settings?
Not under the documented role scope: moderators do not access Classroom settings. Assign that change to an authorised administrator.
Turn this guide into work done in your community
PowerUpSkool reads your Skool community and shows you daily who is going quiet, which threads need replies and what message to send. Free to start; Pro with a 15-day trial.
Keep reading
How to create a Skool community step by step (and keep it alive)
Setting the community up takes an afternoon. Keeping it alive after three months depends on decisions made before you open it.
How to find the unanswered threads in your Skool community
A thread with zero comments tells a new member that nobody answers here. That's the most expensive message they can receive.
Skool points and levels: actual rules and useful rewards
Publishing more does not automatically earn points: likes received on your contributions are what count.
Skool membership questions: what to ask and how to review answers
Entry questions work best when each answer changes an admission or onboarding decision.