# Set up your team Create a product, invite teammates to your organization, and grant each member access to 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 account — [sign up at lessly.com](https://app.lessly.com/signup). Sign in with an email address and a password, with a passkey, or with Google or GitHub. - The Lessly MCP installed in your agent — see [Install](/get-started/install). - Your teammates' email addresses. - Admin rights on the organization: inviting people and sharing products is an owner or admin action. ## How your organization is structured Your **organization** is your team 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. Membership is held at the organization, with the roles **owner**, **admin** and **member**. Access to an individual product is always a concrete grant on that product: owners and admins hold one on every product in the organization, and a member holds one only on the products explicitly shared with them. Without a share, a member does not see the product at all — the default is deny. > **NOTE** > You never create an organization as a separate step. Your first product creates it — the "create your first product" screen also asks for the organization name, and every product you create afterwards goes into that same organization. ## Step 1 — Create a product Make one product for each app you run. The examples use `Acme` and `maria@acme.com`; replace them with your product name and your teammate's email address. ### UI Open `/product/new`, or **Create product** on `/organization/products`, and give the product a name. ### 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 on `/organization/products`, or ask your agent *"List my products."* Acme appears, with you as the owner. ## Step 2 — Invite a teammate to the organization People join the organization first. The role you pick decides how much of the organization they hold. ### UI Open **Members** on `/organization`, enter the teammate's email, choose their organization role, and send the invitation. ### MCP Ask your agent: ```text Invite maria@acme.com to my organization as a member. ``` The agent calls [`organization_member_invite`](/reference/mcp-tools/organization_member_invite). It needs admin rights on the organization. An invited membership stays `invited` until it is accepted, then becomes `active`, and it can carry an expiry date after which it lapses. > **NOTE** > An organization role is not product access. An owner or an admin gets a grant on every product in the organization; a **member** starts with nothing until you share a product with them — Step 3. ## Step 3 — Share the product with them A share is the explicit grant that lets a member work in one product. It carries the role they hold there, and it can carry an expiry. ### UI Open **Members** for the product, at `/{product}/members`, and grant the teammate access to it. ### MCP Ask your agent: ```text Give maria@acme.com access to the Acme product as a member. ``` The agent calls [`organization_member_share-product`](/reference/mcp-tools/organization_member_share-product). Unsharing is [`organization_member_unshare-product`](/reference/mcp-tools/organization_member_unshare-product), and [`organization_member_list-product-access`](/reference/mcp-tools/organization_member_list-product-access) reads back exactly which products a member can reach. Share each product separately: a grant covers one product, so someone who works on two products gets two grants. ## Step 4 — Your teammate accepts Your teammate opens the invitation in a browser and signs in, or signs up with the invited email. The invitation is carried through a Google or GitHub round trip too, so an invited person is never asked for anything extra. ### UI The products you shared with them appear in their product list. Products you did not share are not merely hidden — requesting one returns 404. ### MCP They confirm access by asking their agent: ```text List my products. ``` Acme now appears for them, with the role you granted. ## 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 were granted. ## 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 *"remove maria@acme.com's access to Acme."* - Browse the [Deployment guides](/ship/deployment) for per-task recipes once your team is in.