Guided onboarding Blueprint generation → approval → provisioning token → launch setup
Updated flow
Commonshub guided onboarding
Latest ruleset flow from first landing through provisioning handoff and dashboard setup.
Console mockup
Phase: Approval + provisioning handoff
~8–12 min to Blueprint
1. LandingStart with admin email, focus, and public links.
2. Guided decisionsPositioning, name, address, header line, and owner identity.
3. Approval + tokenBlueprint locked, provisioning token issued, final URL confirmed.
4. Launch setupOpen guided dashboard renderer for platform-specific setup steps.
Console · latest Jason-style onboarding path
Mastodon 4.5.7 setup target
Commonshub · Session startStep 0

Hi — ready to design your community?

First, what email should own the server? This is where we’ll send your login link when it’s live.

Admin email: jason@jaysonjaysmart.com

Commonshub · IntakeFocus

Core focus: STRATEGY, NATIONAL SECURITY, & REPUTATIONAL POLITICS.

Links: jasonjaysmart.com · YouTube · Substack · Kyiv Post

Step 1 · Community PositioningApproved

Selected: A working room for researchers, journalists, and operators analyzing power, propaganda, and geopolitical strategy.

Short description: A working room for researchers, journalists, and operators tracking geopolitical power, propaganda, and strategic conflict in real time.

Step 2 · Community NameCustom final

Locked: The Security Brief

Instance slug: securitybrief

Step 3 · Community AddressApproved

Locked: securitybrief.jasonjaysmart.com

Domain type: External subdomain — brand continuity

Step 4 · Header LineApproved

Locked: Real-Time Security Briefings

Step 5 · Owner ProfileApproved

Locked: jasonjaysmart

Owner handle: @jasonjaysmart@securitybrief.jasonjaysmart.com

Blueprint · CompleteSaved
Community Blueprint
  • Community name: The Security Brief
  • Slug: securitybrief
  • Domain candidate: securitybrief.jasonjaysmart.com
  • Header line: Real-Time Security Briefings
  • Owner handle: @jasonjaysmart@securitybrief.jasonjaysmart.com
Provisioning handoff · Resume-safeNew

Your Blueprint is saved. A private provisioning token is generated so the owner can return later, confirm the final URL, and continue into provisioning without rerunning onboarding.

Provisioning token: cs_live_demo_8X4K2Q_securitybrief

Final confirmation · URL checkRequired before provisioning

Before provisioning begins, confirm the final URL choice. If the preferred URL is unavailable, the system suggests alternatives and preserves the original candidate in the Blueprint.

Next screen: platform-aware launch setup dashboard Missing flows by design: plan purchase and Stripe account setup

What this mockup now reflects

Latest onboarding ruleset

Email → focus → links → 5 identity steps → Blueprint → proceed gate.

Provisioning token handoff

Return-safe token generation with final URL confirmation before provisioning begins.

Dashboard renderer path

After confirmation, the owner lands in guided setup tied to platform defaults and Blueprint content.