# Required Qualifications

Source: https://docs.astalty.com.au/guide/participants/required-qualifications

> Require workers to hold particular qualifications before they can be rostered to a specific Participant.

Astalty Premium - This feature is part of the Astalty Premium plan. See What Premium includes.

## Overview

Some Participants need workers with particular training - Manual Handling, PEG feeding, Epilepsy Management. **Required Qualifications** on a Participant's profile let you enforce that: anyone rostered to support this Participant must hold the qualification you nominate.

This works alongside the role-based requirements set up in [Settings → Users](https://docs.astalty.com.au/guide/settings/users-settings/qualifications). A worker rostered to this Participant has to satisfy both.

Like role-based requirements, Participant requirements are built on your existing [User Record Types](https://docs.astalty.com.au/guide/settings/users-settings/user-records) - there's nothing extra for the worker to upload.

## Setting required qualifications for a Participant

By default, only Admins who can manage other users' records can edit a Participant's Required Qualifications.

1. Open the Participant's profile.
2. Go to the **Preferences** tab.
3. Find the **Required Qualifications** card and click **Edit**.
4. Choose a **Qualification**, choose an **Enforcement** level, then click **Add**. Repeat for each qualification.
5. Click **Save**.

The drawer explains it this way:

> Choose which qualifications a worker must hold to be rostered to this participant, and how strictly each is enforced. Blocking prevents assignment; warning allows it but flags the worker in the picker and schedule.

Each qualification you add appears as a row with its own **Enforcement** dropdown you can change in place, and an **X** to remove it.

![The Required qualifications drawer for a Participant listing First Aid Certificate, Manual Handling, Midazolam Training and Medication Management, with their Enforcement dropdowns highlighted (Block, Warn, Block, Warn), an X beside each row, and the Qualification, Enforcement and Add row below.](https://docs.astalty.com.au/assets/qualifications-participant-required-qualifications.png)

Once every available record type has been added, the add row is replaced with **"Every qualification is configured."**

## Enforcement levels

| Level     | What happens                                                                                                |
| --------- | ----------------------------------------------------------------------------------------------------------- |
| **Warn**  | Workers are flagged when rostered to this Participant without the qualification, but can still be assigned. |
| **Block** | Workers can't be rostered to this Participant unless they hold the qualification.                           |

**Block** is selected by default when you add a qualification.

> **Participant requirements cannot be switched off**
>
> Unlike some other settings, there's no "Off" option here - only **Warn** or **Block**. To stop enforcing a qualification for this Participant, click the **X** on the row and save.
>
> Saving with no rows clears every required qualification for that Participant.

## How requirements appear on the card

Once saved, the **Required Qualifications** card shows one chip per requirement:

- **Red** chips are set to **Block**.
- **Amber** chips are set to **Warn**.

Hovering a chip explains the enforcement in plain language. If nothing has been set up yet, the card reads **"No required qualifications set."**

## Overlapping requirements

A worker may be covered by a role-based requirement *and* a Participant requirement for the same qualification. When that happens, the strictest one applies - if either is set to **Block**, the worker is blocked.

> **Participant requirements don't appear on the compliance report**
>
> The [Qualifications Compliance Report](https://docs.astalty.com.au/guide/reports/qualifications-compliance-report) and its export only cover **role-based** requirements.
>
> A worker who fails only a *participant-based* requirement will never show up there. Those failures surface on the schedule, in worker suggestions and when saving the roster instead, so the compliance report isn't a complete picture of Participant-specific requirements.

> **Archived Participants stop enforcing**
>
> While a Participant is archived, their required qualifications stop being checked - archived Participants are excluded from rostering checks. The requirements aren't deleted; they start applying again as soon as the Participant is unarchived.

## Related guides

- [Required Qualifications in Settings](https://docs.astalty.com.au/guide/settings/users-settings/qualifications) - role-based requirements that apply across a whole user group.
- [Qualification Checks When Rostering](https://docs.astalty.com.au/guide/scheduling/qualification-checks) - what schedulers see when they roster someone who doesn't qualify.
- [Participant Preferences](https://docs.astalty.com.au/guide/scheduling/setup/participant-preferences) - the other preference settings on this tab.