Manage · Onboarding

Onboarding

The hosted first-run checklist. After you create a hosted account, this page walks the six setup steps in order: join the right team, choose repositories, review what leaves your device, connect production and billing sources, verify both directions, and start with clear coverage. Each step is read from what exists on your team, so it resumes where the evidence stops.

Start here if you want to accept an invitation, bind the desktop app and start streaming as an invited member: Connect to your team. This page covers the checklist that tracks those steps once you are signed in.

Where to find it

  • Hosted: https://www.repoops.ai/team/onboarding
  • Steps: jump to a step with the #team, #repos, #sharing, #sources, #verify and #coverage anchors.
  • Reached from: the "Finish setup" banner after sign-up, and the "Connect a desktop" buttons on empty hosted tabs. It is not in the command palette or a sidebar item.

What it does for you

Setup in the right order.Join the team first, then choose repositories, review the sharing policy, connect production sources, verify that evidence arrives in both directions, and start. Each step links the exact place to do it, so a new account reaches a working hosted dashboard without guessing the sequence.
A checklist, not a wizard you can't leave.The steps are anchors on one page, and each is read from what exists on your team rather than from anything you ticked: a bound device, a listed repository, a reviewed policy, a received record. Close the browser, change machines, come back a week later; the page resumes at the first step without evidence. A step that cannot be read says unknown, never done.
Wrong team, wrong role, revoked device: each says its own next step.No membership names the invitation waiting for your address and creates nothing. A role below member says it cannot connect a device, because a connected machine holds a write credential, and points you to an owner or admin. A revoked device says so and offers a new code. No production record leaves a visible coverage gap, not a hidden one, and the step says which hosted provider connections are not built yet.

Read more

Last updated