Rule definitions
18
A mix of hard legal constraints and weighted soft preferences.
Settings
Control rules, roles, integrations, and organizational boundaries.
Settings is where the product becomes domain-agnostic: organizations encode their own hard and soft rules, permission boundaries, and integration hooks without rewriting the app.
Role profiles
05
Owner, admin, scheduler, staff, and observer access models are already mapped.
Integration targets
03
Payroll, HRIS, and time-tracking endpoints are reserved for later implementation.
Primary surfaces
Rules engine
Encode constraints in a way the optimizer and UI can both explain.
Hard versus soft rule modeling with explicit weights.
Jurisdiction-aware limits for hours, breaks, and rest.
Temporary overrides that always require audit reasons.
Roles and permissions
Access control must survive both UI state and database policy.
Role-to-capability mapping for every workflow.
RLS-ready boundaries around staff, scheduler, and observer data.
Sensitive actions isolated for admins and owners.
Integrations and billing
Operational systems can plug in without collapsing the core model.
Payroll and HR sync points for downstream reporting.
Calendar and notifications reserved for later rollout.
Organization-level settings and billing controls.
Build path
01
Lock the permission model
Define role claims and RLS rules before the app starts mutating real schedule data.
02
Ship configurable rules
Make hard and soft constraints editable through a guided rule editor.
03
Layer integrations later
Connect payroll and workforce systems once the core data model is stable.