Staff & Workforce Scheduling · Documentation

How to Use This Demo

Driving Staff & Workforce Scheduling in the host, the Cloud/OSS inspector, and the operator console — with honest labels.

Staff & Workforce Scheduling
  1. 1

    Signing in and reading the roster

    The ecosystem is gated — sign in as owner (admin / admin@123) for the full app, or as the read-only viewer for OPERATE. From the launcher, open Staff & Workforce Scheduling (C5 sub-tab 43). OPERATE shows the published week roster as a grid by department; a viewer can browse it, and operational actions like swap or leave requests are ephemeral to their session.

  2. 2

    Forecasting, rostering, and the inspector

    CONFIGURE (owner-only) is where the work happens: run the metered `forecast` (pick Cloud or OSS) to produce a recommended headcount per day and department with the weekend lift applied, then "Auto-roster" to solve and publish the week's shifts. The owner labour-cost view totals the published shifts by department. Audit logs owner actions (auto-roster, approve-shift). Open "Behind the scenes" for the trace — read-signals · forecast (the one cost row) · roster-solve · labour-check — and the mode. For a viewer, CONFIGURE and Audit are absent from the DOM.

How to Use This Demo · Staff & Workforce Scheduling · Abhishek Saxena