Onboarding
Get from first invite to first passport.
A short launch path for release owners, approvers, and stakeholders. It keeps setup explicit without exposing protected console data on the public site.
First-passport checklist
Workflow
Four roles, one release record.
Invite the release owner
Confirm who can create the first passport, who approves risk, and where escalation messages should land.
Create the first draft
Start with a release ID, source SHA, service, image digest, target namespace, and rollback reference.
Review the decision
Compare policy, runtime health, rollback readiness, and evidence gaps before the pipeline promotes.
Publish the note
Send a short release note with the verdict, residual risk, owner, rollback path, and next check-in.
Zero to first gate
Install, detect, then run one shadow gate.
The first successful customer path should not start with billing or provider-specific assumptions. Install the Trial runtime, review detected connector candidates, then wire one non-blocking gate before promotion.
Operator quick path
Step 1
curl -fsSL https://releasepassport.com/install.sh | bash -s -- --install-token <portal-install-token>Step 2
releasepassport connectors detect --api-url http://127.0.0.1:18081/releasepassport/v1Step 3
releasepassport gate --api-url http://127.0.0.1:18081/releasepassport/v1 --mode shadow --service api --release-id rel-001Replace the local API URL with the dashboard URL printed by the installer when using a real domain. Start in shadow mode so the first release records evidence without blocking production.
First run
Role-by-role setup walkthrough.
Use this sequence for the first customer workspace. Each role gets a specific protected screen, task, and expected outcome before the release is considered ready for review.
Create the workspace, invite release owners and approvers, publish the first template, then verify policy simulation before any enforce-mode rollout.
The settings view shows protected access, explicit roles, permissions, template version, and audit posture.
Create the first draft from the published template, attach source SHA, image digest, rollback path, target namespace, and owner evidence.
The draft can be saved while missing evidence stays visible as the next action.
Read the decision reasons, compare evidence freshness, approve or reject the gate, and request a waiver only with an owner and expiry.
The passport records a named decision instead of treating approval as a silent checklist item.
Filter the release timeline and export a sanitized report after deployment and post-release validation complete.
The export path warns about sensitive evidence and stays behind authenticated permission checks.
Accessible states
Plain-language empty, loading, and error copy.
These user-facing patterns help customer teams understand what is happening without seeing internal operator details.
No passports yet
No passports have been created for this workspace yet. Start with a draft when the release owner has a source SHA and rollback path.
Checking evidence
Release evidence is being checked. Keep this page open; the gate will show a decision when policy and runtime checks return.
Evidence missing
The release cannot be evaluated because required evidence is missing. Add the digest, rollback reference, or owner before trying again.
Release owners
Use the first draft to collect source, artifact, and rollback evidence.
Approvers
Review the decision reasons before approving risk or asking for a waiver.
Stakeholders
Read the release note for status, impact, owner, and next update time.
Need help preparing the first rollout?
Send the release ID, target service, expected window, and current gate mode. Do not send secrets or private evidence over email.