The bell icon at the top right keeps you across field activity from your workers, plus any announcements you have sent. Select the bell to see the five most recent items, or open the full page from Notifications.

Read and clear notifications

The All notifications table lists items newest first, with the Event, the Notification text, When it happened, and a Status of Read or Unread.

Select Mark all read to clear every unread item at once. It is greyed out when nothing is unread.
Select any Unread row to mark just that one read.

Notification preferences

You need Settings edit access to change workspace notification preferences. Select Preferences to choose which field events notify your office team. These are shared office-team preferences for this workspace, rather than your personal email or phone settings. Events are on by default, so turn off only the routine updates the team does not need.

The five groups follow the office workflow. Each switch controls that event independently:

Group	Events and choices
Shift acceptance	Shift declined and Shift unconfirmed for shifts that require a worker response.
Attendance	Clock in, Late clock-in, Early clock-out, Clock out, Missed clock-out, Break started and Break ended. Keep exception alerts separate from routine clock messages.
Travel and transport	Travel started, Travel ended, Pickup and Drop-off. These describe recorded travel or participant attendance actions.
Progress notes	Progress note submitted and Progress note overdue. A submitted note still needs the office’s review.
Incidents	Incident reported, which is always on and cannot be disabled.

Late clock-in applies when a worker has not clocked in five minutes after the scheduled start. Early clock-out applies when they clock out at least five minutes before the scheduled finish. It is a high-priority office notification with its own switch, independent of Clock out. Missed clock-out applies when a worker is still clocked in five minutes after the scheduled finish. Late and missed checks run every five minutes, so an alert is not a promise of delivery at an exact second.

Progress note overdue applies twelve hours after a shift ended without a submitted note; its overdue check also runs every five minutes. A notification does not itself correct the clock or submit, review or approve the note.

Shift acceptance is about workers confirming the shifts you publish to them, and only ever fires on a shift whose Acceptance is set to Required (see Assign a worker):

Shift declined: a worker declines a shift you published to them.
Shift unconfirmed: a shift is still unconfirmed 48 hours, then 12 hours, before it starts.

A worker accepting sends nothing; the shift’s Accepted status is the signal.

There is no Save button: each toggle saves on its own, with a toast such as Clock in notifications off.

Note

Incident reported is always on and cannot be turned off, so this preference cannot suppress an incident notification.

Workspace-wide notification preferences show separate declined and unconfirmed-shift choices; changes save automatically. — 1Keep decline notifications enabled so the office can arrange cover.
2This warns about requests still unanswered 48 hours and 12 hours before the shift.
The shown acceptance alerts are enabled for the whole office team. Each switch saves independently; there is no separate Save action.

Attendance preferences distinguish late clock-in, early clock-out and ordinary clock-out notifications. — 1Late clock-in alerts start five minutes after the scheduled start.
2Early clock-out is a separate high-priority alert for at least five minutes early.
3Ordinary clock-out notification is independent from the early warning.
These saved choices keep late and early exceptions separate from ordinary clock-out messages. The pictured switches do not change worker clocks.

Example: routine messages and exceptions

If the office does not need every completed-shift message, it can turn Clock out off while leaving Early clock-out and Missed clock-out on. Review those three switches separately: suppressing a routine event does not turn off the independent exception events. Keep Incident reported on as required by the app.

Wait for the saved confirmation after each change, then reopen Preferences to check it. To reverse a choice, change that event’s switch back and wait for confirmation again. These controls do not change worker clocks, shift acceptance, phone permissions or personal email subscriptions.

Send an announcement

If you have Settings edit access, the Announcement card lets you message your workers in their app and as a push notification. It reads Message all workers or pick specific ones, in-app and push.

Note

The composer is gated by a workspace feature. With Account > Features > Communication > Announcements switched off, the Announcement card disappears from this page for everyone. See Workspace features.

Choose who it goes to

Leave the Recipients picker empty to reach every active worker, shown as an All workers chip. To target specific people, search the picker (Search workers) and add them; each one becomes a chip. The picker is a searchable multi-select, so you can add as many as you need.

Write the message

Enter a Title (up to 120 characters) and a Message (up to 1000 characters). The send button stays greyed out until both have text.

Send it

The send button reflects who it reaches: Send to all workers when the picker is empty, or Send to workers when you have chosen specific people. Select it, and a Send announcement? dialog confirms the audience: This goes to every active worker in your workspace, in their app and as a push notification. for everyone, or This goes to N selected worker(s), in their app and as a push notification. when you targeted people. Select Confirm. You see Announcement sent to N worker(s). and the fields clear. If nobody matched, you see No matching workers to notify. instead.

Watch out

An announcement cannot be recalled once sent. Check the recipients, title and message before you select Confirm.

Availability requests and responses

Availability notifications open the relevant collection period or submission. Casual workers receive a request on mobile, and the office can review their response in Workforce > Availability > Approvals. If the office proposes new hours, the worker can accept them or resubmit a different response. See Review availability submissions.

Platform announcements and release notes

Platform updates can appear in a banner above the office navigation or in an announcement dialog. Follow Release notes for the full change history. Dismissing an announcement clears it for your own account; it does not dismiss it for the rest of your team.

These updates are separate from the office announcements you write for workers. On mobile, the Home tile surfaces a recent office announcement for up to 24 hours, while the message remains in the Notifications list afterwards. Push notifications go to the worker’s active phone.

Worker reminders and your own emails

Office notification preferences are separate from worker phone reminders. The owner controls six worker reminders under Account > Features > Scheduling, covering the 60-minute and 15-minute pre-shift alerts, missed clock-in/out, progress notes due and participant transport. See Workspace features.

Your personal Product news, NDIS & award updates and Tips & training email choices are on Account > Account > Emails. Service notices stay on. Phone alerts depend on a worker’s signed-in app and notification settings; a sent announcement is not proof every phone displayed it.

Check the destination before acting

Open the notification and confirm the participant, worker, shift and date before changing a record. Marking an item Read only acknowledges the notification; it does not approve an assignment, resolve an incident or accept availability. If the linked screen is unavailable, check your role and whether the module is enabled. A missed phone push does not prove no notification or assignment exists: workers should check the app’s Notifications and schedule after reconnecting.