> 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/training-requests.md).

# Training Requests

## What Are Training Requests?

**Training Requests** are topic ideas submitted by members of your organization. Instead of guessing what training your team needs, you get a running list of the subjects people have actually asked to learn about — so you can prioritize and build the content that matters most.

***

## How Requests Are Submitted

Anyone with access to the **Trainings page** can submit a request with the **Request training** button in the page header. It opens a short dialog — *"Tell us what you'd like to learn. Your request goes to your organization's admins."* — with two fields:

* **Topic** (required) — what they'd like training on, for example *Spotting deepfake voice scams*.
* **Description** (optional) — anything that helps: why they need it, who it's for, links.

Click **Submit request** and the request lands in the admin queue as **Pending**. Each request captures the topic, the description, who asked for it, and when.

***

## Reviewing Requests

The **Training Requests** page is **admin-only**. It lists every request your team has submitted, filterable by status (**All / Pending / Acknowledged / Completed**). Each card shows:

* The **topic** requested.
* Any **description** or note the requester added.
* The date and the current **status**.

***

## Working Through Requests

Each request moves through three statuses:

| Status           | Meaning                                                         |
| ---------------- | --------------------------------------------------------------- |
| **Pending**      | A new request that hasn't been looked at yet.                   |
| **Acknowledged** | Your team has seen the request and plans to act on it.          |
| **Completed**    | Training for the topic has been created or otherwise addressed. |

Use the actions on each request to update its status:

* **Acknowledge** — move a pending request to **Acknowledged** to signal it's on your radar.
* **Mark complete** — move a request to **Completed** once you've built or delivered training for it.
* **Reopen** — send a completed request back to **Pending** if it needs more work.

{% hint style="info" %}
Acknowledging requests is a simple way to let your team know their input was heard, even before the training is ready.
{% endhint %}

***

## Tips

* Filter by status to focus on **Pending** requests that still need a decision.
* Turn recurring or high-demand topics into a [Training Track](/herd-security-docs/tracks/training-tracks.md) so they're delivered on a schedule.
* When you finish a requested training, **Mark complete** to keep the list current.