First-time setup checklist
Follow these steps in order. Each one unlocks the next: you cannot build a labor forecast without a labor matrix, and you cannot build a labor matrix without job positions.
Locations
A location is one physical store or unit. Forecasts, labor plans, dashboards, permissions, and alerts are all scoped to locations, so this is the first thing to configure.
People and roles
People are the members of your organization. Roles decide what they can do; location permissions decide which stores they can do it for.
Location permissions
Roles say what a person can do. Location permissions say where, and can grant or remove individual capabilities for one person at one store.
Email groups
An email group is a named distribution list, for example alerts-leadership. Notification rules can be wired to a group so every member receives the alert without each person subscribing individually.
Forecast settings
These five settings pages are the engine room of forecasting. Configure them in the order below, because each one depends on the previous.
Approval settings
Approval settings decide whether a submitted forecast needs a human sign-off before it can be published, and who that approver is. They are configured per location.
Data stores
A data store is a read-only connection to the warehouse that holds your POS, labor, and review data. UnitOps queries it to power KPIs, dashboards, ML forecasts, and grounded AI answers.
Branding, org settings, and housekeeping
The remaining admin pages: how the app looks, what happened, and how to undo a mistake.
Documents
Upload handbooks, SOPs, vendor contracts, and training material so your team can find them, and so the AI assistant can answer questions from them.