Prerequisites
Prerequisites gate a program so it stays locked until a learner satisfies the conditions you set — finishing something else first, scoring above a threshold, belonging to a group, or having been enrolled long enough.
What this does
Section titled “What this does”A prerequisite is a set of conditions attached to one thing — a program, one offering of a program, or a step inside a program. Lurno evaluates them for each learner; until they pass, the gated item stays locked and the learner sees what is still outstanding.
Rules are built two levels deep and no deeper: paths, and conditions inside each path.
- Inside a path, conditions are joined by ALL or ANY.
- When there is more than one path, a single Match control at the top decides whether the learner must satisfy ALL of the groups or ANY of the groups.
Two paths joined by “any” is how you express alternative routes in — “finish the course, or pass the challenge test”.
This works the same whether your learners are employees, students, pupils or customers; those words may be renamed for your organization (see Terminology).
Before you start
Section titled “Before you start”- You can manage prerequisites in your organization.
- Everything you want to reference already exists: the program being gated, and the programs, modules, assessments, assignments, groups or offerings the conditions point at.
- Conditions can only reference things inside your own organization.
Set prerequisites
Section titled “Set prerequisites”- Open Programs, open the program, and choose Prerequisites under Scheduling in the left rail. (From the other direction: Scheduling → Set prerequisites, then pick a program from the list.)
- You start on Path 1. Set its joiner to ALL or ANY.
- Choose Add condition. A panel opens; pick a condition type and fill its fields (see the table below), then choose Add condition in the panel to put it on the path.
- Repeat for more conditions on the same path.
- To offer an alternative route, choose Add alternative path — you get Path 2, and the Match control appears above so you can set ALL or ANY across paths.
- Choose Save.
Use the List / Graph / Boolean tabs at the top right to check your work. List is where you edit. Graph draws the rule as a dependency diagram and Boolean prints it as an expression — both are read-only views of the same rule.
Condition types
Section titled “Condition types”| Condition | What it asks for |
|---|---|
| Entity completion | The learner has completed a specific program, module, assessment or assignment |
| Minimum score | The learner scored at or above a threshold, out of 100, on a chosen item |
| Time enrolled | The learner has been enrolled for at least a number of days |
| Date condition | A specific date and time has passed |
| Manual approval | A person must approve — pick Instructor or Admin as the approver |
| Group membership | The learner belongs to a chosen group, optionally in a specific role |
| Co-requisite | The learner is also enrolled in another offering, optionally in a specific enrollment state |
Approvals
Section titled “Approvals”Scheduling → Approval queue is where prerequisite approval requests are reviewed. For each request you can Approve (unlocks the gated content), Reject (the learner can address the reason and ask again), or Mark as reviewing to claim it so nobody double-handles it. A note you add is shown to the learner if you reject, and a reason is required before a rejection will save. A decided request can be re-opened. Waiting requests are also counted under Needs your attention on the Scheduling home page.
Chains
Section titled “Chains”Prerequisites chain naturally: gate B on completing A, gate C on completing B. Lurno runs a cycle check on save and refuses a rule that would make a loop, showing you the path of the cycle. Keep chains shallow — a misconfigured early step blocks everything downstream.
In a program’s Schedule view, choosing When the previous step is completed on a step creates exactly this kind of completion prerequisite behind the scenes. Note that it also replaces whatever prerequisites that step already had; see Drip content.
Troubleshooting
Section titled “Troubleshooting”Saving again created duplicate rules. Expected — the builder never loads what is already saved, so every save adds. Check the Graph or Boolean view and remove the extras.
“Circular dependency”. The rule would create a loop (A needs B, B needs A). The message lists the cycle. Point one of the conditions at something else.
“Wrong organization” or “Missing entity”. A condition references something outside your organization, or an entity was never picked. Reopen the condition and choose a valid item.
“Unsupported entity type”. The thing you picked isn’t a supported prerequisite target. Choose a program, module, assessment or assignment.
A learner finished the item but is still blocked. Check whether the condition is Entity completion or Minimum score. Someone can finish an assessment without reaching the score you required.
Content unlocked earlier than expected. The Match control across paths is on ANY, so satisfying one path was enough. Switch it to ALL if every path must be met.
A learner is stuck behind a Manual approval condition. Remove the condition. There is no learner path to request approval today, so nothing will arrive in the queue to approve.
Prerequisites I set on a step disappeared. Someone changed that step’s Starts in the program’s Simple schedule view, which rewrites that step’s prerequisites.
Save fails with a permission error. Inside a program the authoring buttons stay visible even when you can’t save; the server is the real gate. You need the manage-prerequisites permission. See Roles & permissions.