Use this checklist before connecting production systems. It prevents avoidable delays and keeps access decisions explicit.
People and ownership
- Name the workspace owner and a backup owner.
- Identify who can approve production changes.
- Identify who administers the automation runtime.
- Identify who owns the source repository and credential system.
- Choose the support contact for operational incidents.
Environment plan
- List the environments you intend to manage.
- Give each environment a clear purpose: Development, Staging, Production, or another approved role.
- Confirm the number of environments fits your current plan.
- Decide which environment is allowed to receive unreviewed changes. Production should not be that environment.
Workflow and repository preparation
- Inventory the workflows that matter most to the business.
- Choose a small, non-critical workflow for the first synchronization test.
- Agree on the authoritative repository and branch strategy.
- Record any workflows that contain environment-specific identifiers or values.
Credential preparation
- Inventory credential names, owners, targets, and environments without copying secret values.
- Confirm every credential has a rotation owner.
- Remove secrets embedded directly in workflow definitions before onboarding.
- Decide how access will be revoked if a team member leaves.
Change and recovery decisions
- Define who may accept a runtime change into desired state.
- Define who may restore desired state over a runtime change.
- Choose the evidence required before production approval.
- Document the business owner and rollback expectation for critical workflows.
Do not send secrets during onboarding
Support and onboarding should use tenant IDs, environment names, workflow IDs, credential names, timestamps, and error references. Never paste API keys, passwords, private keys, tokens, or complete credential payloads into a ticket.