> 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/messaging/reminders.md).

# Reminders

Chase completion of work that lives outside Herd — an LMS course, an HR form, a vendor attestation — with a roster, a reminder cadence, and Send now.

## Overview

**Reminders** are for things your people need to finish *outside* Herd: a course in an external LMS, an HR form, a vendor's security training. You create an item, assign people or groups to it, and Herd keeps asking the people who aren't done yet — by Slack or Teams direct message, inside their business hours, at most once a day — until they are marked complete.

To open it, expand **Messaging** under **Manage** in the left-hand sidebar and click **Reminders**. It sits beside [Announcements](/herd-security-docs/messaging/announcements.md).

{% hint style="info" %}
Reminders for Herd's own content don't need an item here. A training's or track's reminder schedule lives on its **Nudges** tab, telling a manager about someone still overdue lives on its **Escalations** tab (see [Assigning Users to Training](/herd-security-docs/trainings/getting-started-with-trainings/assigning-users-to-training.md#due-dates-nudges-and-escalations)), and compliance campaign reminders are covered under [Nudges](/herd-security-docs/campaigns/nudges.md).
{% endhint %}

Seeing the page needs the **View events** permission and creating items, assigning people, sending reminders, and marking completion needs **Manage events** (both listed under **Events** in the permission picker — the page's earlier name). Admins always have them.

***

## Creating an item

Click **New item** and fill in:

* **Title** (required) and an optional **Description**, which is shown in the reminder so people know what they're being asked to do.
* **Link** — where they go to do it. It becomes the button in the reminder.
* **Due date** (required).
* **Nudge every (days)** (required) — the reminder cadence.
* **How do we know someone is done?** — **Manual — an admin marks people done**, or **External — read from a connected system** when a connected system (for example a Docebo course) can report completion for you. See [Docebo Integration](/herd-security-docs/messaging/reminders/docebo-integration.md).

Click **Create item**. The list shows every item with its **Progress**, **Due** date, **Cadence**, and **Completion** method.

***

## Assigning people and how reminders are timed

Open an item to see its roster and assign people or groups. Assigning someone sends nothing right away: the first reminder goes out the cadence's number of days after they are assigned, during their business hours on a weekday, and then again every cadence period until they are done. Business hours are your organization's configured window read in each person's own time zone; with business hours off, it is 9 AM–5 PM on weekdays in the person's zone. Herd checks hourly, so a reminder lands within about an hour of the window opening — an item assigned on a Thursday with the default cadence first reminds on Monday.

The roster answers "why hasn't my reminder sent yet?" directly. Each row shows the person, their **Status** (**Done** with the date, or **Not done**), when they were **Last nudged**, how many **Nudges** they've had, and their **Next reminder** — a date and time, **Within the hour** when it is due now, or **—** when nothing is scheduled.

### Send now

If you don't want to wait for the cadence, use **Send now** — on a person's roster row to remind just them, or at the top of the item page to remind everyone still outstanding. It sends immediately, even outside business hours, but still at most one reminder per person per day, never to someone on leave or do-not-disturb, and it restarts that person's cadence from the send. The result toast tells you what happened, for example *3 sent · 1 already reminded today · 2 on leave or do not disturb · 1 not on Slack or Teams*.

### Marking people done

For items with manual completion, mark people done from their roster row (**Mark done**), individually or in bulk, and **Reopen** if you need to. Items tied to an external system are marked done as that system reports it. Remove someone from the item with the remove control on their row.

***

## Related

* [Docebo Integration](/herd-security-docs/messaging/reminders/docebo-integration.md) — mark people done automatically from Docebo course completion.
* [Announcements](/herd-security-docs/messaging/announcements.md) — a one-off message to everyone, with nothing to chase.
* [Nudges](/herd-security-docs/campaigns/nudges.md) — reminders for trainings, tracks, policies, and compliance campaigns inside Herd.