Onboard First Project

Set up a project that is ready for safe non-production delivery and production governance from day one.

Task Outcome

Your first project becomes operational with explicit environment policy, ownership, and a validated preview-ready delivery path.

When To Use This Guide

Creating a new project for a product team.
Standardizing an existing project that has inconsistent environment controls.
Preparing for first controlled release run.

Prerequisites

Team roles and grants are already configured.
Organization environments exist in intended progression order.
Tenant naming and ownership conventions are defined.

UI Route Map

Open Projects and Environments.
Create project and assign ownership.
Attach project environments.
Configure policy/freeze expectations per environment.
Add tenant mapping and validate preview readiness.

Step-By-Step Execution

Create project with a clear, stable name and owner group.

Attach environments in progression order (for example dev -> staging -> production).

Set environment-level controls: deployment behavior, approval expectations, freeze handling.

Add at least one tenant and verify tenant-environment visibility.

Open workload/binding entry and confirm project receives expected assignment surfaces.

Run one non-production preview to validate generated impact scope.

Review project readiness with DevOps + Platform before first release creation.

Project Design Decisions

Use stable project IDs that survive team or repo rename cycles.
Avoid temporary labels in long-lived production projects.

Keep production controls stricter than non-production controls.
Explicitly define freeze behavior before first release.

Single owner team for governance; shared operators for execution.
Document who can request, approve, and execute high-risk actions.

Validate preview, approval, and audit visibility before go-live.
Do not postpone rollback drill planning.

Validation Checklist

Project has explicit owner and team-level access boundaries.
All environments show expected policy and freeze posture.
Tenant mapping appears correctly in project workspace.
Preview output is understandable and scoped.

Common Failure Modes

Environments attached but controls undefined: hidden production risk.
Tenant added before environment design is settled: inconsistent mapping.
Team can create project but cannot operate release: missing project operator grants.
Preview fails due to unresolved scaffold or assignment state.

Project Kickoff Checklist Template

Project name:
Owner team:
Operator teams:

Environment order:
Policy per environment:
Freeze behavior per environment:

Tenant model:
Preview validation completed (yes/no):
First release window:
Rollback drill date: