Advanced Access
Content that opens when the member is ready for it.
Unlock on tags, levels, achievements, points, dates, cohort, purchase, or any combination of them. Access rules live in the CRM, which is why they can respond to anything the platform knows.
The learning lifecycle
Design
>
Sequence
>
Practice
>
Prove
Time-based drip is a blunt instrument
Releasing a module every Monday assumes every member moves at the same speed, which none of them do. The fast ones sit waiting and lose momentum. The slow ones fall behind and the backlog becomes a reason to stop. Access driven by demonstrated readiness fixes both, and because Gamplify runs access off CRM tags rather than an LMS setting, the same rule can read a purchase, a streak, an assessment result, or a coach sign-off.
Available now as custom development.
What you can gate on
Everything available to you.
Any of these combine with AND and OR, so one rule can serve several cases.
What they have done
Progress
- Previous course, module, lesson, or topic completed
- Quiz score above a threshold
- Percentage through a path
- Attendance at a required event
What they have earned
Gamification
- Level reached
- Specific achievement unlocked
- Points balance above a number
- Active streak of a given length
Who they are
Record
- Any CRM tag
- Membership type, tier, or role
- Team, cohort, or seat assignment
- Assessment result or profile type
- Any custom field value
What they bought
Commerce
- Specific product or course purchased
- Subscription active, lapsed, or within a grace window
- Lifetime value above a threshold
When
Time
- Fixed date or date window
- Days since enrollment, for cohort pacing
- Recurring windows for seasonal content
Not just courses
What can be gated
- Courses, modules, lessons, topics, and quizzes
- Downloads and content libraries
- Events, groups, and community areas
- Individual page blocks, so one page can differ per member
Worked example
One course page, three different
members
Same URL. Three experiences, decided by rules rather than by three separate pages.
Module 3: Advanced Practice
Access evaluated per member
Sequence
Dana: Level 4, module 2 complete, active streak
Full access. She sees the module, the workbook, and the live session invite.
Sequence
Marcus: module 2 complete, Level 2
Module opens, workbook stays locked with the requirement shown rather than hidden.
Sequence
Priya: enrolled yesterday
Module 3 is visible but locked, with the two steps that unlock it named explicitly.
Prove
Every lock states its own condition
A hidden lock is confusing. A visible one with a stated requirement is a goal.
Design
You maintained one page
Not three, and not a duplicate course per tier.
Recipes
Three you could build this afternoon.
Show the lock, do not hide the content
When
Only if
Then
Gate on readiness rather than the calendar
When
Only if
Then
Keep the history when access ends
When
Only if
Then
Before you build
Three things worth knowing.
Note
Gate less than you think. Every lock is a place a member can stop.
Note
Name the requirement on every lock. Locked with no explanation reads as broken.
Note
Because rules live on CRM tags, one tag change can move a member through several gates at once. Test that before it goes live.
The rest of LMS
Advanced Access is one of 5 parts.
Learner Journey
Advanced Access
Front End Faculty
Quiz Banks
Flash Cards
Put Advanced Access to work.
Tell us what you are trying to get members to do, and we will show you the Flow that does it.