> 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/trainings/getting-started-with-trainings/assignment-statuses.md).

# Assignment Statuses

Each time you send a training, Herd keeps that send as its own assignment with its own status. Close, reopen or archive one assignment without touching the others, and see what learners and reports sh

Each time you send a training, Herd keeps that send as an **assignment**: who it went to, when, and how far each person got. A training can have many assignments, for example a September cohort and an October cohort. Every assignment has its own status, and closing one leaves the others, and the training itself, as they were.

You'll find a training's assignments on the **Assignments** tab of the training's page (see [How Assignments Work](https://herd-security.gitbook.io/herd-security-docs/trainings/getting-started-with-trainings/how-assignments-work.md)). Tracks and exercise scenarios have the same statuses. Each card shows its status as a pill. Hover over the pill, or move to it with the keyboard, to see what the status means for learners, reminders and reports.

Each card also says when the assignment went out and who sent it, in your own time zone, for example *Assigned Nov 12, 2026, 3:30 PM by Dana Lee*. On the small cards in the sidebar, choose **Details** from a card's actions menu to see the same line. A send nobody made by hand (a campaign, a track, a group rule or a repeat) names no sender, and a send by Herd staff reads **Herd Support**. The same line shows on a track's **Assignments** tab.

People who were removed from an assignment, or sent the training again in a later assignment, no longer count toward its total. If that leaves nobody in an assignment, its card shows a line in place of the completion bar, for example *No one left to finish it: 1 sent it again in a later assignment.*

## The five statuses

| Status        | What it means                                                                                     | What learners see                                                                                                                                                                                                                                                                                                                                                      | How it counts in reports                                                                                                                                                     |
| ------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Scheduled** | The assignment launches on a future date. Nobody has received it yet.                             | Nothing yet.                                                                                                                                                                                                                                                                                                                                                           | Nobody is enrolled yet, so there is nothing to count.                                                                                                                        |
| **Live**      | The assignment has launched and isn't past a fixed due date with people still working on it.      | The training in Slack, Microsoft Teams or the web player, with reminders on the training's schedule.                                                                                                                                                                                                                                                                   | Each person counts as completed, in progress, not started or queued.                                                                                                         |
| **Overdue**   | The assignment has a fixed due date on an earlier day, and some people haven't finished.          | The same as Live. They can still finish, and reminders and escalations after the due date follow the training's schedule.                                                                                                                                                                                                                                              | As for Live. People who haven't finished also count as overdue.                                                                                                              |
| **Closed**    | You closed the assignment, or its training was closed.                                            | People who hadn't finished no longer see it: it leaves their Slack App Home and Teams tab, the buttons on its Slack messages are removed, a button on an older Teams message tells them *This assignment has been closed by your administrator, so it can no longer be continued.*, and the web player won't open it. Anything they already completed stays completed. | Completions stay. Everyone who hadn't finished counts as **Closed – not completed**. They count against the completion rate, and not as in progress, not started or overdue. |
| **Archived**  | You archived the assignment, or its training was archived. An archived assignment is also closed. | The same as Closed.                                                                                                                                                                                                                                                                                                                                                    | As for Closed, when you archived the assignment yourself. When its training is archived, the training and all of its assignments leave reports.                              |

{% hint style="info" %}
An assignment on **relative** due dates (each person due a number of days after they receive it) never reads **Overdue** as a whole. Each person goes overdue on their own date.

