Skip to content

Create your first project

A project is the home for one product, platform area, or infrastructure initiative. It keeps the people, workspaces, diagrams, Terraform history, policy evidence, and cost context for that initiative together.

Typical time
5–10 minutes
You need
Project creation access
Next step
Invite team members

Before opening the form, write down:

  • a short project name that teammates will recognize;
  • one sentence describing the system or initiative;
  • the primary cloud provider for the first workspace;
  • the default environment;
  • who should see the project; and
  • a few useful tags such as a team, product, or cost-centre label.

Example:

Field Beginner-friendly example
Project Name Customer Portal
Project ID customer-portal
Description Cloud infrastructure used by the customer portal team.
Provider Amazon Web Services
Project Access Private
Default Environment Development
Tags customer-experience, web-platform

Do not put credentials, customer records, private account numbers, or incident details in the name, description, ID, or tags.

  1. Sign in to the correct ScrinCloud organization.
  2. Open Projects from the product navigation.
  3. Choose Create project.
  4. Confirm that the four guided steps appear: Project details, Cloud provider, Access & defaults, and Review.

If Create project is missing, your role may not allow project creation. Ask an organization administrator to create the project or adjust your access.

  1. In Project Name, enter the human-readable name.
  2. Review the generated Project ID.
  3. Change the ID only when your naming standard requires it.
  4. Add a short Description that explains the project purpose.
  5. Check Create readiness. Project details should show as complete.
  6. Choose Continue.

The Project ID is a stable, URL-safe identifier. Use lowercase words separated by hyphens. Avoid environment names in the project ID because environments belong in workspaces.

Project 1 of 4 · Screenshot placeholder

Complete Project details

Show the project name, generated Project ID, description, and Create readiness panel before continuing.

Future capture briefCapture the Create project form on Project details with synthetic example values. Keep the four-step progress row and readiness panel visible.

The first progress card should show the project name or indicate that the details are ready. Continue should be enabled.

  1. Select Amazon Web Services or Microsoft Azure.
  2. Choose the provider that owns most of the first workspace.
  3. Confirm the selected card is visibly marked.
  4. Choose Continue.

This choice sets the project default. A project can later contain controlled work across supported providers, but the first setup and resource library use the selected provider as their starting context.

Selecting a provider does not connect an account and does not grant ScrinCloud cloud access.

Project 2 of 4 · Screenshot placeholder

Choose the primary cloud provider

Show the AWS and Azure provider cards with one provider selected and the project summary visible.

Future capture briefCapture Cloud provider with the selected state, provider descriptions, progress row, and Project summary. Do not show real account information.

The provider appears in Project summary, and the Cloud provider progress card is complete.

  1. Open Project Access.
  2. Choose the narrowest suitable option:
    • Private limits access to explicitly authorized people.
    • Team is suitable when the project should be available to its assigned team.
    • Organization is suitable only when broad organization visibility is intended.
  3. Choose the Default Environment used by the first diagrams, workspaces, and Terraform variables.
  4. Add optional tags. Press Enter after each tag.
  5. Confirm Default environment is complete in Create readiness.
  6. Choose Continue.

Start with a non-production environment when you are learning the workflow. Your organization may offer different environment names; select the one that matches its approved terminology.

Project 3 of 4 · Screenshot placeholder

Set access and the default environment

Show Project Access, Default Environment, tags, and the completed Create readiness checklist.

Future capture briefCapture Access & defaults with a non-production environment, synthetic tags, and no menus left open. Keep readiness and progress visible.

Create readiness should say Create is available. If it says Create is disabled, read the reason shown directly below it and return to the named step.

  1. Read the project name, ID, description, provider, access, environment, and tags.
  2. Use the edit actions if any value is wrong.
  3. Confirm the project does not contain sensitive information.
  4. Choose Create project.
  5. Wait while ScrinCloud creates and opens the guided project setup.

Do not click the button more than once. The loading state prevents duplicate submissions while the project is being created.

Project 4 of 4 · Screenshot placeholder

Review the complete project

Show both review cards, the Ready to create state, and the Create project action.

Future capture briefCapture Review immediately before creation. Use synthetic values and include all summary fields plus the final primary action.

Creation succeeded when:

  • the new project name appears in the setup page;
  • Project Created is marked complete;
  • the setup sequence shows Add Members, Create Workspaces, and Configure Policies; and
  • no error notification is displayed.

If the project does not open, return to Projects and look for its name. Do not create a duplicate until you confirm that the first request failed.

Use letters and numbers separated by hyphens. Remove spaces, punctuation, and leading or trailing hyphens. The ID must also be unique within its scope.

Your organization may not have an available environment configuration. Ask an administrator to confirm the environment catalogue.

Open each progress card in order. Required data is:

  • Project Name and a valid Project ID;
  • one cloud provider; and
  • one Default Environment.

Return to Cloud provider before creation. After creation, do not hide a provider mismatch by using an unrelated workspace; correct the project through the approved project settings flow.

The product now opens the project setup journey. Continue with Invite your team.