Launch checklist
Before launch, go through four checkpoints in order: technical items and real first-use acceptance.
Launch checklist
This page is the pre-launch checklist: first go through the four checkpoints, then check the technical items one by one, and finally do first-use acceptance with real accounts.
Go through the four checkpoints in order; do not check the next one until the previous one passes. Pass each checkpoint in both open modes, embed and new tab (unless open lists only one).
| Checkpoint | How it passes |
|---|---|
| ① Published | Approved, installed in the organization and active; target roles see the entry on the Apps page; the shell opens the expected URL {url}{sub-path}?theme=…&openmax_lang=… (see URL composition examples) |
| ② Authorization works | New tab: with no session it goes to the authorization endpoint and returns to redirect_uri with code / state / iss; it does not stop on an authorization page final state (APP_AUTHORIZE_*). Embed: gets a code from the host (no openmax:auth:error), and the iframe did not redirect (see "Sign-in when embedded") |
| ③ Session established | Token exchanged, id_token verified, org_id allowed, binding found / created per policy, native session created with lifetime ≤ token expiry |
| ④ Business pages work | All cases in "Real first-use acceptance" below pass |
Sign-in when embedded (requestAuthCode) and route sync (
openmax:location) are live. Do not rely on host prompts: apps that have not adopted requestAuthCode show a blank screen on iPhone / iPad / desktop Safari.
Technical items
- ☐ manifest passes validation (
versionisX.Y.Zand greater than existing versions); has apath: "/"entry; requests only the scopes it uses - ☐ Secret is configured only on the backend: never in the frontend, the repo or logs (do not log code, verifier or tokens either)
- ☐ Authorization requests include
state+nonce+ PKCE S256;redirect_urimatches the manifest byte for byte - ☐ Callback: flow is single use; check
issandstate; exchange the token withcode_verifier; verify the id_token (signature,iss,aud,exp,nonce) - ☐ returnTo is taken only from the server-side flow, and only a single path starting with
/is accepted - ☐
login_required/access_denied/ 401 / 403 end in a final state and never loop redirects automatically - ☐ embed: CSP
frame-ancestors(the Workspace originhttps://openmax.com), remove XFO DENY; cookies still used inside the iframe areSameSite=None; Secure; Partitioned - ☐ embed sign-in follows "Sign-in when embedded": no redirect inside the iframe, ask the host for an authorization code; send messages only to the Workspace origin (never
"*"), checkevent.source/event.origin/requestIdon replies;redirectUrimatches the manifest exactly, and the backend exchanges the token with the sameredirect_uri+code_verifier - ☐ Only
not_embeddedfalls back to redirect sign-in;host_timeout/timeout/busyat most 3 tries in total; other errors show an explanation + "Open in new tab" - ☐ embed sessions do not rely on third-party cookies: keep them in memory (or
sessionStorage) and send them in request headers; use short-lived tickets for sub-resources that cannot carry headers - ☐ With
offline_access, store the new refresh_token on every refresh - ☐ Data is isolated per organization; a 401 is treated as authorization lost
- ☐ Callback checks
org_id; binding is only by(issuer, org_id, member_id), never auto-linked by email - ☐ Session lifetime ≤ token expiry; expired sessions are blocked and re-authorized (re-checking identity is not renewal)
- ☐ Never use
theme/openmax_langfor auth or tenant decisions; routes tolerate these two parameters - ☐ The integration policy table (see "Integrating existing systems") is filled in and confirmed by an organization admin
- ☐ If you adopted route sync: under embed, refreshing the browser on a deep page stays on that page; callback / sign-in relay / one-time pages are not reported; messages go only to the Workspace origin, never
"*"
Real first-use acceptance
Run through this with real accounts on the target environment, not only the developer's own admin account.
| Case | Expected |
|---|---|
| A brand-new member opens it for the first time (no account in the app yet) | Policy A: one account is created automatically, role = default role, added only to the agreed default projects, lands on the first-use landing page; Policy B: sees "Please contact your admin to get access", and no account is created |
| An existing member opens it again (session expired) | Seamless re-authorization, back to the same account (no second account created), existing projects and data all there |
| Open via embed on iPhone (Safari or any browser), iPad, desktop Safari | No blank / black screen, enters the app with no interaction; still signs in seamlessly after refreshing the Workspace page; opening in a new tab works too |
| A second tab / open once in embed and once in a new tab | Both work; no duplicate accounts; embed and new-tab sessions do not affect each other (Partitioned cookies, see Open modes and URLs) |
| Default projects are correct | New members see only the agreed projects, not unrelated historical projects |
| No 403 on core pages | With the default role, open each core business page (lists, details, create / edit common objects): no 403, blank page or endless loading |
| No unexpected projects created | First entry does not trigger an onboarding wizard that auto-creates sample projects / workspaces; the total project count is unchanged |
| Sign out inside the app | Stays on the "Signed out" page (?signed_out=1), does not sign in again automatically; "Sign in again" brings you back |
| After signing out of Workspace | The app session lives at most until token expiry; after that, re-authorization shows "Please sign in to Workspace first", with no redirect loop |
| Authorization revoked (install disabled / removed from organization / account disabled in the app) | On the next Workspace API call (401) or re-authorization after session expiry (access_denied), shows no-access within 15 minutes at most, with no redirect loop; after re-enabling, opening again works normally and the account and data are still there |
For more pre-launch practice tips, see Release and versions.
