# Onboard a team

Bring a whole team onto EasyCode: the GitHub App, your repos and products, the kit, knowledge, teamspaces and invites.

Olivia is the admin of Northwind's EasyCode org. Her team ships a web shop and a design system from about forty
repos. By the end of this page, the repos are products, every session starts with the team's kit and knowledge, and
Dan, Lena and Adam are in the org.

Before you start:

- EasyCode creates your org and sends its first admin an invitation. Accept it and sign in.
- You need the org's **Owner** or **Admin** role for every step here.
- Scanning repos runs in the desktop app, on a machine that can read them. Install it first:
  see [Desktop app](/setup/desktop-app).

## Where do I start?

As an owner or admin, your org's **Home** shows a checklist: "Four steps to get your team working." Each step links
to the page that does it:

1. **Install the GitHub App**: connect your repos so products can use them.
2. **Register your repos**: pick the repos to learn; products come out of the review.
3. **Create teamspaces**: give each team a place and its products.
4. **Invite people**: bring your team into the org.

A step you don't need can be dismissed. The checklist is gone once every step is done or dismissed.

## Walk it through

### Install the GitHub App

Olivia presses **Install the GitHub App** and grants it the Northwind repos. If the App can read no repos yet, the
page says "Give the GitHub App access to at least one repo, then refresh." See
[Products and repos](/setup/products-and-repos).

### Register the repos

On **Register your repos**, she picks the repos EasyCode should learn and presses **Register repos**. Anything left
out can be picked later. Repos the App sees after this arrive unpicked, marked as new.

### Let a desktop app scan them

**Scanning your repos** shows each repo's state: Waiting, Scanning, Ready or Scan failed. A desktop app signed in to
the org does the scanning. Olivia presses **Scan on this computer** to scan from her own machine. If no desktop app is
scanning, the page says so.

She doesn't wait for the end: **Review what is ready** opens the review while the rest scans.

### Review the proposed products

The review groups repos into proposed products, such as "Storefront · 6 repos, 2 used from Platform". Olivia renames
a product where she wants and presses **Accept**. Repos that fit nowhere sit in **Unsorted**; **Make Unsorted a
product** turns them into one. A repo with a problem is held out until it is fixed.

### Choose the kit

The last step of registration is **Choose your kit**: what every session is offered. It lists what the repos already
carry, beside EasyCode's built-in core. Each row is **Found**, **Suggested**, **Merged** or **Conflicting**.

Under **Who is on the team?**, Olivia ticks **Developers**, **QA**, **Product managers** and **Designers**, which suggests
those role packs. A conflicting row
needs a choice before she applies. Skipped rows are remembered. See [Bring your existing kit](/guides/bring-your-kit).

### Set up knowledge

The scan is what each session learns about a repo: how the code is shaped and how to run it. On a product's
**Knowledge** tab, an admin or the product's maintainer can also start **Propose conventions** (rules with their
evidence in the code) and **Capture the design system**. See [Set up knowledge for a repo](/guides/set-up-knowledge).

### Create teamspaces

In **Settings → Teamspaces**, Olivia makes a teamspace for the shop team and one for the design system team, and gives
each its products. See [Org, members and teamspaces](/setup/org-members-teamspaces).

### Invite the team

In **Settings → Members**, she presses **Invite people**. She pastes Dan's, Lena's and Adam's emails (separated by
commas or new lines) and picks a **Role**: Member or Admin. She can also set a **Persona**, such as QA, and the
**Teamspaces** they join. They get an email with a link to join.

For a bigger group, **Create an invite link** makes one link with an expiry and a maximum number of uses. Whoever
opens it and signs in joins as a member. Copy it at once: it is not shown again.

## What happens when people join?

Each member has a persona, set on the invite or in their profile. When a persona has a role pack the kit has not added or skipped, the admin's Home says
so, for example "Kit: 1 role pack suggested · 3 new repos". Open the kit and add or skip it.

New members follow the [Quickstart](/setup/quickstart): install the desktop app, sign in, and connect their harness on
their own login. EasyCode never holds their harness credentials. See [Security and privacy](/overview/security-and-privacy).

## Related

- [Quickstart for org admins](/setup/quickstart-admins)
- [Set up your org](/walkthroughs/set-up-your-org)
- [Roles and access](/overview/roles-and-access)
