The dashboard is the owner’s control center. It should show what WatchTower knows now, what changed recently, which locations are protected, which machines are online, which alerts need attention, and what paid features are active.
Dashboard layout goals
A good WatchTower dashboard should be fast to understand. Owners should not have to dig through logs to know whether their land is covered. The top of the dashboard should show the health of the account and the newest important items.
Recommended dashboard summary cards:
| Card | Meaning |
|---|---|
| Locations Online | Number of active protected locations with recent terminal updates. |
| People Seen | Recent avatar presence count, with freshness indicators. |
| Alerts | Open alerts or rules needing owner review. |
| Region Health | FPS, time dilation, lag score, and stale-data warnings. |
| Subscription | Plan, paid-through date, add-ons, and location usage. |
| Machines | Terminal objects, Payment Stations, relays, and other WatchTower machines. |
Freshness matters
Every live card should show when the data was last received. A count without a timestamp can be misleading. A location that showed 12 visitors an hour ago should not look the same as a location showing 12 visitors right now.
Recommended freshness states:
| State | Suggested meaning |
|---|---|
| Live / Fresh | Received within the expected update window. |
| Recently seen | Slightly delayed, likely still normal. |
| Stale | No recent update; terminal or region may be offline. |
| Offline | No data for a longer period or token not active. |
| Needs review | Data exists but the system is unsure how to match it. |
Command Center
The Command Center is the owner’s main action panel. It should not be cluttered with every raw log. Instead, it should focus on current decisions:
- Which location needs attention?
- Which alert fired?
- Which avatar, if any, is involved?
- Which rule triggered?
- What action is recommended?
- Is the action safe, available, and permission-supported?
- Does a staff member need to review it first?
Actions from the Command Center should use clear labels such as **Warn**, **Eject Attempt**, **Ban Attempt**, **Unban Attempt**, **Open Ticket**, **Mute Alert**, **Assign Staff**, **Mark Reviewed**, or **View Logs**.
Locations page
The Locations page should show each protected location as a real-world owner would think of it: store, club, rental area, event floor, or parcel. It should not only show terminal UUIDs. Include region name, parcel name, location nickname, SLURL, online state, last heartbeat, plan usage, and whether the location counts against the subscription.
Recommended columns:
- Location name
- Region
- Parcel
- Online/stale/offline state
- People seen recently
- Region health
- Active machine count
- Last update
- Plan usage state
- Actions
Machines page
The Machines page is the technical inventory of WatchTower objects. It helps owners and support identify terminals, payment stations, chat relays, or other WatchTower parts.
Machine states should be simple:
| State | Meaning |
|---|---|
| Online | Recently reported and token is valid. |
| Stale | Has not reported recently. |
| Offline | Token missing, reset, expired, or no recent data. |
| Duplicate | Looks like another object/location already exists. |
| Needs Review | Owner/account/location match is unclear. |
Alerts page
The Alerts page should show owner-important events, not every small telemetry update. Examples include terminal offline, location over limit, payment issue, region performance problem, watched avatar seen, security action failed, Discord delivery failure, adult gate issue, or scanner data stale.
Every alert should include:
- Title
- Severity
- Location
- Time triggered
- Last update
- Rule or source
- Recommended action
- Current state: open, acknowledged, muted, resolved, or escalated
Demo site
The demo site should show the dashboard flow using safe example data. It should not require a live terminal or real owner account. Demo data should clearly be marked as demo data so customers do not think the sample locations are their land.
Good demo examples:
- One online store location
- One stale club location
- A few visitor rows
- A sample region-health card
- A sample alert rule
- A sample billing status
- A sample Payment Station event
- A sample Discord alert preview
Daily owner workflow
A normal daily check should take under five minutes:
- Open the dashboard.
- Confirm locations are online.
- Check open alerts.
- Review recent visitors or watched avatar events if needed.
- Confirm region health is normal.
- Check billing/add-on status if any feature is locked.
- Respond to support tickets or staff notes.
The dashboard should be useful even when nothing is wrong. A quiet dashboard should clearly say that the protected locations are healthy instead of making the owner guess.