Not all training programs fit in just one Module. A new hire might need an orientation Module in their first week, a role-specific Module a week later, and a leadership Module only if they move into a lead Role. Paths assign that sequence for you, so each team member gets the right Module at the right time, and nobody has to keep track of it by hand.
Paths are great for:
Growing a team member's skills step by step in their Role, like going from new hire to team lead
Cross-training team members on new skills
Running long-term training programs that last weeks or months
✅ Before you start: This article covers the new Path builder.
Admins can opt in for the whole business: go to Training > Paths and click Turn on for your org on the card in the bottom left corner.
Once it's on, everyone in your business who builds Paths uses the new builder.
💡 Used the Path builder before? Here's what's new:
Your Paths moved over automatically: existing Paths keep running as they did. Each one is named after its first Module, with [Migrated] in front, and you can rename it anytime.
Paths have their own names: name each Path for the program it runs, like New Hire Program.
Build with steps: instead of setting conditions between Modules, you add steps to a drag-and-drop canvas, like assigning a Module, waiting a few days, or checking a team member's Role.
Changes save automatically, and you publish when you're ready: team members keep following the published version until you do, and you choose what happens to anyone partway through.
Track each team member on the Runs tab: see where everyone is in the Path, step by step.
Choose when a Path assigns: set start and stop dates in the Path's Settings.
Table of Contents:
How Paths Work
✅ Before you start: To build Paths, you need the Manage Library and Update Automations permissions. Admins have both by default.
Think of a Path as a training plan that runs on its own. You line up Modules in the order you want, add any waiting time in between, and decide who gets which Module. Opus then moves each team member through the plan at their own pace.
Every Path starts when a team member completes a Module you choose, called the trigger. From there, Opus follows the steps you set up, like waiting a few days, checking their Role, or assigning the next Module.
The Path doesn't assign that first Module itself. It only starts once a team member finishes it, so assign the first Module the way you normally would, for example with an Automation that assigns it to every new hire.
It doesn't matter how they got it: a one-time assignment, an Automation, their Library, or another Path all work.
➡️ Learn more:
How to Assign Courses and Modules in Opus: how to assign the first Module once or with an Automation
How to Build a Path
Build Paths in the dashboard:
Go to Training > Paths and click New path. Opus creates a draft called Untitled path and opens the builder.
Click the title to give your Path a name, like New Hire Program.
Click the Training completion step and select the Module that starts the Path. It can be a Module your business built or a premium Module from the Marketplace.
Click + under the last step and choose what happens next:
Assignment to assign a Module.
Time delay to wait a few days.
Filter to continue only for certain team members.
Wait for completion to wait until they finish a Module.
Keep adding steps until your Path is complete, then click Publish.
To add a step between two others, click + on the line that connects them. Your changes save automatically as you go, so there's no Save button.
Undo and redo changes with the buttons at the bottom of the canvas, or with these keyboard shortcuts:
Undo:
Ctrl + Z(Cmd + Zon a Mac)Redo:
Ctrl + Shift + Z(Cmd + Shift + Zon a Mac)
Hover over either button to see how many changes you can undo or redo. The shortcuts don't work while you're typing in a field.
Choose When the Path Assigns
Click an empty spot on the canvas to open the Path's Settings:
Start assigning: when the Path begins assigning Modules. By default, it starts as soon as you publish.
Stop assigning: when the Path stops assigning Modules. By default, it keeps going with no end date.
Path Steps
Each step tells Opus what to do next for team members on the Path:
Assignment: assigns a Module, including premium Modules from the Marketplace.
Time delay: waits a set number of days before moving on. The next step happens at midnight in the team member's Location time zone.
Filter: continues only for team members who match the audience you choose, like a certain Role or Location. Everyone else stops here.
Wait for completion: waits until the team member finishes a Module that was assigned earlier in the Path.
If there's no Time delay, the next step happens right away.
When to Use Wait for Completion
An Assignment step assigns a Module and moves on right away. It doesn't wait for them to finish. So if you put two Assignment steps in a row, both Modules are assigned at the same time.
Add a Wait for completion step when the next step should only happen after a team member finishes a Module. Use it when:
One Module builds on another: assign Advanced Customer Service only after a team member finishes Customer Service Basics.
You don't want to overwhelm your team: give team members one Module at a time instead of a stack of assignments.
You want a break after they finish: a Wait for completion followed by a Time delay of 7 days assigns the next Module a week after they finish, not a week after it was assigned.
Wait for completion can only wait on a Module that was assigned earlier in the same Path. If a team member has already finished that Module, they move on right away.
Here's how a simple New Hire Program could look:
Training completion: a team member finishes Orientation.
Time delay: wait 7 days.
Assignment: assign Customer Service Basics.
Wait for completion: wait until they finish Customer Service Basics.
Filter: continue only for team members in the Team Lead Role.
Assignment: assign Leadership Essentials.
💡 Send team members down different routes: Drag from the bottom of a step to add more than one next step, like one Filter per Role. Each route continues on its own.
How to Publish a Path
When your Path is ready, click Publish. If a step still needs something, like a Module or a number of days, Opus highlights it in red and tells you what to fix.
If you're publishing changes and some team members are already partway through the Path, Opus asks what should happen to them:
Let them finish the current version: they keep following the steps they started with.
Move them to the new version: steps they've already finished stay done, and their remaining steps follow your changes.
Team members who start the Path after you publish follow the new version.
Edit a Published Path
To change a Path that's already running, edit it directly. Open the Path from Training > Paths and make your changes.
The Path shows Unpublished changes, and team members keep following the published version until you click Publish again, so you can take your time.
When you publish, choose what happens to team members who are partway through:
Let them finish the current version is the safe choice for most changes, like adding a Module at the end or changing a delay. Nobody's plan changes midway, and team members who start later get the updated Path.
Move them to the new version when you're fixing a mistake that affects everyone, like a wrong Module or a Filter with the wrong Role. If a team member's progress doesn't fit the new version, they stay on the current one.
💡 Make your changes in the Path itself: Your edits stay private until you publish, and everyone stays on the same Path.
View or Restore an Earlier Version
Click Version: Draft at the top of the builder to see the published version and every version before it, with when each was published and by whom.
Select a version to view it. You can't edit an earlier version, so click Back to draft when you're ready to keep building.
Go back to an earlier version: Select it and click Restore this version. It replaces your draft, and team members get it once you click Publish.
Throw away unpublished changes: Select Published and click Discard draft changes.
Version numbers, like v3, match the Version column on the Runs tab.
⚠️ Restoring replaces your draft: Any unpublished changes are lost.
How to Track Progress
A run is one team member's journey through a Path. Open the Path and select the Runs tab to see everyone who's on it, what they're waiting on, and who's finished. Click a run to see the Path from that team member's point of view.
➡️ Learn more:
How to Track Path Progress: see runs, take a team member off a Path, and check completion in the Completion Grid
How to Duplicate or Archive a Path
On the Paths page, open a Path's … menu:
Duplicate: creates a copy you can edit, named after the original. It's a quick way to start a new program from one you already have. Give the copy its own first Module so each Path starts for the right team members.
Archive: stops the Path from assigning and cancels runs in progress. Modules already assigned stay assigned.
⚠️ Archiving can't be undone: Archived Paths can't be restored or edited. If you might need a Path again, duplicate it first.
Best Practices
Assign the first Module with an Automation: for example, assign Orientation to every new hire automatically, so the Path starts on its own.
Keep each Path to one program: a New Hire Program and a Team Lead Program are easier to manage as two Paths than as one big one.
Add Wait for completion between Modules when order matters: this keeps team members moving one Module at a time.
Space out training with Time delays: give team members a few days to practice what they learned before the next Module.
Filter early: if a Path splits by Role or Location, add the Filter right after the step where it splits, so each team member only sees what applies to them.
Give each Path its own first Module: each Path runs on its own, so a unique first Module makes sure team members only get the training meant for them.
Check the Runs tab after publishing: once the first few team members start, open their runs to make sure they're moving through the steps you expect.
Name Paths clearly: use names like New Hire Program or Team Lead Program so everyone knows what each Path is for.
FAQ
Can I add Courses, Resources, or Check-ins to a Path?
No. Paths only assign Modules. Add your Courses, Resources, and Check-ins to a Module, then use that Module in your Path. Learn more: How to Create and Manage Modules: build a Module from Courses, Resources, and Check-ins
Who can build a Path?
Admins, and Managers whose Role has the Manage Library and Update Automations permissions. Anyone without both permissions won't see Paths.
Can I use premium content from the Marketplace in a Path?
Yes. You can use premium Modules from the Marketplace in any step that uses a Module: the step that starts the Path, Assignment, and Wait for completion. If your business loses access to a premium Module in a Path, replace it before you publish the Path again.
How do Paths work with my Automations?
They work together. Your Automations keep working as usual, and if an Automation assigns a Path's first Module, finishing that Module starts the Path.
What if a team member already completed a Module in the Path?
A Wait for completion step moves them forward right away if they've already finished that Module.
Can I remove one team member from a Path?
Yes. Open the Path's Runs tab, open the … menu on their run, and select Cancel run. Learn more: How to Track Path Progress: see runs, cancel a run, and check the Completion Grid
Should I edit a Path or make a copy?
Edit the Path itself. Your changes stay unpublished until you publish them, and everyone stays on one Path. A copy works best for starting a new program with its own first Module, since each Path runs on its own.
Can I undo changes to a Path?
Yes. Before you publish, select Published in the version menu and click Discard draft changes. After you publish, restore the earlier version and publish again.
Can I delete a Path?
No. Archive Paths you no longer need.
How are Paths different from Sections in a Module?
Sections organize the Courses, Resources, and Check-ins inside one Module. Paths assign a series of Modules over time.