Start with one useful handoff
Make the reason findable before expanding the workspace.
Create a workspace and one owned ticket. Repository installation and invitations can wait until you need them.
1. Sign in, then complete Profile
The entry offers GitHub sign-in and an email-code sign-in option. After authentication, set your profile name and title. When creating a workspace, prepare its company/workspace name, country, data region and website. Company email is optional. These workspace fields also appear for personal projects.
2. Team: invite a reviewer or skip
Invitations are optional. Invite later from Contributors. Free supports up to two active human contributors; check Billing limits and card requirements before adding active teammates. A larger trial needs a separate capacity decision.
3. GitHub: connect when you need code evidence
The GitHub installation step is conditional on the workspace and connection flow. It can be skipped for now. Installing the App is separate from signing in with GitHub: review actual grants and repository selection before approving. Connect later in Settings → GitHub.
4. Updates: choose preferences and finish
Review the update preferences presented by the app. Theme and keyboard-shortcut review are not standalone steps in this onboarding sequence.
5. Make one useful handoff
Create a ticket, assign an owner and add the original request or decision source. Write acceptance criteria and the remaining review/QA step. Ask the reviewer to recover the reason without a separate chat. Add repository context only after the pilot access review.