A course on Vome can live in two places. It can be a step inside a sequence, or it can stand on its own in your Courses list. Both are fully supported, and plenty of organizations use both at once. This article explains what actually changes between them, so you can pick the right one for each course you build.

It comes down to one question: who decides when the course happens, and what does it hold up?
Everything else, the content, the quizzes, the grading, the certificate, the expiry, the automations, works identically either way. The course is the same object. Only its placement changes.
Put it in a sequence when the training is a condition of getting started. Typical cases:
The short version: if not finishing the course should stop someone from moving forward, it belongs in a sequence.
Leave it standalone when the training is not a gate into onboarding. Typical cases:
A published course can be attached to a sequence as a Course step. The step carries its own gate:
You can also set a minimum score on the step, which overrides the course's own pass mark for that sequence only. That is useful when the same course serves two audiences at different standards. When the person finishes the course, they are returned to the sequence.
Two ways, and they work together.
They find it themselves. A published course appears in the Courses list for anyone eligible to see it, on the web and in the mobile app. You control eligibility with the course's visibility conditions, which can require the person to be active in your database, to have finished a specific sequence, to hold a specific Opportunity assignment, to be associated with a site, to fall in an age range, or to carry particular profile tags.
You enroll them. An administrator can always enroll someone directly from the course dashboard, including into a restricted or admin-only course. This is the practical answer when a course is meant for a named handful of people rather than a rule.
Yes. Attaching a published course to a sequence does not remove it from the Courses list, and one course keeps one roster. Whichever route people arrive by, the course dashboard is the single place you see everyone, their progress, their grades and their pass or fail result.
If you need people to take the training again later, use the course's expiry and renewal settings rather than building a second copy. A duplicate course splits your reporting and doubles the maintenance.
Expiry behaves the same whether the course was reached through a sequence or not. You can expire a credential a set time after completion, a set time after the person starts, or on a fixed date, and you can notify people ahead of time.
You can also point an expired person at a separate renewal course instead of the full original. In practice the renewal is usually the standalone case, because by then the person is long past onboarding and does not need to be walked back through a sequence.
No. Automations are configured on the course itself, not on the sequence step, so they run the same way in both situations. That includes granting an award, assigning profile tags, notifying the person and notifying an administrator.
There is one thing only a sequence can do. A sequence step automation can assign an Opportunity directly, and a course automation cannot. If direct Opportunity assignment on completion is the point of the exercise, that is an argument for the sequence.
For the full mechanics of building a course, see How do Courses work on Vome?. For turning a completed course into access, see How do I use a course to unlock shifts and Opportunities?