Staff — Overview
Staff manages people and work schedules: staff view their own calendar/timetable, request and get approval for leave, and admins build weekly rosters with visibility into leave overlaps so they do not schedule incorrectly.
Four main areas
| Area | What it is | Users |
|---|---|---|
Staff Home (/staff/home) | Staff "My Calendar" page + navigation links | Staff |
Timetable (/staff/timetable) | Personal timetable, date/week navigation | Staff |
| Roster Weekly Planner | Admin schedules weekly shifts per staff member | Admin |
| Leave / Availability | Request leave, approve leave, declare availability | Staff + Admin |
Important ideas
- Leave has its own type: leave forms only show
TrackingCodeof type Leave (not Shift). - Roster can see leave overlapping shifts: when creating/editing a shift, the popup shows read-only
Leaveif the staff member has leave that overlaps the shift interval (compare by time interval, not only date). - One person = one row in planner, even when they have records in multiple BUs (dedupe by
enterpriseUserId).
Suggested reading order
- End-user view — what staff and admin do.
- Concepts & architecture — leave, roster, tracking code, dedupe.
- Data & read/write tables — EnterpriseUser, Shift/EmployeeAbsence tables in flows.
- Common cases — leave overlap, cross-BU, slot sorting.