# 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 to Organization**. This creates an editable copy in your workspace — the original is unaffected.

***

### Building a Track

#### 1. Create the track

Navigate to **Tracks → 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** and search for any training in your library.
* Trainings appear in a numbered list — this is the order they will be delivered.
* Drag rows to reorder. Position is saved automatically.
* A track can contain between 1 and 50 trainings.

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

#### 3. Set up reminders (optional)

Under **Details → Reminder Schedule**, attach a reminder schedule to the track. This controls how often Herd nudges users who haven't completed their current training. Reminders set here apply to all users assigned to the track.

***

### Assigning the Track

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

#### 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 a Slack, Okta, Google, or Herd group. Every current member is enrolled. New members added to the group later are automatically enrolled if **Auto-assign new members** is enabled.

***

### 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.                                       |
| **Hourly**    | Next training queued N hours after completion (you set N).                             |
| **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 Assignment tab.

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

### Monitoring Progress

#### Assignment 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 over a selectable time range (week / month / quarter / all time).

#### Nudging

To send a one-off reminder to a user who is behind, click **Nudge** next to their name. To nudge an entire assigned group at once, use **Nudge Group**.

### 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.

### 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** (use **Custom** with 720 hours, or **Weekly** × 4).
3. Assign your whole organization via your primary Herd group.
4. Enable **Auto-assign new 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. Clone a Herd catalog track relevant to the role (e.g., engineering, finance).
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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://herd-security.gitbook.io/herd-security-docs/trainings/getting-started-with-trainings/training-tracks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.