Admin Settings Reference

Skool divides settings between the people who run a community and the members who use it. Start with the area you want to change, then make sure the right person owns the setting before you touch it.

What it covers

• Admin settings cover payments, billing, roles, community structure, Classroom, Calendar, leaderboards, Discovery, plugins, and affiliates.
• Member account settings cover profile details, password, email, device sessions, notifications, chat, location, and multiple accounts.
• Community settings are where you look for categories, rules, and moderation.
• Plugin settings include Membership Questions, Auto DM, and the Zapier connection.
• Admin Settings Reference is a practical map, not a substitute for checking the current screen in your own group.

How to use the settings map

1. Name the outcome you want, such as changing a role, adding a rule, or connecting Zapier.
2. Open the matching settings area instead of searching through unrelated menus.
3. Confirm whether the owner, an admin, a moderator, or a billing manager should handle it.
4. Record who owns any plugin or automation, but never record the secret key itself.
5. Test changes that affect member access, messages, payments, or course unlocks before relying on them.

Use Members And Roles for responsibility questions, Moderation And Anti Spam for safety settings, and Webhooks And API Keys for integrations. Membership-question automations also need the correct group URL slug, which is explained in Membership Questions To CRM.

Best practice

• Keep member account controls separate from group administration.
• Give each important setting one clear owner and one backup.
• Review role access before giving someone control of plugins, billing, or moderation.
• Keep rules, reporting, and chat safety easy for members to find.
• Store a note that a group has a Zapier key, but store the key only in an approved secret manager.
• Revisit settings after a plan change or a major change to your community structure.

Pitfalls

• A Help Center category name does not tell you every permission available inside the product.
• Owner, admin, moderator, and billing manager responsibilities should not be treated as interchangeable.
• Refreshing a Zapier key can break existing Zaps until they are rebuilt.
• Auto DM and other automations can create a poor member experience when nobody owns their review.
• Skool has no public API. Use the documented Zapier and webhook routes for supported integrations.