Multi-location exception roll-up for owners and ops directors

GMs need their store. Owners need every store. How location-scoped permissions and a shared portal queue scale from three locations to twenty.

Multi-unit operators face a tension: central visibility without micromanaging every GM. Email chains and weekly calls do not scale; neither does logging into twelve separate accounts.

Location-scoped by design

Luminix permissions are role + location:

GM / shift lead — sees exceptions, schedules, and records for their location
Area manager — sees a district roll-up
Owner / ops director — sees organization-wide exceptions and KPIs

Same data model. Different lens. No duplicate tenants per store.

What rolls up to the top

The portal aggregates exceptions across modules:

Cert gaps by location
Below-par items after counts
Open shifts and publish blockers
Vendor invoice exceptions
Onboarding overdue items

Owners stop asking "anything I should know?" on every call — they open one queue filtered to what needs escalation.

GMs stay in control

Roll-up does not mean owners edit every schedule line. GMs publish and run the shift; owners intervene on exceptions and trends, not every checkbox.

Implementation pattern

Provision locations and roles in week one
Train GMs on portal + their primary modules in week two
Enable owner roll-up views once data is flowing — week three go-live

See multi-location rollout guide for the full narrative.