For a short, self-paced course, use Full access when lesson order is guidance. Consider Drip content only when later lessons need to stay unavailable for a clear reason. You can recommend a learning sequence without putting a timer on it.
This decision is about when an enrolled learner can open a lesson—not which course they bought.
What the two settings change
Systeme.io’s access-type guide says Full access opens all modules and lectures immediately and ignores lecture delays. Drip content releases material progressively using configured delays. Partial access selects modules; partial access with drip combines module selection and gradual release.
Keep this choice simple: “Start with Lesson 1” is a recommendation; “Lesson 2 is unavailable until later” is a restriction. A timer does not establish that someone understood the previous lesson.
Give every lock a job
Example: a short writing course asks learners to draft an introduction, then revise it. If they can revise whenever ready, show the order and leave both lessons available. If your course deliberately includes a practice interval, explain what learners should do during that interval before adding a timed release.
Check whether a locked lesson contains a reference file learners need earlier. Move the needed resource into their available path. For words that distinguish core work from extra practice, use the required, optional and reference labels.
Verify timing before you promise a date
The official guide describes delays after viewing a previous lecture, while a later example discusses elapsed time from enrollment. We cannot resolve that timing basis from the text alone. Confirm the trigger and release behavior in your course or with support before promising an exact date.
Systeme.io also documents a separate per-lecture availability email. Check the notification and the lesson opening independently; receiving a message does not prove access works.
Copy a release decision note
Why a later lesson must wait: [reason, or no restriction needed]
Chosen access: [Full / Drip; record selected modules separately if relevant]
First entry: [what the test learner can actually open]
Release condition: [confirmed trigger and delay, or unverified]
Later check: [time, expected availability, actual result]
Notification: [configured / received / unverified]
Next action: [fix, ask support, or keep the suggested route]
Use an authorized test account. Record only what you observed; do not fill in future releases as passed. If a course is already selling, assess existing learners before changing its access mode or delays.
If no lesson needs a timed restriction, stop here with a suggested order. For the first screen learners see, use the first-five-minutes guide.
Official pages checked September 11, 2026. This is a documentation-based decision guide with original diagrams and examples; no product test or release-time experiment was performed. No signup or affiliate links.