Most 24/7 teams don’t actually pin shifts to a specific seat — people sit wherever. That’s why location is optional on every shift, trade, OT opportunity, and duty. Use locations only when the seat genuinely matters for your org.
Manage locations
On/app/admin/locations:
- Name — required (e.g. “Console 3”)
- Code — optional short code (e.g. “C3”)
- Description — optional
- Active — if off, the location won’t appear in dropdowns
Using locations
Locations appear as optional dropdowns in several places:- User edit form — “Default position” for a user
- Shift creation — which console this shift is for
- OT opportunity — the seat the OT covers
- Duty assignment — the seat for a duty block
Reporting
Future reports will filter and group by location. For now, location is primarily informational.Required permissions
locations.view— readlocations.manage— create/edit/delete