Audit export continuity
The launchpad is still part of the navigation-only audit-export relay: reopen the Latest export receipt from /settings?intent=upgrade, capture the filename, filters, and SHA-256, and keep that note attached as you move to verification, go-live, or the admin follow-up loop.
These CTAs keep the workspace context, but they do not automate follow-up, impersonate another user, or change readiness records on your behalf.
SaaS Workspace Launch Hub
Use this as the operator-facing launch state machine: confirm session/workspace context, inspect readiness and plan posture, then continue through the right manual lane for this workspace.
Workspace launch summarydefault
This launchpad is a navigation hub for manual governance follow-up. It does not impersonate users and does not trigger support automation.
Workspace
default
Loading workspace id...
Organization
Loading...
-
Plan
Unassigned
Billing status: Loading...
Updated
-
Delivery: loading
Onboarding baseline
Bootstrap baseline before moving to credential steps.
Context source: Environment fallback (non-production)
Source: onboarding checklist baseline flag.
Credentials
Create at least one service account and one API key.
Role scope: platform_admin
Source: onboarding checklist credential flags.
Demo run
Run a first demo flow to produce run/trace evidence.
Source: onboarding run checklist and latest demo state.
Billing posture
Billing posture is not currently warning.
Source: workspace billing summary tone/status.
Mock go-live readiness
Complete verification and clear billing/demo prerequisites first.
Source: delivery track plus onboarding/billing status.
Onboarding recovery lane
Keep the latest demo run, verification evidence, and go-live rehearsal aligned with the current onboarding state.
Follow the guided onboarding lane
Bootstrap providers and policies before credential setup.
Manual launch state machine
Follow one operator-owned lane from session confirmation through evidence relay.
Step 0
Confirm session and workspace context
Verify the active identity, workspace, tenant, and context source before touching onboarding, billing, or evidence surfaces.
Step 1
Bootstrap baseline and credentials
Keep provider/policy setup, service accounts, and API keys attached to the same workspace story.
Step 2
Run the first governed flow
Create a real run, then confirm the usage signal before widening scope or inviting more pressure.
Step 3
Relay evidence and rehearse go-live
Capture verification notes, review settings when needed, rehearse mock go-live, then return to the right queue or readiness focus manually.
This hub is still navigation-only. It does not provision on your behalf, send invitations, or enforce plan gates automatically.
Plan and usage checkpoint
Keep Week 6 plan posture visible before the first run or before widening scope.
Usage has not accumulated yet for the current period. Keep this checkpoint in the loop so the first governed run has a clear billing and plan story.
Recommended next step
Use this as your primary handoff target, then continue with the rest of the navigation surfaces.
Role/session-aware lane
Confirm workspace governance settings
Admin lanes should confirm policy, billing posture, and rollout safeguards first.
Role: admin · Context source: Environment fallback (non-production)
Session/context checkpoint
Confirm the active workspace session before deeper changes
Week 3 depends on session-backed workspace routing. Check identity, roles, and accessible workspaces before onboarding, billing review, verification updates, or the mock go-live drill.
Current role scope: platform_admin · Context source: Environment fallback (non-production)
Trusted session guidance still applies here: only carry this lane forward if the session page confirms a metadata-backed workspace context for the same workspace you plan to onboard, measure in usage, and cite in verification or go-live evidence.
Returning to Session is the safe fallback whenever a workspace feels off. That is cheaper than cleaning up keys, billing actions, or evidence attached to the wrong tenant later.
Current blockers
- Baseline providers and policies are not ready.
- Service account is missing.
- API key is missing.
All launch surfaces
Loading workspace and delivery context...