Skool Book

Skool Feature Map

Skool brings community, courses, events, payments, discovery, gamification, chat, and mobile access into one platform. For a community owner, the useful question is not how many features exist, but how they support a simple member journey.

As of September 2026, Skool has also shipped freemium signup, trial controls, temporary closure, an interface in 11 languages, member reviews on every paid community with a report button and moderation, automatically generated closed captions in English for uploaded videos that have sound, a faster payout system rolling out to most countries, and a bid slider for Growth Boost. Payout timing and public review visibility are still settling, so check the current screens for those two.

The core areas

  • Community is the social home for posts, comments, rules, and moderation.
  • Classroom holds courses, access rules, unlocks, drip content, and video.
  • Calendar holds events, Skool Call, and Go Live.
  • Gamification uses points, levels, and leaderboards.
  • Discovery helps people find groups and uses growth, activity, and retention signals.
  • Payments and affiliates support paid memberships, course purchases, payouts, billing, and referrals.
  • Accounts and chat cover profiles, notifications, credentials, and member communication settings.
  • Mobile access lets members use the platform away from a desktop.

How the pieces fit

A clear About page helps the right person decide whether to join. Community and onboarding help that person participate. Classroom and Calendar give them structured value and reasons to return. Payments, affiliates, and Growth Boost support monetization and acquisition around that experience.

Best practice

  • Start with the member journey, then add only the features that support it.
  • When you need the exact current terms, Skool's own product pages are the place to look.
  • Discovery, Games, pricing, fees, and payout rules change from time to time, so treat those pages as a snapshot.
  • Treat third-party product descriptions as context, not as the final authority.
  • Follow Community Classroom And Calendar and the linked feature notes when you need detail.

Pitfalls

  • A feature list can make a simple community feel more complicated than it is.
  • Category pages do not explain every setting or limit.
  • A product demonstration does not replace current billing, policy, or contractual information.
  • Skool has not published every internal ranking or distribution weight.

See also

Read this page in the interactive book