Skip to content

article

Navigate your workspace dashboard

A guided tour of the Dashboard — the hero quick-actions, at-a-glance metric cards, the app launcher, recently-used apps, and the shortcut links along the bottom.

What the Dashboard is for

The Dashboard is the page you land on when you sign in and whenever you select the workspace logo or Dashboard in the left rail. It's a control room, not an app: it gives you a snapshot of your workspace and fast ways to jump into the work. Its route is the workspace root (/).

The hero and quick actions

At the top, a header labeled Client control room / Workspace dashboard introduces the page and, on the right, shows a small panel with your account name and your active organization ID. This is a handy place to confirm you're in the right workspace before you start.

Alongside it are quick-action buttons:

  • Open App Launcher — jumps to the full My Apps catalog.
  • Manage StretchWP — opens your managed WordPress sites.
  • Support — opens the support intake so you can file a request.

The metric cards

Below the hero, three stat cards give you at-a-glance numbers:

  1. Apps — how many apps are available to this workspace.
  2. StretchWP sites — how many starter WordPress sites are attached.
  3. Launch pipeline — how many sites are approved, queued, or provisioning (that is, on their way to live).

These are quick health checks, not clickable reports — use them to decide where to go next.

The app launcher and recently used

The middle of the Dashboard hosts the app launcher, split into two parts:

  • Recently used — the last apps you opened, so you can jump straight back. If you haven't opened anything yet, this shows a featured set instead (CRM, Books, Tasks, Schedule, Calendar, Meet, Projects).
  • App launcher — the full grid of your apps, each with a short description and an Open app button.

This is the fastest place to launch something when you're already on the Dashboard.

Next to the launcher, a Starter site status card summarizes your StretchWP sites — how many are live or provisioned and how many are still in the pipeline — with a Manage link.

Along the bottom, a row of feature links takes you to the workspace essentials:

  • StretchWP — manage starter WordPress sites.
  • Services — track active work and requests.
  • White Label — plan branding and reseller identity.
  • Domains — attach custom URLs.
  • Support — submit a request.

A quick example

You sign in to Payne Coaching. The metric cards show 26 apps, 2 StretchWP sites, and 1 in the launch pipeline. You glance at the hero panel to confirm the active organization is Payne Coaching, then select Recently used › StretchCRM to pick up where you left off. Later you use the bottom Support link to file a quick billing question — and because you launched it from inside the workspace, the request already knows which organization it's for.

Tips

  • Treat the hero panel as your "you are here" sign. The account name and organization ID confirm context before you make changes.
  • Use Recently used for daily work; use the App launcher to discover. The first gets you back to routine tasks; the second helps you find apps you rarely open.
  • The three quick-action buttons cover 80% of first clicks. App launcher, StretchWP, and Support are deliberately one tap away.

Troubleshooting

"The metric cards all show 0." A brand-new or empty workspace legitimately has nothing to count yet. If you expected sites or apps, confirm you're in the right organization (top-bar breadcrumb and the hero panel's organization ID).

"Recently used shows apps I don't remember opening." When your history is empty, the panel falls back to a featured set — those are suggestions, not your actual history. Once you open apps, your real history replaces them.

"My StretchWP numbers look wrong." The pipeline count only includes sites that are approved, queued, or provisioning. Live sites are counted separately. Open Manage StretchWP for the full breakdown.

Was this helpful?

Help us improve this article

Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.