​
Dashboard Overview

Once connected, the WordPress integration screen becomes a lightweight control surface for the pairing. The layout has two main areas:
  • the main panel with connection details and settings
  • the Quick Actions sidebar with site status data from Watchman Tower

​
Connection State

The connected view shows:
  • a green Connected badge
  • the local instance ID
  • the paired site ID
  • Last Successful Heartbeat
  • Last Error when the latest attempt failed

​
Instance ID

The instance ID is generated locally by the plugin and stored in wthb_instance_id.
The plugin generates this value with WordPress UUID helpers when available. It should be treated as an internal identifier, not as a fixed human-formatted code.

​
Site ID

The site ID is the Watchman Tower-side identifier returned after pairing. It is stored inside wthb_options and used for later authenticated traffic.

​
Quick Actions Sidebar

The Quick Actions panel loads the latest site snapshot from Watchman Tower. It can show:
  • current site status
  • uptime percentage
  • downtime percentage
  • domain name
  • registrar
  • remaining domain days
  • SSL issuer
  • SSL days left
  • certificate chain trust state

​
View Dashboard

The View Dashboard button opens the site directly in Watchman Tower: 
https://app.watchmantower.com/monitoring/{site_id}

​
Settings Area

The connected screen includes three active controls:
  • Heartbeat Interval
  • Pause heartbeat monitoring
  • Save Settings
There is also an Unlink Site action for removing the pairing.
The current connected screen does not expose a separate Send Heartbeat Now button. Connection checks and settings sync happen through the existing plugin actions.

​
What the Dashboard Is For

Use the connected screen to:
  • confirm the site is paired
  • see when the last successful heartbeat arrived
  • adjust interval and pause state
  • open the full Watchman Tower dashboard
  • unlink the site when needed

​
What the Dashboard Is Not

This screen is not a full analytics workspace. It does not replace the web dashboard for:
  • historical incident review
  • alert routing
  • broader site monitoring workflows
  • team-level operational context

​
Next Steps