Screenshot Flow Coverage in-progress
This page tracks which user-visible flows have screenshot-backed guidance. It exists because the MFA work proved that a feature can be technically present but still not product-complete from a user journey point of view.
Rule
Do not call a user-facing feature complete until its happy, blocked, recovery,
and admin/ops support paths are visible in UAT or the user guide.
Coverage Matrix
| Flow | Persona | Screenshot status | Minimum screenshots |
|---|---|---|---|
| Sign in and choose context | user, admin | needed | login, tenant/project context, blocked access |
| MFA setup | user | partial | security page, setup action, provider setup, post-setup protected state |
| MFA manage/remove/recover | user, admin, ops | needed | manage state, recovery request, admin review, completed reset |
| Launch app/runtime | user | needed | catalog, launch config, active runtime |
| Connect to workload | user | needed | connection action, terminal/browser access, stopped/expired session |
| SSH key management | user | needed | add key, list keys, default key behavior, validation error |
| Storage | user | needed | bucket/object list, upload/download, quota/permission block |
| Billing | user, billing admin | needed | balance, usage, low balance, payment path |
| Tenant administration | tenant admin | needed | members, roles, project, service account |
| Platform operations | platform admin, ops | needed | IAM readiness, service versions, release/readback |
| Troubleshooting | user, ops | needed | no capacity, forbidden, stale status, support handoff |
Screenshot Capture Standard
Use real kind/dev/demo UI unless the page is explicitly conceptual.
Each screenshot-backed guide should capture:
- environment and URL family;
- source SHA or portal publication build;
- persona;
- preconditions;
- expected result;
- blocked/recovery behavior;
- UAT or manual evidence path.
Guide Structure
Every screenshot-backed page should use this pattern:
- what the user is trying to do;
- what they need before starting;
- screenshots for the happy path;
- screenshots for blocked or empty states;
- recovery path or support handoff;
- how admins/operators verify or repair the workflow.
Current Accepted Limitation
The portal can explain flows now, but full screenshot coverage is still being
filled in. Until each row in the matrix has screenshots, the portal should call
the user guide in-progress, not complete.