Launch Readiness
Confirm what must be ready before internal or customer launch.
Use this page before opening a workspace to internal teams, customer traffic, or a new feature rollout.
Readiness is an operating diagnostic for the selected workspace. An app task guide checks only that app task. Check billing, ownership, moderation, and Commerce payment readiness here; configure connections in Shared payment settings. Review the current Console results and the owners on this page before launch.
Item States And Overall Status
Items use ready, todo, blocked, attention, optional, and unknown, with required or recommended severity. unknown means the check could not establish readiness; it is not a success. The overall status is decided in this order:
| Condition | Overall status |
|---|---|
Any required item is neither ready nor optional | blocked |
| Otherwise, any item is unresolved | attention |
| Otherwise | ready |
For billing, when the plan source is a subscription, past_due, expired, and suspended produce a blocked item. canceled produces an attention item. Billing is required, so that attention item still makes the overall result blocked. Keep subscription state, item state, and overall status distinct.
Plan-blocked selections, Secret Key setup, team ownership, webhooks, and occurrence sellability are recommended diagnostics; a recommended blocker can make the overall result attention without increasing required blocking. Assess whether each applies to your launch.
A Secret Key is needed for privileged server integrations, not every public-read app; a webhook registration is needed only for workflows that use it.
Open diagnostics for the selected workspace from Settings → Workspace → Operations → Diagnostics. All four roles can find it in Settings and Cmd+K before and after readiness completes. Session conversion and tool-call-to-write conversion in the AI tool connections (MCP) section are shown to super-admin. Platform AI tool connection totals and links to audit logs and webhook deliveries are available above the Workspaces list for super-admin.
Console Diagnostics lists blocked checks and checks needing attention or setup before ready checks. Each check appears once in the readiness list. Workspace administrators and super-admins see integration key management shortcuts and webhook delivery history links. Optional checks use a neutral gray tone.
Readiness Categories
| Category | Ready means | Stop when |
|---|---|---|
| workspace | identity, owner, and team access are clear | no admin owner or stale access remains |
| features | at least one selected feature is effective | selected features are plan-blocked |
| keys | Publishable Key, CORS, and Secret Key ownership are clear | browser origins or key ownership are missing |
| billing | plan and subscription state are usable | subscription is past due, suspended, expired, or unclear |
| content | enabled areas have minimum real content | enabled areas are empty or unowned |
| webhooks | owners know where delivery failures appear | failure ownership is unclear |
| team | tenant-admin memberships have operating owners | no admin exists; a single admin needs attention |
An expired subscription has ended, for example when a scheduled cancellation takes effect at the end of the billing period.
Commerce Payment Connections
When Ecommerce is effective, the required commerce.paymentConnection item checks managed connections together with enabled custom providers for every active market.
| Situation | Item state | Next action |
|---|---|---|
| Saved secrets cannot be decrypted by this deployment | blocked | Rotate each connection credential, then check configuration and activate it |
| No connection is eligible for new payments | blocked | Complete configuration checks and activate a connection, or enable a custom provider |
| Some active markets have no selectable provider, or there are no active markets | attention | Assign markets and check for duplicate connections for the same provider and market |
| A lookup fails | unknown | Retry and inspect payment settings |
| Every active market has a selectable provider | ready | Continue the launch checklist |
Managed connections need the current credential generation and configuration checks accepted for new payments. Custom providers need explicit enablement and market membership. An active connection with no markets remains available in shared settings and needs attention for Commerce. Each managed provider needs exactly one eligible connection per market to be selectable.
Managed connections must also match the selected workspace's payment environment policy. PortOne needs at least one usable Hosted or Standard V2 configuration; Standard V2 checks its redirect origin against the workspace's current allowed origins. A valid Hosted configuration remains usable when the Standard redirect origin is removed.
Currency support remains a checkout-time check.
Workspace administrators and super-admins can open the payment connection list from this item. Since the item is required, attention and unknown also block overall launch readiness.
Feature setup, 01 feature check ecommerce, and MCP check-feature-progress check connection eligibility and market coverage in the required payment.connection item:
| Connection check | Feature progress state |
|---|---|
| No eligible connection | incomplete |
| Missing market coverage or no active markets | attention |
| Lookup failed | unknown |
| Full coverage | complete |
The first three states keep feature progress from reporting ready. Evidence contains only the verdict. Ask a workspace administrator to complete configuration checks, activate a connection, and assign providers to every active market.
The workspace readability probe does not change saved state. The connection panel also shows “Action required” and disables its activation button. Lock or infrastructure failures remain unknown. Feature progress polling does not run this probe; check saved-secret readability in the connection panel or workspace diagnostics.
Default Shipping Policy
For a workspace that ships products, configure shipping rate rows or a free-shipping condition on an active default policy. Both readiness views use the cart shipping calculation: the policy must provide shipping lines or a free-shipping condition in active market currencies.
| Situation | Item state | Next action |
|---|---|---|
| The active default policy provides usable shipping rates or a free-shipping condition | ready | Check shipping with actual order amounts and destinations |
| The default policy has only a zero base amount without rates, or all rate rows are inactive | todo | Add shipping rate rows or a free-shipping condition |
| There is no active default policy or active market | todo or attention | Set the default policy and activate a market |
| Policy or market lookup fails | unknown | Retry and check shipping settings |
An explicit zero-amount rate row is usable. Rates for the first cart addition must apply before a destination is selected. Conditional rates and free-shipping thresholds are checked at their configured order amounts, so test the order amounts and destinations you will sell to before launch. Workspaces without shipping omit this item.
Launch Checklist
- owner and admins are current
- effective features match the launch scope
- required content or commerce records exist
- if admission types are configured, review the recommended occurrence sellability diagnostic
- CORS, keys, and webhooks have owners
- billing state is not blocking
- support and moderation responsibilities are assigned
Stop Conditions
Pause launch when any required item is blocked, when plan-blocked features are still part of the launch promise, or when nobody owns customer-facing failures.
Treat readiness blockers as launch blockers. Fix the owner, feature, key, billing, content, or support gap before expanding exposure.
Next Actions
- If access is unclear, return to Workspace Setup.
- If features are blocked, return to Feature Planning.
- For credential ownership, return to Integrations & Keys; for browser API origin setup, follow Deploy.