Skool course access: unlock rules and manual exceptions
Before granting an exception, identify the course rule and confirm which member needs access.

Belonging to a Skool community does not mean someone can access every course in it. Diagnosis starts with the course configuration and the member's identity, not with changing group-wide settings. Our recommendation is to separate three questions: whether the person belongs to the group, whether the course is available and whether they meet its specific access condition. Each question points to a different possible solution.
Identify the rule before intervening
| Configuration | Documented behaviour |
|---|---|
| Open | Accessible to all members. |
| Level Unlock | Access at the configured level; supports manual grants. |
| Buy Now or Private | Supports granting and revoking individual access. |
| Time Unlock | Unlocks automatically after the configured number of days. |
Official guidance allows manual course access for Level Unlock, Buy Now and Private courses. It does not describe the same exception as the solution for Time Unlock courses, so avoid promising that behaviour. For level-locked courses, remember that an administrator's view is not representative: administrators have access to all courses and do not see the lock in the same way an ordinary member does. Seeing it yourself is not sufficient confirmation.
How to grant an individual exception
Open Members, find the person and enter Membership settings. Under Courses, select the course you want to enable. The documentation says the member will have access to the courses checked in that window, and describes Remove access for revoking a grant. Review every selection before confirming: an exception for one specific resource should not accidentally become access to several unrelated courses or a broader entitlement than intended.
Worked example: migrating an existing learner
An academy moves Irene from another platform. She is already entitled to a course configured as Buy Now in Skool. After checking her identity and entitlement, the administrator grants only that course through her member settings. As an operational recommendation, the team records the reason and asks Irene to confirm she can open it. It does not change the course to Open, because that would alter access for the entire group.
Access checklist
- Confirm the exact member, account and course.
- Identify the access rule before changing it.
- Check whether an individual exception is appropriate.
- Review every selected course in the access window.
- Record the reason and verify the result with the recipient.
Explore PowerUpSkool features to support your community operations.
ContinueSources and documentation
Frequently asked questions
Can I revoke manually granted access?
The guide documents Remove access for supported types. Also review the course's general rule: removing an exception and changing its configuration are different actions.
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 Calendar: schedule events without timezone confusion
An event time needs a full date and timezone, especially around seasonal clock changes.
Skool Classroom: structure courses members can navigate
A useful course is more than a video folder: each page should make the next action clear.