Operator access, Previews, and explicit lifecycle

Review the accepted security and lifecycle decisions as one connected dashboard experience.

Sign in as the operator

Use a wallet or authenticator when configured, with no registration or recovery flow.

When neither method is configured, Colonize continues to Projects without a persistent dashboard warning.

Use the recommended cross-account role or standard credentials supplied by the host environment.

Configure Preview values independently so a Preview never receives Production values.

Select an open PR targeting main, then keep the Preview current on later commits.

Review repository identity, exact SHA, and Preview secret names before building.

Review its stable public endpoint, current commit, build history, and manual cleanup actions.

Trace the clean builder, exact source, configuration snapshot, artifact, roles, and AWS-held logs.

Running resources remain online while future source builds are unavailable.

Remove domains, stores, project resources, and retained metadata through separate confirmed actions.

Screen map