Venue & Settings
Group Command Centre, Performance, and Operations
Use the All locations command centre to review today's pulse, compare performance, manage live issues and messages, and configure group settings.
Last updated 10 July 2026
TL;DR
- The web-only All locations workspace is organised around Today, Performance, and Operations.
- Today shows the group pulse, live issues, booking pace, and linked-location status.
- Performance keeps one URL-backed location and date scope across Overview and Reports.
- Operations keeps Issues, Messages, and privileged Tasks in one work area.
- Group settings hold linked locations, shared booking identity, and reliable operations thresholds.
The Group Command Centre helps multi-location operators decide what needs attention now, compare locations without losing scope, and hand live issues into internal follow-up. It is behind rollout gates, so not every multi-venue account will see it. It remains separate from the public group storefront and individual venue workspaces.
Where to find it - Web: Open an enabled All locations workspace, then use Today, Performance, or Operations in the sidebar. Mobile: Not available.
Access and rollout requirements
The workspace requires a linked group and GROUP_ADMIN_CONSOLE_ENABLED. Consolidated reports require PRO access for every selected location. Operations additionally requires GROUP_ADMIN_OPERATIONS_CONTROLS_ENABLED.
| Role | Workspace behaviour |
|---|---|
| Group owner | Full Today, Performance, Operations, Tasks, group settings, and group menu access. |
| Regional manager | Group-wide Today and Performance, issue and message management, Tasks, and permitted Manage destinations. |
| Location manager | Data is scoped to accessible linked locations. Issues and Messages are read-only; Tasks and privileged group settings are hidden. |
| Venue staff | Continue using the source venue workspace; the command centre is not a staff or mobile surface. |
If access is missing, the UI can show You do not have access to group reporting, You do not have access to this overview, Group inbox unavailable, or Operations are unavailable.
Today
Today is the landing surface. It shows a compact current pulse, live issues that need attention, booking pace for each venue's local day, and linked-location status. Freshness comes from source timestamps rather than the page load time.
Use Assign to me on a live issue to create or reuse its active task. Issues retain stable identity across refreshes and stay visible until their underlying source condition clears. Completing a task alone does not resolve its source issue.
Booking pace compares each linked location's local today with the same weekday in the previous week. This prevents one shared server timezone from moving a venue into the wrong operating day.
Performance
Performance combines two tabs under one scope:
| Tab | What it shows |
|---|---|
| Overview | Compact group metrics, a comparison-first location table, risks, and source-report drill-downs. |
| Reports | Searchable group-capable report library, recent reports, up to eight personal pins, CSV actions, and print actions. |
Use Performance scope to choose the date range and linked locations. The scope is stored in the URL and preserved while switching tabs or opening a source report. Old /overview and /reports bookmarks redirect into the matching Performance tab with their existing query parameters.
Group reporting can show blocked states when consolidation is not safe:
| Blocked state | Meaning |
|---|---|
| No linked locations | Link locations to the group before using all-location reporting. |
| Mixed currencies cannot be consolidated | Select locations that use the same reporting currency. |
| Selected scope includes a non-PRO location | Every selected location must have PRO access before consolidated reports can run. |
| No PRO locations available | At least one linked location needs PRO access. |
| Location unavailable | A selected location is no longer available to the group or account. |
Operations
Operations has three URL-backed tabs:
| Tab | What it does |
|---|---|
| Issues | Shows live cross-location conditions with stable identity, location filtering, reliable age/SLA state, and assignment actions for privileged roles. |
| Messages | Embeds group inbox oversight for overdue, escalated, complaint, unassigned, and AI-review conversations. |
| Tasks | Lets owners and regional managers manage internal follow-ups created from issues or directly. |
An issue only shows an age or SLA breach when its source provides a trustworthy timestamp or metric. Severity alone does not manufacture an elapsed-time breach.
Message oversight
Messages focuses on overdue, escalated, complaint, unassigned, and AI-review conversations across linked accessible locations. Filters can narrow by venue, channel, status, urgency, assignee, unanswered age, and AI-review state.
Opening a row shows a read-only conversation preview. Open source conversation takes staff to the original venue inbox to reply. Privileged group roles can assign, escalate, resolve, or hand an oversight item back to the location.
Note
Group message oversight does not send replies. Staff still reply from the source venue inbox.
Group settings and navigation
The group shell separates daily work from lower-frequency administration:
- Run: Today, Performance, Operations.
- Manage: Brand standards, Policies, People, and Finance where the role permits them.
- Group menu: Group settings, implementation details, audit access for privileged roles, public booking page actions, and the exit back to the source venue workspace.
Group settings show linked locations with exact venue-management links, shared booking/storefront identity for owners, and operations thresholds. The old checklist and health-setting controls are retained only for compatibility and are no longer part of the command-centre UI.
Common mistakes
Assuming every grouped venue can be consolidated. Group reports can block when selected locations use mixed currencies, lack PRO access, or are unavailable to the group.
Replying from group message oversight. The preview is read-only. Use Open source conversation to reply from the venue inbox.
Treating task completion as issue resolution. A task records follow-up work. The issue remains live until the source condition clears.
Assuming every warning has an elapsed age. The UI only shows age and SLA breach state when the source supplies reliable timing data.
Using Operations to reply or change venue settings. Operations is an internal coordination surface. Reply in the source venue and use the linked venue settings page for location changes.
Troubleshooting
| Issue | Solution |
|---|---|
| You do not have access to group reporting | Return to All locations, confirm the group admin console is enabled, and check that every selected location has PRO access. |
| Mixed currencies cannot be consolidated | Select locations that use the same currency before opening consolidated reports. |
| Selected scope includes a non-PRO location | Remove the non-PRO location from the selected scope or upgrade the location. |
| Group inbox unavailable | Click Retry. If it still fails, confirm the group is inside the enabled rollout and your account has inbox oversight permission. |
| Operations are unavailable | Click Retry or return to Today. Confirm operations controls are enabled for the group. |
FAQ
What is the Group Command Centre?
The Group Command Centre is the All locations workspace for enabled groups. Today supports the current operating decision, Performance combines comparison and reports, and Operations combines issues, messages, and tasks.
Who can use the Group Command Centre?
It is web-only and requires the group admin rollout gate plus an owner, regional manager, or location manager group role. Consolidated Performance reports also require PRO access for every selected location.
Can group inbox oversight reply to customers?
No. Group inbox oversight opens read-only conversation previews. Replies stay in the source venue inbox, and Open source conversation takes the operator back to the original venue conversation.
When does assigning an issue create a task?
Assigning a live issue creates or reuses one active task linked by a stable issue key. Completing the task does not hide the issue; it clears only after its source condition is resolved.