User Journeys

AI Cloud documentation starts from the task a person is trying to finish.

End User

Step	Goal	What good looks like
Sign in	Reach the product with the right tenant and project selected	The top bar shows the expected tenant and project.
Secure account	Add account protection and access keys	MFA, SSH keys, API keys, and sessions are visible in account settings.
Choose capacity	Pick compute or an app runtime	The catalog shows available runtime families and cost posture.
Launch	Start a runtime in the current project	The runtime moves from provisioning to active.
Connect	Open terminal, SSH, notebook, IDE, scheduler, or endpoint route	The connect action lands on the expected work surface.
Operate	Watch state, usage, storage, and spend	The user can understand health, hourly burn, and next action.
Release	Stop using capacity when finished	Billing stops and cleanup state is visible.

Tenant Admin

Step	Goal	What good looks like
Tenant setup	Confirm tenant name, workspace, and default project	The tenant has a usable project and visible admin context.
Project lifecycle	Create and review project ownership	Projects have clear names, roles, and lifecycle state.
Membership	Add users and assign least privilege	Members can use only the projects and roles they need.
Service accounts	Create automation identities	Credentials are scoped, rotatable, and auditable.
Quota and spend	Control capacity and budget exposure	Admins can see balance, quota, burn, and blocked states.
Access review	Remove stale access	Drift, stale members, and risky credentials are visible.

App Developer

Step	Goal	What good looks like
Pick runtime family	Decide scheduler, compose, notebook/IDE, or inference endpoint	The runtime model matches the user workflow.
Define manifest	Describe launch, health, connect, storage, and cleanup	The manifest is reviewable before packaging.
Package artifact	Build the image or runtime bundle	The artifact has digest, version, and trust state.
Test lifecycle	Prove launch, status, connect, and release	The app can be operated without special workarounds.
Promote	Make the app available to users	Users can launch it through the product catalog.

CLI And API Consumer

Step	Goal	What good looks like
Authenticate	Use bearer auth safely	Tokens are never placed in URLs or logs.
Set context	Send tenant/project context where required	API calls operate on the intended project.
Mutate safely	Use idempotency keys	Retries do not create duplicate work.
Handle errors	Use stable error codes and correlation IDs	Support can trace an issue without private data.
Automate	Prefer CLI or generated SDKs	Automation follows the same contracts as the UI.

When To Contact Support

Contact support with the visible correlation ID when:

• an access-denied state does not match your expected role;
• capacity remains unavailable after choosing another SKU or region;
• release or cleanup does not complete after retry;
• a route or connect action fails after the workload is active;
• billing or quota state does not match expected usage.