OperationSavvy added the first web-app administration foundations for managing the structure behind a workforce operation: roles, permissions, organisations, departments, instruments, levels, regions, services, and teams. This release matters because workforce operations software has to model how a business is actually organised — a flat roster is not enough when teams work across different sites, regions, departments, service lines, and permission boundaries.
What changed
- Added role management and API/web support for roles.
- Added permission management and the ability to manage role permissions.
- Added organisation model, API resources, policies, seeders, and organisation UI.
- Added department model/API/settings pages.
- Added the first instrument, level, region, service, and team model stacks.
- Added supporting TypeScript types, Inertia pages, settings navigation, and model-generation improvements used by later admin areas.
Why it matters
Labour-intensive businesses are rarely simple. They need software that can separate responsibility, location, service type, seniority, permissions, and team structure without forcing everything into one generic list. These early web-app commits established the administrative model that later scheduling, site management, compliance, payroll, and field workflows could build on.