Skool Classroom: structure courses members can navigate
A useful course is more than a video folder: each page should make the next action clear.

Classroom is Skool's space for organising courses, guides, instructions and other community resources. Official documentation describes pages that can contain text and video, plus folders for grouping them. That flexibility supports many designs, but it does not decide the sequence for you. Our recommendation is to begin with the result a member should achieve, rather than building the structure around whichever files already happen to be available.
Decide what deserves a page
As an editorial rule, give a page to an action or explanation that makes sense on its own. A title such as Prepare your first proposal provides more direction than Video 3. Group pages into folders when they share a stage of the work, and avoid organisational layers that leave members guessing where to begin. Skool supports dragging pages into folders or adding pages directly inside a folder.
Combine explanation, resources and the next action
Official help documents resource links, files, transcripts and community posts pinned to a page. Use each element for a purpose: a file for doing the work, a link for further reference and a discussion for questions or progress. Transcripts make video content searchable within the group. Avoid attaching resources merely to make a lesson look substantial; an extra download should help someone complete the intended task or understand a genuine difficulty.
Worked example: a proposal-writing course
A consultant proposes three folders: Diagnosis, Draft and Review. Diagnosis contains a page for defining the problem and another for gathering information. Draft explains the proposal structure and supplies a template. Review offers a checklist and links to a discussion for questions. This is a design example, not a requirement that every course contain three folders or the same number of pages. The structure follows the work members need to complete.
Pre-publication checklist
- Identify the starting point and the course's intended outcome.
- Check that titles describe recognisable content or actions.
- Open links and files using the permissions intended for their audience.
- Review each page's Published state and save changes.
- Distinguish structural problems from Classroom tab visibility and course access.
Page publication and Classroom visibility are separate controls. Official help places the tab setting under Settings, Community and Tabs. If content appears missing, also check the page's publication state before reorganising the entire course or changing unrelated access settings.
Explore PowerUpSkool features to support your community operations.
ContinueSources and documentation
Frequently asked questions
Do all resources need to become videos?
No. Classroom supports text pages and resources. Our recommendation is to use video when showing or explaining something offers a real advantage.
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
What is Skool and how it works: the complete creator guide
Skool merges community, courses and gamification into one very simple interface. That simplicity is its greatest strength and its biggest limit.
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.
Skool course access: unlock rules and manual exceptions
Before granting an exception, identify the course rule and confirm which member needs access.
Skool points and levels: actual rules and useful rewards
Publishing more does not automatically earn points: likes received on your contributions are what count.