**Overdue** and **Closed** are not the same. An overdue assignment changes nothing for learners: it stays in front of them and its reminders keep going. Closing it removes the unfinished training from them and stops its reminders. To give people more time instead, move the due date with **Edit reminders** on the live or reopened assignment (see [Changing an assignment's reminders](#changing-an-assignments-reminders)).
{% endhint %}

## Closing an assignment

On the **Assignments** tab, open the actions menu on the assignment's card and choose **Close assignment**, then confirm. Each status action in the menu has a line under it that sums up what it does to learners, reminders and reports.

* Reminders and escalations stop for anyone in it who hasn't finished.
* They show as **Closed – not completed** in reports, and completions stay.
* Other assignments of the same training are not affected. The training stays in your library, and you can still send it to new people and add it to tracks.

Which assignments you can close:

* **Assignments you made with New assignment.** Close any of them on its own.
* **Earlier assignments.** These hold everyone who had the training before Herd started keeping assignments in November 2026, grouped by how they got it: one card for everyone assigned by hand (for example *Manually assigned, Oct 9, 2026*), and one for each other source, such as AI Insights or a track. Each card carries an **Earlier assignment** pill. You can close or archive one the same way.
* **Assignments from a track, a compliance campaign or a group rule.** These keep enrolling people from their source, so you end them there. The exception is a group rule's past cycle, which you can close or archive from its card (see [Group rule cycles](https://herd-security.gitbook.io/herd-security-docs/trainings/getting-started-with-trainings/how-assignments-work.md#group-rule-cycles)).

Policy assignments can't be closed. On an exercise scenario, closing an assignment only stops its members being nudged: nobody is withdrawn, anyone who hasn't finished can still start it, and every result stays.

## Recalling an assignment from Microsoft Teams

Closing an assignment stops what hasn't gone out yet. To also take back the training messages people already received in Microsoft Teams, open the actions menu on the assignment's card and choose **Recall from Teams**, then confirm. You need permission to assign trainings, and your organization needs Teams connected. If Slack is connected too, the menu reads **Recall messages** and one recall covers both (see [Recalling an assignment from Slack](#recalling-an-assignment-from-slack)).

* Herd closes the assignment, so anything still waiting to go out isn't sent and its reminders stop.
* Herd deletes the assignment's training messages from the Teams chat of everyone who received them. They see *This message was deleted* in their place.
* Completions stay.

The card then shows when the recall ran and how many messages were recalled from how many people. A large assignment takes a few minutes: the card reads **Still recalling** and the count goes up while it runs.

If Teams couldn't delete some messages, the card says how many and for how many people. Choose **See who** to list those people with the reason:

* *The message or the chat is already gone.*
* *Teams refused: they have blocked or removed the Herd app.*
* *The recall was interrupted, so this may or may not have been deleted.*
* *Herd never saw whether this message was delivered, so it may still be in their chat.*

The last reason covers a message that **couldn't be confirmed as sent**: Herd began sending it, but its record never showed Teams accepting or refusing it (for example, Teams didn't answer in time, or Herd was restarted mid-send). Herd can't delete a message it has no address for, so it lists the person instead. The card says how many messages to how many people couldn't be confirmed as sent, and **See who** lists them. A person with more than one reason appears once for each.

A recall also waits for a message that is still being sent. It stays open for up to 15 minutes, and then lists whatever was never confirmed. If the message turns out to have been delivered, the recall deletes it.

{% hint style="warning" %}
A recall can't take back everything. Training messages sent before recall was added to Herd, reminders that were already sent, and copies sent by email stay where they are. Copies sent in Slack stay too, unless your organization has Slack connected.
{% endhint %}

Which assignments offer **Recall from Teams** (or **Recall from Slack**, or **Recall messages**):

* **Assignments you made with New assignment** on a training's own **Assignments** tab, once they have gone out. A scheduled assignment hasn't sent anything yet, so close it instead.
* **Earlier assignments** don't. Their messages were sent before recall was added.
* **Assignments from a track, a compliance campaign or a group rule** are ended at their source, so they don't. The exception is a group rule's past cycle (see [Group rule cycles](https://herd-security.gitbook.io/herd-security-docs/trainings/getting-started-with-trainings/how-assignments-work.md#group-rule-cycles)): where you can close or archive it from its card, you can recall it too, including a cycle that closed when the group moved on.

Tracks, policies and exercise scenarios have no recall.

You can't reopen an assignment while it is still being recalled, so its menu doesn't offer **Reopen assignment** until the recall has finished. After that you can reopen it, and recall it again. For the same reason, a group rule you turned off can't be turned back on while its cycle is still being recalled: save the rule again once the recall has finished.

## Recalling an assignment from Slack

If your organization has Slack connected, you can take back an assignment's training messages from people's Slack DMs the same way. The menu reads **Recall from Slack**, or **Recall messages** when Teams is connected too. The confirmation asks **Recall this assignment from Slack?**, or **Recall this assignment from Teams and Slack?** when it covers both.

A Slack recall deletes every message Herd posted for the assignment: the first message, each step reply in its thread, file and video messages and their buttons, and any step a learner asked to have sent again. The same rules apply as for Teams: Herd closes the assignment, completions stay, the card counts what was recalled, and **See who** lists anyone it couldn't reach. Slack adds three reasons of its own:

* *Slack no longer lets Herd delete messages: the Slack app was removed, or its access was revoked.*
* *Slack no longer has this conversation, or the person's account is deactivated.*
* *Slack would not let Herd delete this message.*

Slack limits how fast messages can be deleted, about 45 a minute for each workspace, so a large Slack recall takes longer than a Teams one. A recall of 3,000 messages takes a little over an hour. If it is interrupted, for example by a Herd update, it carries on by itself, more slowly, and can take several hours to finish.

A Slack recall can't take back messages sent before Slack recall was added to Herd (November 20, 2026), reminders, nudges, digests or copies sent by email.

## Reopening an assignment

Open the actions menu on a closed or archived assignment and choose **Reopen assignment**. Reminders and escalations resume for anyone who hasn't finished, and each person's current step is sent to them again so they can pick up where they left off. In reports they count as in progress, not started or queued again, and as overdue once they're past their due date.

You can't reopen an assignment while its training is closed or archived. Reopen the training instead.

## Archiving an assignment

Choose **Archive assignment** from the actions menu. The assignment is closed and moved out of the list on the **Assignments** tab. Completions stay in reports.

To see archived assignments again, click **Show archived assignments** below the list. You can reopen an archived assignment from there.

## Changing an assignment's reminders

An assignment follows the training's **Nudges** schedule unless you gave it one of its own when you sent it. To change it afterwards, open the actions menu on the assignment's card and choose **Edit reminders**. Saving gives the assignment a schedule of its own: the changes apply to the people in it only, and the training's **Nudges** tab and its other assignments keep theirs. Reminder emails, Slack and Teams messages follow the new schedule.

To go back, choose **Use the training's schedule** and confirm. Anyone already past the training's due date becomes overdue and starts getting overdue reminders.

Which assignments offer **Edit reminders**:

* **Assignments you made with New assignment** on a training's or a track's own **Assignments** tab, unless they're archived. A closed one keeps **Edit reminders**, but its reminders stay stopped until you reopen it.
* **Earlier assignments** don't. They follow the training's **Nudges** tab.
* **Assignments from a track, a compliance campaign, a group rule or a repeat schedule** don't. They follow their source's schedule. That includes a track's assignment listed on one of the track's trainings.

Policies and exercise scenarios have no reminders per assignment. While the training is closed or archived, none of its assignments offer **Edit reminders**.

## Closing or reopening the whole training

[Closing a training](https://herd-security.gitbook.io/herd-security-docs/trainings/getting-started-with-trainings/navigating-training-page.md#closing-a-training) closes every live assignment of it, and nobody new can be assigned until you reopen it. Each assignment it closed reads **Closed**, and the people who hadn't finished count as **Closed – not completed**.

Reopening the training reopens exactly the assignments its close closed. An assignment you had closed or archived yourself, before or after the training was closed, stays closed.
