# Set up your team

Adding your team shouldn't mean handing everyone the keys to everything. Here's how to bring people into Lessly, scoped to just the products they work on.

## Goal

Turn a single account into a structured team: one organization, a product for each app you run, and the right people in each.

## Prerequisites

- A Lessly organization — [sign up at lessly.com](https://app.lessly.com/signup). Sign in with Google, GitHub, or email and password.
- The Lessly MCP installed in your agent — see [Install](/get-started/install).
- Your teammates' email addresses.

## How your organization is structured

Your **organization** is your account and your single bill. Inside it, you create one **product** for each app you run — a SaaS, store, or game. Each product has its own database, deploys, and members. The organization keeps one consolidated bill, with per-product cost attribution.

> **NOTE**
> You never create an organization by hand — signing up is what creates it. Your job from here is creating products and inviting people into them.

## Step 1 — Create a product

Make one product for each app you run.

### UI

Open the product switcher at the top of the sidebar, choose **Create product**, enter a **Product name**, and click **Create product**.

### MCP

Ask your agent:

```text
Create a product called Acme.
```

The agent needs admin rights on the organization.

Products are isolated — members and resources in one product don't leak into another. Confirm it exists in the product switcher, or ask your agent *"List my products."* Acme appears, with you as the owner.

## Step 2 — Invite a teammate

Invite people to the specific product they work on.

### UI

Open **Members** in the sidebar, enter the teammate's email, and click **Invite**.

### MCP

Ask your agent:

```text
Invite maria@acme.com to the Acme product.
```

The agent needs admin rights on the product.

The invite grants the **admin** role and expires after **7 days**.

> **NOTE**
> Invites are scoped to one product. To give someone access to two products, invite them to each one.

## Step 3 — Accept an invitation

Your teammate opens the invite in a browser, signs in (or signs up with the invited email), and lands in the product as an admin.

### UI

The product appears in their sidebar.

### MCP

They confirm access by asking their agent:

```text
List my products.
```

Acme now appears for them.

## What you just did

You went from one account to a working team: an organization that bills as one unit, a product per app, and teammates scoped to exactly the products they touch.

## What to do next

- [Ship your first deploy](/get-started/first-deploy) into one of your products.
- Manage people any time — in the UI from **Members**, or ask your agent to *"list members of the Acme product"* or *"revoke the invite for maria@acme.com."*
- Browse the [task guides](/ship/custom-domain) for per-tool recipes once your team is in.