> For the complete documentation index, see [llms.txt](https://herd-security.gitbook.io/herd-security-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://herd-security.gitbook.io/herd-security-docs/tracks/training-tracks.md).

# Training Tracks

### What Is a Track?

A **Track** is an ordered list of trainings assigned to users or groups. Rather than sending trainings ad-hoc, tracks let you define a learning path once and have Herd handle the scheduling automatically.

When a user is assigned to a track:

1. Their first training is delivered immediately (or after an onboarding delay).
2. Each subsequent training is queued and sent based on the cadence you configure.
3. Herd tracks their progress through every training in the track.

***

### Catalog vs. Custom Tracks

| Type             | What it is                                                                                      |
| ---------------- | ----------------------------------------------------------------------------------------------- |
| **Herd Catalog** | Pre-built tracks managed by Herd. Browse from the catalog and clone into your org to customize. |
| **Custom**       | Tracks you build from scratch using your own trainings.                                         |

To use a catalog track, open the **Catalog** tab, find the track, and click **Clone** (or **Clone Track** on the track's detail page). This creates an editable copy in your organization — the original is unaffected.

***

### Building a Track

#### 1. Create the track

Click **Tracks** in the left sidebar — it's a top-level navigation item, no longer nested under Trainings. Click **New Track** and fill in:

| Field           | Notes                                                   |
| --------------- | ------------------------------------------------------- |
| **Title**       | Required. Shown to users and admins.                    |
| **Description** | Optional summary of the curriculum.                     |
| **Tags**        | Used to filter and organize tracks across your library. |

#### 2. Add trainings

From the **Trainings** tab inside the track:

* Click **Add Training to Track** and search for any training in your library. (In the new-track create form, the per-row button is simply **Add**.)
* A **Mandatory by default** toggle on the track marks the trainings the track assigns **from now on** as mandatory, with an optional **Passing score** — existing assignments are unchanged.
* Trainings appear in a numbered list — this is the order they will be delivered.
* Drag rows to reorder. Position is saved automatically.
* A track must contain at least one training, up to a maximum of 50.

**Tip:** The track sends trainings in strict sequence. A user only receives Training 2 after completing Training 1.

#### Transition messages (optional)

You can show learners a short message between consecutive trainings — for example, to congratulate them on finishing one module and set up the next. Enable transition messages on the track, then write the message (up to 2,000 characters) between any two trainings in the list; a preview shows exactly what the learner will see.

#### 3. Set up due dates and reminders (optional)

In the **Assign** tab, give the track a **due date** and attach a reminder schedule. Reminders are anchored to the due date: by default Herd nudges users **2 weeks, 1 week, and 3 business days before** it's due, optionally **on the due date**, and then **after the due date** at a frequency you choose (every 3 business days by default). You can also **escalate** — after a number of days overdue, Herd notifies each user's manager or specific people you pick, with a customizable message. Reminders and escalations set here apply to all users assigned to the track.

***

### Assigning the Track

Go to the **Assign** tab on the track detail page.

The track detail page has four tabs: **Trainings**, **Assign**, **Escalations**, and **Results**.

#### Assign users directly

Search for users by name or email and add them individually. Each person begins the track from Training 1.

#### Assign a group

Select an Okta, Slack, Google, Azure (Entra), or Herd group. Every current member is enrolled. New members added to the group later are automatically enrolled if **Auto-assign to new group members** is enabled. Group assignments with it on show an **Auto-assign new** badge.

***

### Configuring the Cadence

The cadence controls how long Herd waits between completing one training and delivering the next. You set this per assignment, not per track — so the same track can run at different speeds for different groups.

| Cadence       | Behavior                                                                               |
| ------------- | -------------------------------------------------------------------------------------- |
| **Immediate** | Next training sends as soon as the current one is completed.                           |
| **Daily**     | Next training queued for the following day. Optionally restrict to business days only. |
| **Weekly**    | Next training queued for the same day next week.                                       |
| **Biweekly**  | Next training queued two weeks after completion.                                       |
| **Monthly**   | Next training queued one month after completion.                                       |
| **Custom**    | Next training queued after a specific number of hours you specify.                     |

**Example:** A five-training security awareness track on a weekly cadence delivers over five weeks — one training each week.

#### Business days

When using **Daily** cadence, enable **Business days only** to skip weekends. If a training would land on Saturday or Sunday, it shifts to Monday.

#### Catch-up

Enable **Catch-Up** to handle users who fall behind. Set a threshold (e.g., 3 days). If a user's next queued training is overdue by more than that many days, Herd bypasses the cadence delay and delivers it immediately to get them back on track.

### Onboarding Delay

If your organization has an onboarding delay configured, newly added users are queued but not sent their first training until the delay period expires. You'll see these users in the **Delayed Users** section of the Assign tab.

To bypass the delay for a specific user, click **Send Now** next to their name.

### Monitoring Progress

#### Assign tab

Shows every enrolled user and their current status:

| Status          | Meaning                                                        |
| --------------- | -------------------------------------------------------------- |
| **Not started** | User has been assigned but hasn't opened their first training. |
| **In progress** | User is actively working through the track.                    |
| **Completed**   | User has finished every training in the track.                 |

#### Results tab

Provides a training-by-training breakdown per user:

* Which trainings have been completed and when.
* How long each training took.
* Overall completion rate across the track.

Use the search box and the status filters (All, Completed, In Progress, Not Started) to narrow the list, and **Export CSV** to download the results.

### Editing a Track

You can update a track's title, description, tags, and training order at any time from the track detail page. Changes to training order take effect for users who haven't yet reached those trainings — users mid-training are unaffected.

> Removing a training from a track does not un-send it from users who have already received or completed it.

### Archiving a Track

To retire a track without deleting it, open the track's detail page and click **Archive Track**. An archived track:

* Is hidden from the active tracks list — the list's archive filter switches between **Active** (default), **Archived**, and **All**, and archived tracks carry an **Archived** badge.
* Can't receive new assignments and is excluded from reports.
* Keeps its historical completion data, and can be restored at any time with **Unarchive Track**.

Archiving the track doesn't archive the trainings inside it — each training remains independently usable. Archiving is blocked while the track still has in-flight assignments; complete or remove them first.

### Deleting a Track

Tracks are soft-deleted — they are hidden from your library but historical completion data is preserved. Deleting a track does not remove user progress records.

### Common Patterns

#### Monthly security awareness curriculum

1. Create a track with 12 trainings (one per security domain).
2. Set cadence to **Monthly**.
3. Assign your whole organization via your primary Herd group.
4. Enable **Auto-assign to new group members** so new hires are enrolled automatically.

#### New hire onboarding track

1. Build a track covering your most critical policies (5–7 trainings).
2. Set cadence to **Weekly**.
3. Assign the track to your "New Hires" group.
4. Let the org-level onboarding delay hold the first training until their first week settles.

#### Role-based training

1. Add a Herd catalog track relevant to the role (e.g., engineering, finance) to your library.
2. Customize the training order or swap in your own content.
3. Assign to the relevant department group.
4. Set a reminder schedule to follow up with non-completers after 2 days.