Find and open your Cloud project
Find the correct Cloud organization and project, and distinguish access errors from a stopped workspace.
Find the correct workspace
Open Cloud from the official website and sign in. Check the selected account and organization before looking for a project. A personal workspace and a team workspace can contain different projects even when you use the same browser.
Open the project from the Cloud navigation. If a saved link reports that the project is missing, return to the project list and check its current name and location instead of editing identifiers in the URL.
Access denied is a permission check
If a project is visible but cannot be opened, ask its organization administrator to confirm your active membership and the intended project access. Being signed in, having a subscription, or knowing a project URL does not by itself grant access.
If an invitation was sent to a different email or provider identity, use the intended account or ask the administrator to correct the invitation. Do not send passwords or session cookies to an administrator or another team member.
A stopped VM and a missing file are different problems
Check the status shown by the workspace. A stopped or disconnected execution environment can affect tools that need a running backend. Review any usage information shown before starting or resuming compute.
If the editor opens but a file does not, note its project-relative path and error text. Some workbenches have different availability in Cloud and desktop; check the current product documentation. A visible editor or circuit draft does not imply that a simulation or backend job has run.
When to contact support
Report the approximate time, browser, project name or identifier if appropriate for a private ticket, and whether the failure happens while listing projects, opening a file, or starting a tool. Redact secrets and private source code. Include a minimal reproduction instead of a full workspace archive.