Members and Roles

Members manage their own account details, while owners, admins, moderators, and billing managers help run a community. Give each person only the responsibility they need, and check the current permission screen before relying on a role for sensitive work.

Member account controls

Members can find help for passwords, email changes, logging out of all devices, notifications, Skool Chat, profile pictures, map location, multiple accounts, and connectivity issues.

During onboarding, show people only the controls that matter right away. Most members need to know where to manage notifications, how to find the rules, and how to ask for help.

Community roles

• The owner carries overall responsibility for the community.
• Skool publishes the boundaries. Owners and billing managers have access to everything, admins have access to everything except Billing settings, and moderators can approve or decline members, remove reported posts, delete comments, invite people, and run and record scheduled events, but cannot change Classroom or Calendar settings.
• Billing manager is not a narrow finance role; Skool describes it as essentially a co-owner, so give it only to a co-founder, partner, or head of accounting.

How to assign responsibility

1. List the recurring jobs in your community.
2. Separate community management, moderation, billing, and integrations.
3. Give each job a primary person and a backup.
4. Use Moderation And Anti Spam for rules, reports, and enforcement work.
5. Use Payouts And Billing and Payments And Billing for money-related responsibilities.
6. Use Zapier Integration and Admin Settings Reference for plugin and key ownership.
7. Review access when a person changes role or leaves the team.

Best practice

• Use the smallest role that safely supports the job.
• Keep billing and payout responsibilities separate from everyday moderation when possible.
• Do not share one person's login to avoid assigning the right role.
• Keep membership-question data limited to people who need it.
• Tell members how to contact an admin without exposing private staff details.

Pitfalls

• Role names do not prove every permission inside the current product.
• A plugin owner may also control data flowing into outside systems.
• Old team members can retain access if role reviews are skipped.
• Member search, bulk management, and export capabilities should not be assumed without checking the product.