Skip to main content

Staff View

The Staff View is a dedicated workspace for grooms and yard hands. It is deliberately narrower than the admin view: staff get exactly the surfaces they need to run the day, and nothing more. Staff access is unlocked with the Staff Management feature and is only available to team members with the staff role.

On the native mobile app, the staff view has its own bottom tab bar, so grooms can move between the day's screens one-handed while they work out in the barn — no need to dig through a desktop-style menu.

The dashboard

When a staff member logs in, they land on a dashboard that greets them by name and shows their own Pending and Done today task counts at a glance. From here, quick links lead to each of the surfaces below.

Today's Tasks (the daily loop)

This is the heart of the staff view. Each staff member sees only the tasks assigned to them for the current day, split into Pending and Done, with one large button per task to mark it complete.

Tasks are created on the admin side (see Task Management) — either as one-off tasks or as recurring templates. When a staff member marks a task done, the system stamps the exact time and automatically writes an entry to the horse's care log, so the owner-facing care history stays up to date without any extra effort from the team.

Works offline

Barns are notorious dead zones, so task completion is built to keep working with no signal. When a groom marks a task done (or logs work from the Horses screen) while offline, the change is saved on their device straight away and the task moves to Done as usual — an "Offline" banner reminds them that changes will sync automatically the moment the connection returns. Nothing is lost, and there's no need to stand in the one corner of the yard that gets a bar of signal.

Horses — bulk logging

The Horses screen is a paginated roster of the stable's horses. Staff can multi-select several horses and log completed work for all of them at once.

Bulk logging from the staff view is limited to the four hands-on task types:

  • TURNOUT — letting horses out
  • LUNGE — exercising on a line
  • TRAIN — riding or training
  • OTHER — anything else

FEED, FARRIER, and VET are intentionally not available here, because those are scheduled and managed on the admin side.

7-day activity & overtraining

Each horse on the roster has an Activity button that opens its last 7 days of logged work — trained, lunged, turned out, fed, and so on — showing what was done, by whom, and any notes. Because every team member's completed work feeds the same timeline, a groom can tell at a glance whether a horse has already been trained or turned out that day, which prevents it being worked twice by two people who didn't cross paths.

The timeline also flags when a horse's training load looks high for the week, as an early nudge against overtraining. The same 7-day view is available to admins on the horse's records and to owners on their own horse (see Health Records), so staff, office, and owner are all looking at the same picture of a horse's recent care.

Stable Map

A read-only view of stall occupancy, grouped by row, so staff can quickly see where every horse is stabled.

Paddocks

A read-only day schedule shown in 30-minute slots, with each slot marked free, reserved, blocked, full, or past. This lets staff see who is riding when without being able to change bookings.

Events & Lessons

A view-only calendar that merges stable events with lesson occurrences, so staff always know what's happening on the yard.

Maintenance

Maintenance is the one surface where staff genuinely act on shared data. Staff can operate the full maintenance queue:

  • Filter requests by active or resolved
  • Open a request to view its detail
  • Edit the internal notes
  • Move a request through open → in progress → resolved

This gives the team a single, shared place to pick up repair jobs and keep everyone updated on their status.

What staff can and can't do

The staff view follows a strict least-privilege model:

  • Tasks — staff can read only their own tasks, and the only thing they can change is marking a task complete.
  • Maintenance — staff can read and update every maintenance request for the stable.
  • Stable map, paddocks, events & lessons — read-only.

These limits are enforced at the database level, not just hidden in the interface.