Start Here

AI Cloud has three common entry paths.

I Am A User

Use this path when you need to run work.

1. Sign in.
2. Confirm the tenant and project in the top bar.
3. Review account security and complete required MFA.
4. Add an SSH key if the runtime needs SSH.
5. Open Workloads, Compute, or Apps.
6. Launch the approved runtime.
7. Connect, monitor usage, and release it when finished.

Continue with Quickstart, then Launch Compute or Launch And Operate.

For a complete first-day procedure with account setup, launch, connect, release, CLI, SDK, and troubleshooting steps, use AI Cloud User Guide.

To see the full current surface before choosing a path, open Platform Capabilities.

I Am A Tenant Admin

Use this path when you manage access, projects, service accounts, and spend.

1. Confirm tenant context before changing access.
2. Review projects and project ownership.
3. Add or remove members with least privilege.
4. Create service accounts only for automation that needs them.
5. Review quota, billing, account-security posture, and stale access.
6. Prepare a support handoff path before broad user rollout.

Continue with Tenant Administration.

I Am Building Or Automating

Use this path when you package an app, integrate with APIs, or automate workflows.

1. Choose the runtime family: scheduler, compose, notebook/IDE, or inference.
2. Define the app manifest or integration workflow.
3. Use tenant and project context consistently.
4. Use idempotency keys for retryable mutations.
5. Handle structured errors and correlation IDs.
6. Prove launch, status, connect, and release before handoff.

Continue with App Developer Guide and CLI And SDK Guide.

What To Learn First

Topic	Why it matters
AI Cloud User Guide	Complete task-based procedure for users, tenant admins, and developers.
Platform Capabilities	Inventory of current UI, CLI, SDK, API, service-account, app, billing, and storage capabilities.
Tenant and project	They decide where access, spend, and runtime ownership land.
Resource hierarchy and roles	It explains ownership, billing group, project role, and support owner.
Quickstart	It shows the shortest first-use path and success criteria.
Runtime family	It determines launch inputs, connect actions, and cleanup behavior.
Account security	MFA, sessions, SSH keys, and API keys protect access to capacity.
Billing and quota	Long-running workloads consume balance, entitlement, and capacity.
Correlation ID	Support uses it to trace an issue without secrets.

If You Get Stuck

Use Troubleshooting Playbook before escalating. It tells you the likely owner and the evidence packet to send.