Skip to main content

Guide

How to monitor workspaces

Use Admin HQ workspace signals to review operational health, billing risk, owner approvals, and internal workspace activity.

Updated 2026-05-02For Owner, Manager

Admin HQ includes a workspace monitor for internal operators who need to review workspace-level queue, owner, commercial, and launch-readiness signals without entering the normal business app.

Open the right surface

Use /admin for Admin HQ. It is the internal command-center surface for platform operators, not the daily workspace dashboard for business users.

If you are trying to work leads, bookings, won/lost records, or business settings for a customer workspace, open the business app instead.

Read the KPI row first

Start with the top Admin HQ signals. They summarize whether the internal operating surface is stable before you inspect individual rows or cards.

  • Active Workspaces shows starter, team, and legacy demo signals.
  • Leads Processed helps operators understand demo or sales intake volume.
  • Billing Risk highlights commercial readiness, plan, entitlement, seat, or invoice pressure.
  • System and automation indicators call out operational warnings that need review.

Use the Workspace monitor section

The Workspace monitor section is for workspace-level queue, owner, and commercial state. Use filters and search before taking action so you do not confuse internal demo data with a real customer workspace.

  1. 1Review the workspace or queue summary.
  2. 2Check owner or assignment state before opening a workspace-related workflow.
  3. 3Look for commercial signals such as trial, starter, team, subscription, or seat pressure.
  4. 4Open the relevant Admin HQ workflow only when the signal needs operator action.

Signals that need attention

  • A workspace or queue has overdue demo activity.
  • Owner approvals are pending or blocked by seat capacity.
  • Billing risk is warning or critical.
  • A workspace is over seat capacity or would lose capacity after a downgrade.
  • System readiness or launch evidence is marked blocked.

Keep Admin HQ separate

Admin HQ is intentionally separate from the authenticated business AppShell. Do not use it as a replacement for owner, manager, or team-member workflows.

Platform operators should avoid exposing internal workspace notes, readiness evidence, or admin-only controls to normal workspace users.

Safe operating habits

  • Confirm you are in the internal HQ workspace before treating the page as an admin surface.
  • Use Admin HQ links for owner approvals, demo inbox, privacy ops, compliance, and settings when you need platform-level review.
  • Avoid adding sensitive customer details to operational notes unless they are required for the review.
  • When a signal relates to a customer workspace, verify the workspace identity before opening or changing anything.

Was this article helpful?

Your answer helps Cendaro improve launch documentation.