Skip to content

Manage projects

A project groups diagrams, workspaces, members, provider defaults, policies, runs, and related activity under one ownership boundary.

Typical time
5–10 minutes
You need
Project access
Outcome
A reviewed project list or update
  1. Open Projects.
  2. Enter a name in Search projects….
  3. Narrow the page with Environment, Provider, Status, and Visibility.
  4. Choose Clear filters to restore the unfiltered page.
  5. Use the page-size selector and Previous or Next to move through results.
  6. Choose Refresh projects to request the latest permitted page.

Search and filters refine the loaded list. Pagination and refresh request bounded backend pages; the cursor itself is never displayed.

Projects 1 of 5 · Screenshot placeholder

Search and filter the project list

Show Search projects, the four filters, Clear filters, Refresh projects, and Previous/Next pagination.

Future capture briefUse synthetic project rows. Remove member names, IDs, repository details, provider account details, and real environment names.

Every visible row matches the selected filters, and the pagination summary describes only the current bounded page.

  1. Choose Create Project to start a new project.
  2. Complete the guided project details and review before creation.
  3. If an existing project has incomplete setup, open its actions and choose the available setup action rather than creating a duplicate.
  4. From project details, choose New Workspace or Create workspace to continue setup under that project.

Creating a project and workspace are backend mutations and require write permission. Follow Create your first project and Set up a workspace for their full review steps.

  1. Choose Open on the row, or open the action menu and choose Open project.
  2. If the project has several workspaces, choose one in the workspace picker.
  3. ScrinCloud opens the saved destination for that workspace, such as Architecture Studio or the Terraform code editor.
  4. Choose View details to inspect provider, environment, members, workspaces, latest run, and project metadata without editing.
  5. In the details drawer, use Copy project ID only when a trusted support or integration workflow requires it.
  6. Choose View runs to open the project’s run history.

Opening a project, viewing details, viewing runs, choosing a workspace, and copying the ID are read or navigation actions. Copying puts the identifier on your local clipboard; treat it as tenant context even though it is not a secret.

Projects 2 of 5 · Screenshot placeholder

Review project details and available actions

Show View details with New Workspace, View Runs, Edit Project, Delete Project, and Copy project ID.

Future capture briefUse a synthetic project. Redact IDs, members, account connections, repository URLs, run IDs, and timestamps that identify a tenant.

The drawer title and project metadata match the row you selected. Opening the project keeps you inside the same project and selected workspace.

  1. Choose Edit project.
  2. Review the Project details, Defaults, and Review changes steps.
  3. Change only the fields you intend to update.
  4. Choose Continue between steps and inspect the final summary.
  5. Choose Save changes.
  6. If the change is classified as high impact, review Save high-impact project changes? and confirm only when the provider, environment, region, visibility, and downstream impact are correct.

Saving creates a backend update. Some provider choices may be locked after dependent resources exist. A concurrency warning means a newer project revision must be reloaded and reviewed before retrying.

Projects 3 of 5 · Screenshot placeholder

Review project changes before saving

Show the edit steps, changed-field review, Save changes, and the high-impact confirmation when applicable.

Future capture briefUse harmless synthetic changes. Do not show identities, repository details, cloud identifiers, policy content, or real production values.

Reopen View details and confirm the saved fields and latest revision match your intended change.

  1. Open the row menu or details drawer and choose Delete project.
  2. Read Delete project? and confirm you selected the correct project.
  3. Verify your team’s retention and cleanup requirements.
  4. Choose Delete project and wait for completion.

Deletion is destructive and requires project administration permission. It removes the project from the accessible list; it is not a substitute for destroying or verifying external cloud resources.

Projects 4 of 5 · Screenshot placeholder

Confirm the project deletion impact

Show Delete project? with the synthetic project name, impact message, cancel action, and Delete project confirmation.

Future capture briefUse a disposable non-production project. Exclude customer names, IDs, cloud resources, members, and repository details.

The deletion notification completes and the project no longer appears after Refresh projects.

Project list and detail screens prove saved application state only. They do not prove that a Terraform run, deployment, cloud cleanup, or provider-side change completed.

Projects 5 of 5 · Screenshot placeholder

Confirm the resulting project list

Show the filtered project list after a create, edit, or deletion has completed and the refresh control is idle.

Future capture briefUse synthetic non-production rows and hide all tenant, member, cost, run, repository, and provider-account identifiers.

You may have read-only project access. Ask a project administrator for the smallest role that supports the required action.

Choose the workspace whose environment and destination you intended. Cancel if you cannot identify a safe choice.

Reload the latest project state, reapply only the intended change, and review again. Do not overwrite a teammate’s update blindly.

Wait for deletion to finish, then choose Refresh projects. If it remains, record the visible error and do not repeat the destructive request.