All Collections
How to nest tracks within tracks
How to nest tracks within tracks

Learn about how to add one track into another track and about the benefits of doing so.

Chris Ramlow avatar
Written by Chris Ramlow
Updated over a week ago


As an admin or content owner you want to nest a track within another track.

This is especially useful for integrating generic tracks (like new employee onboarding) into persona-specific tracks (like new engineer onboarding) without duplicating work and creating a single learning path for tracking consumption and feedback.


Use the Tracks within tracks feature, following these steps.

  1. Make sure Tracks within tracks is enabled at Settings > Feature Management > Features > Tracks within tracks.

  2. Access the track you want to add another track to.

    (Please note that if the track has sections the "add a content" button is available in the header of each section instead and not at the top, so we know which section the item should go to:)

  3. Open the context menu (button with three dots) and select Edit.

  4. Open the Track Items and click the add content button (plus sign button).

    The Add Content to Track dialog opens.

  5. Set the Content Type filter to Track and search for the track Name you want to add.

  6. Select the check box for the track and click Add to track.

  7. Optionally, drag and drop the track on the left side of the Track Items page to reorder it within the track.

Go deeper

Why nest tracks within tracks?

When multiple tracks naturally flow together or are part of a larger learning initiative, you can manage all the content in a single learning path or playbook. Some of the benefits of this are:

  • You can delegate ownership of individual sub-tracks so that they can be managed and evolve on their own independently of the whole. For example, for a Backend Engineering Onboarding track, you could let one team own the HR Onboarding track and another own the Engineering Onboarding track that are within it, allowing you to use those tracks within yours without having to manage them.

  • It's easier to receive and gain insight from user feedback on a single track than on multiple tracks. You can even gauge the difference in feedback for a track when it stands alone versus when it is part of a larger learning path.

  • Instead of gauging consumption on multiple tracks, you can do it on one.

  • Instead of managing assignments (like dropping, completing, or exempting track content) in multiple tracks, much of the work can be consolidated by integrating tracks together.

  • Track sections make it easy to organize multiple tracks for the optimal experience for people consuming the track.

See also

Did this answer your question?