# Quickstart for org admins

Set up your org in order: connect GitHub, register your repos, create teamspaces, invite your team and choose the kit your sessions get.

This page sets up an org for a team, in the order that works best. Each step links to the page with the details.
You need to be an owner or an admin of the org. Owners and admins see the same setup pages.

## How your org is created

EasyCode creates your org and sends its first admin an invite. Open that invite, sign in with the email it went to
and click **Accept**. You land on the org's **Home**.

Home shows a checklist to owners and admins: **Install the GitHub App**, **Register your repos**,
**Create teamspaces** and **Invite people**. Each item opens the page where you do it, and ticks itself when it is
done. You can dismiss an item you don't need.

> **Install the desktop app too**
>
> Scanning repos and running sessions happen on a computer, in the desktop app. Install it early: see
> [the desktop app](/setup/desktop-app).

### Connect GitHub

Open **Settings → Repos** and click **Install on GitHub**. On GitHub, pick the account and give the EasyCode GitHub
App access to **All repositories** or to **Selected repositories**. Back in EasyCode, the page says
**Connected to GitHub**.

The App lets EasyCode see your repos. Cloning and pushing still use each person's own git login.
[Products and repos](/setup/products-and-repos) explains what the App can and can't do.

### Register your repos, or create products

When your org has the Knowledge module, the checklist says **Register your repos**. Pick the repos EasyCode should
learn. Repos that aren't archived and were pushed in the last 12 months are ticked for you. Click
**Save and scan**.

The scan runs in a desktop app signed in to your org, on a computer that can clone the repos. Code never leaves
that computer. In the desktop app, click **Scan on this computer** if it says **This computer is not scanning**.
When repos are scanned, **Review the proposed products**: keep, move or clear what EasyCode suggests.

Without the Knowledge module, the step is **Create products**: open **Settings → Products** and group the repos
each team ships. A repo can be in many products.

### Create teamspaces

Open **Settings → Teamspaces** and click **New teamspace**. A teamspace gives a team a place and owns its
products, for example _Checkout_ and _Mobile_ at Northwind. Add its members once they have joined.

### Invite your team

Open **Settings → Members** and click **Invite people**. Enter up to 20 email addresses, pick **Member** or
**Admin**, and choose their teamspaces. Each person gets an email with a link to join.

To invite without email, use **Invite links**: click **Create link**, set how many days it lasts (1 to 30) and,
if you want, a maximum number of uses. You can **Reset** or **Revoke** a link at any time.

[Org, members and teamspaces](/setup/org-members-teamspaces) covers roles and what each one can do.

### Choose your kit

The kit is what your sessions are offered: skills, agents, guides and MCP servers. After the review, click
**Choose your kit**, or open it later from the **Kit** link in **Settings → Library**. Answer **Who is on the team?**, then make one
choice per row. Each row says what a session will see.

Already have `CLAUDE.md`, `AGENTS.md` or skills in a repo? [Bring your existing kit](/guides/bring-your-kit) imports
them into your library.

### Set up knowledge

With the Knowledge module, EasyCode keeps an index and a map of each repo that sessions read. **Settings →
Knowledge** sets the models for knowledge tasks and how refreshes are reviewed.
[Set up knowledge for a repo](/guides/set-up-knowledge) walks through it.

## Optional next steps

- Connect Jira or Linear so sessions can start from a ticket: [Jira and Linear](/setup/jira-and-linear).
- Behind a firewall? Allow the hosts in [Network and firewall](/setup/network-and-firewall).
- Some modules are switched on per org, such as Studio, Workflows and Design systems. See
  [Kill switches and modules](/reference/kill-switches-and-modules).

## Next

- Send members the [Quickstart for members](/setup/quickstart).
- Follow the [Set up your org](/walkthroughs/set-up-your-org) walkthrough to see each screen.
- Read [Onboard a team](/scenarios/onboard-a-team) for the full first week.
