This path is for people consuming the platform: users launching GPU capacity,
customer admins managing tenant/project access, and teams tracking usage,
storage, and billing.
Task Routes
Persona Routes
| Persona | First-read path | Decision points | Next-action pages |
|---|
| End user | User Journeys, Account and Access, Launch and Operate | Do I need sign-in help, MFA, SSH/API keys, capacity launch, terminal access, or release guidance? | Start with account/access, then launch/operate, then use troubleshooting for failures |
| Tenant admin | Tenant Administration, Billing and Storage, Security Readiness | Do I need project/member governance, budget/spend awareness, access policy, or audit/review context? | Review tenant-admin flows first, then billing/storage, then security/readiness gaps as needed |
What This Section Must Achieve
| Reader | Must be able to answer quickly |
|---|
| End user | How do I sign in, protect my account, launch work, connect, and recover from problems? |
| Tenant admin | How do I manage workspace access, budgets, and escalation paths without reading internal architecture docs? |
| Product reviewer | Are the documented user flows complete enough to claim the UX is actually ready? |
First User Journey Checklist
- Sign in, understand tenant and project context, and find available capacity.
- Launch a GPU node, slice, or managed app from the catalog.
- Connect through browser terminal or SSH according to the active access policy.
- Attach storage, move data, and monitor workload state.
- Understand usage, credits, billing, budgets, and low-balance alerts.
- Troubleshoot common states such as provisioning, active, releasing, failed, and release failed.
User Guide Rule
This section should be navigable by task, not by implementation vocabulary. If
the reader needs to know how the backend or provider is arranged in order to
finish a normal task, the user route is still incomplete.
Pages