
Courses do two different jobs, and it is worth naming them separately.
During onboarding, a course is a gate: something somebody passes before they start. For people who are already active, a course is an offer: something to go deeper with, or to stay current with.
This article is about the second job. It is for administrators deciding what to offer once somebody is already contributing.
The builder is identical, so there is nothing new to learn. What changes is who you point it at and why.
If you need to know how to build a course chapter by chapter, that is covered by the onboarding material. Here the question is not how but what to offer, and to whom.
Four patterns cover almost everything organizations actually build:
You rarely want every course visible to everybody. Restrict a course and only people who meet your conditions will find it.
The conditions are the same family used across Vome:
They combine with AND, so each one you add narrows the audience.
The most useful condition here is usually assigned to an opportunity. An advanced course for your kitchen team is genuinely confusing to somebody who drives deliveries, and gating it on the role means the offer only reaches people it could apply to.
A required course can be unrestricted, because everybody has to do it and its relevance is not in question.
An optional one is different. If you offer everything to everybody, your course list becomes a wall that people scroll past, and the specialist course you actually wanted somebody to take is buried in it.
So the default for an optional course should be a condition, not an open door. Ask who this is genuinely for, and set that as the rule.
A course can expire, which is what you want for compliance training that has to be redone.
You choose how the clock runs:
Two things make this genuinely useful rather than just a deadline:
You can point people at a shorter renewal course instead of the full original. Somebody renewing their food handling certificate does not need the introduction again, and being made to sit through it is how renewal turns into a chore people avoid.
You can warn them before the expiry date rather than after it. Turn on expiry notifications and set how many days of lead time. Telling somebody their certification lapsed last week is an administrative problem you created; telling them it lapses in thirty days is a reminder they can act on.
If you are unsure, start with a renewal. It has a real deadline attached, so it is the one where the tooling saves you actual work rather than just offering a nice option.