Required Qualifications

Overview

Qualifications let you say that a Support Worker must hold a particular credential — First Aid, NDIS Worker Screening, Manual Handling — before they can be rostered onto a shift.

A qualification isn't a new kind of record. It's built directly on your existing User Records: you mark an existing User Record Type as required for rostering, and Astalty works out who holds it from the records already on each worker's profile. There's nothing extra for workers to upload, and no separate Qualifications screen to maintain.

Requirements can come from two directions:

• Role-based — "everyone in the Support Worker group needs First Aid." Set up on the record type, and covered on this page.
• Participant-based — "anyone supporting this Participant needs Manual Handling." Set up on the Participant's profile — see Required Qualifications for a Participant.

Setting up a role-based requirement

1. Go to Settings → Users.
2. Find the User Record Types card.
3. Click Create User Record Type, or open the menu on an existing record type and click Edit.
4. Scroll down to the Rostering section.
5. Tick Required to work.
6. Choose a role from Select a role, choose an Enforcement level, then click Add. Repeat for each role that needs this qualification.
7. Click Update (or Create on a new record type) to save.

The Rostering section only appears once Qualifications is enabled on your account. Ticking Required to work reveals the description:

Warn or block rostering workers who don't hold a current record. Workers see this as a required qualification when you roster them.

Each role you add appears in a list above, with its own Enforcement dropdown you can change in place and a Remove link.

Once every user group has been configured, the add row is replaced with "Every role is configured."

Enforcement levels

Enforcement decides what happens when a worker who doesn't hold the record is rostered.

Block is selected by default when you add a role.

Turning a requirement off

There's no "Off" option in the dropdown. To stop enforcing a qualification, either:

• Remove a single role — click Remove next to it, then save. Everyone else's requirement stays in place.
• Remove the requirement entirely — untick Required to work and save. The qualification is deleted along with all of its role requirements.

Overlapping requirements

A worker can be covered by more than one requirement for the same qualification — for example, a role requirement set to Warn and a Participant requirement set to Block.

When that happens, the strictest one applies. If any requirement covering that qualification is set to Block, the worker is blocked.

Seeing which record types are required

Once Qualifications is enabled, the User Record Types table gains a Required to Work column showing a tick against each record type that has at least one rostering requirement.

Required record vs Required to work

The User Record Type drawer has two settings that sound similar but do different jobs:

• Required record (and Required for some user groups) controls whether the record shows as missing on the User Records Report. It's about record-keeping.
• Required to work, in the Rostering section, controls whether a missing or expired record warns or blocks when rostering. It's about scheduling.

You can use either on its own, or both together.

When a worker counts as holding a qualification

A worker holds a qualification when they have a current record of that type. A record is current when it is:

• not archived,
• not declined,
• verified, if the record type requires verification,
• not expired.

Anything else counts as a failure, and shows on the compliance report as one of four reasons: Missing, Expired, Awaiting Verification or Declined.

If you rename a record type, the qualification is renamed with it. If you delete a record type, the qualification and all of its requirements are deleted too. Deleting a user group removes that group's requirements.

Permissions

Setting up a role-based requirement needs permission to edit user record types, plus the qualification create, update and delete permissions. By default these sit with Admin users who can manage user records for other users.

Manager and Team Member roles can view qualifications but not change them, and Support Workers have no access. Individual permissions can be adjusted per user — see Roles & Permissions.

Related guides

• Required Qualifications for a Participant — requirements that apply to anyone supporting a particular Participant.
• Qualification Checks When Rostering — what schedulers see on the roster.
• Qualifications Compliance Report — who's currently missing a required qualification.
• Lapsed Qualification Notifications — get alerted when a worker on an upcoming shift is no longer qualified.