Set up your team

Create a product and share it with a teammate. An organization membership puts someone on your team; a product grant determines which product they can use.

Prerequisites

Lepsto access and an active account.
Owner or admin rights for the organization you will manage.
Your teammate’s email address.
For MCP, an authenticated client. The organization creation, invitation, and sharing tools use user scope and check the caller’s organization role; they are not product permission patterns to add to a token.

Use Acme for the example product and teammate@example.com for the teammate. Replace both with your values.

Step 1 — Create a product

Open Create product in the web app at /organization/products, or use /product/new. Give the product a name. Your first-product screen also asks for an organization name.

Ask your agent to list your organizations, select the intended one, and create a product named Acme. organization_product_create accepts name and an optional organizationId. If you need a new organization first, organization_create creates one from its name.

A product name must be nonempty and at most 100 characters. Its URL slug is derived from the name; its region is eu. Confirm Acme in the UI product list or with organization_product_list.

Step 2 — Add your teammate

The agent calls organization_member_invite. Its productShares can grant Acme in the same operation. Each share uses exactly one of role, roleId, or permissions; an optional expiresAt ends that share at the chosen time.

For an existing organization member, use organization_member_share-product instead of inviting them again.

Step 3 — Check whether acceptance is needed

Inspect the invitation result. added means the email already belonged to a registered user: they were added directly, with no invitation email or acceptance token. invited means an email was sent with a pending invitation valid for seven days.

When acceptance is needed, your teammate opens that link and signs in or registers with the invited email. This browser step establishes their own identity; the invitation is preserved through Google or GitHub sign-in.

Step 4 — Verify it works

Have them ask their own agent to list their products. Acme should appear. As an administrator, you can also inspect organization_member_list-product-access for their grants and expiry dates.

Choose Member when someone needs only selected products. Organization owners and admins receive grants on every product; sharing only Acme does not restrict that broader role. Roles and permissions explains the difference.

Was this page helpful?