> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorbitcrm.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Multiple Products or Business Units

> Run several product lines, brands or business units in one workspace: each with its own team, leads, pipeline, workflows and view of the CRM.

One workspace can hold several products or business units. Each one gets a **team**, and the team is what keeps them apart: its leads go to its people, its people see its records, and its workflows run for its records only.

This page is the setup from start to finish. It builds on [Teams and Lead Routing](https://docs.useorbitcrm.ai/guides/teams-and-routing.md), which explains each setting in more detail.

## What you end up with

For each product or business unit:

| Piece | How it is kept separate |
| - | - |
| People | A team, with a switch for who receives new leads |
| Leads | Its forms and booking pages put contacts on the team and share them between its people |
| Deals | Its own pipeline, visible only to the team |
| Customers | Its users and accounts sync in under the product, on the same contacts and companies |
| Automation | Workflows that start when a record joins the team |
| Visibility | Its people see their team's records and each other, not the other teams' |

Contacts, companies and deals are still one shared database. A customer who buys two products is one contact on two teams, with one deal per product.

> [!NOTE]
>
> Use one workspace when the units share customers, reporting or admins. Use separate workspaces when they must share nothing at all: no contacts in common, separate billing, separate admins.

## Set it up

**1. Create a team for each product**

Go to **Settings → Team members → Teams** and create one team per product or business unit, for example **Product A** and **Product B**. Add the people who work it.

Each member has a **Receives leads** switch. Leave it on for the reps who should be given new leads. Turn it off for a manager who should see the team's records without being assigned any.

A person can be on more than one team.

**2. Give each product its own pipeline**

In **Settings → Pipelines**, create a pipeline for each product. Under **Who can see this pipeline**, choose the product's team. Other teams no longer see the pipeline or its deals. Admins always do.

Skip this step if all products share one sales process.

**3. Send each product's leads to its team**

Pick whichever fits how the leads arrive:

* **A form or booking page per product.** Open its settings and choose its **Team**. Everyone who submits or books joins that team.
* **One form for several products.** Build a workflow: **Form Submission**, then a **Router** on the answer that says which product, then an **Assign to team** step on each path.
* **Leads from your own system.** Create the contact through the API with the team already set (see [With the API or MCP](#with-the-api-or-mcp)).

To give each lead an owner as well, add an **Assign to team** step with **Round robin between the team**. Every workflow that assigns to the same team shares one rotation.

**4. Sync each product's users and accounts**

If the products are software your customers sign in to, list them under **Settings → Users & workspaces → Products and business units** and choose each product's team. Then create one API key per product (**Settings → API keys**, with the product chosen) and give each product's code its own key.

Each product sends its users and accounts with [Users and Workspaces](https://docs.useorbitcrm.ai/developers/users-and-workspaces.md#several-products-in-one-workspace). A person who uses two products is one contact with an account in each, on both teams. Each product has its own fields on the contact, such as **Product A last seen**, and a company page shows each product's account with its plan.

Then, under **Customers** on the same page, choose the lifecycle stage for paying accounts. Someone who pays for any one of your products then shows as a customer, and so does their company.

Skip this step if nothing syncs from the products themselves.

**5. See each contact's products**

List the products under **Settings → Users & workspaces → Products and business units** if you have not already, choose each one's team and give it an icon. This works without any sync: the team is enough.

Then, on **Contacts**, add the **Products** column under **Columns**. Each row shows the products the person belongs to, with their icons: the ones whose team they are on and, when the products sync, the ones they have an account in.

**6. Limit what each team sees**

In **Settings → Team members**, open **⋮ → Record access** on each rep and set contacts, companies, deals and tasks to **Their team's**.

Two switches finish the job:

* Turn off **Also show records with no owner and no team**, so a lead that has not been routed yet is seen only by people with full access.
* Set **People** to **Their teams**, so reps see and assign to their own teammates only.

Admins and the workspace owner always see everything.

**7. Build each product's workflows**

Start the workflow with the **Added to Team** trigger and choose the product's team. It runs for each contact, company or deal that joins that team, and for nothing else.

Examples for Product A:

* **Added to Team** (contact, Product A) → **Add to Sequence** (Product A's welcome sequence)
* **Added to Team** (contact, Product A) → **Create Deal** in Product A's pipeline → **Slack** message to the team's channel
* **Added to Team** (deal, Product A) → **Create Task** for the deal's owner

Set **Re-enrollment** to **Once per record** if a contact should only ever go through the workflow one time.

Then set the workflow's own **Team** to the product's team, and do the same on its sequences. People limited to their team see only their team's workflows and sequences.

**8. Bring existing records in**

Records created before the teams existed are on no team. In **Contacts**, **Companies** or **Deals**, filter or select the ones that belong to a product, then choose **Teams** in the bulk actions bar and add the team.

This counts as joining the team, so an active **Added to Team** workflow runs for these records. Pause the workflow first if they should not go through it.

To bring in a product's list from a file, import it from the **Contacts** page and choose the team under **Put the imported contacts on a team**. New contacts start on the team, and existing contacts the import updates are added to it. Contacts the import skips (when you choose to leave existing contacts alone) are not, and neither is a contact that would end up on more than 10 teams. Imports only start a workflow whose trigger has **Imports** ticked under **Start on changes made by**.

**9. Check it**

Submit each product's form with a test email address. Then check that:

* the new contact's **Teams** field shows the right team, and it has an owner if you used round robin;
* the product's workflow shows a run in its run history;
* a rep from another team cannot find the contact.

## How records get their team

You rarely set a team by hand. A record joins a team when:

| When | Result |
| - | - |
| Someone submits a form or books a page that belongs to a team | The contact joins that team |
| A workflow runs **Assign to team** | The record joins that team |
| A record with no team gets an owner | It joins the teams its owner is on |
| A contact is linked to a company | The company joins the contact's teams |
| A deal is created | It joins the teams its pipeline is visible to. In a pipeline everyone can see, it joins its primary contact's teams, or its company's, or its owner's |
| You set **Teams** on the record, in bulk, or through the API | It joins the teams you chose |

Each of these starts **Added to Team** workflows that watch the team. Teams are added for you but never removed for you.

## Workflows: which trigger to use

| You want | Use |
| - | - |
| A workflow for one product's records | **Added to Team**, with the team chosen |
| A workflow for one form's submissions | **Form Submission**, with the form chosen |
| A workflow for one product's bookings | **Meeting Booked** or **Meeting Outcome**, with the product's team chosen under **Teams**. It runs for bookings on that team's scheduling pages only |
| One workflow that treats products differently | **Form Submission**, **Meeting Booked** or a contact trigger such as **Record Created**, then a **Router** on **Contact's teams** → **includes** → the team. On a form run the teams are there when the submission has an email address that matches a contact, which the form's own new contact does. Other triggers, such as **Meeting Outcome**, do not carry the contact's teams |
| A workflow for every new contact, whatever the team | **Record Created** |

> [!TIP]
>
> Make the team of your main product the [default team](https://docs.useorbitcrm.ai/guides/teams-and-routing.md#the-default-team). New forms, pages, sequences, workflows and records that nobody put on a team then join it by themselves.

> [!WARNING]
>
> **Meeting Booked** with nothing chosen runs for every scheduling page in the workspace. Once a second product has its own booking pages, open each existing Meeting Booked workflow and choose its team or its pages, or one product's alerts will fire for another product's demos.

> [!WARNING]
>
> **Record Created** cannot be limited to a team. A record usually joins its team a moment after it is created, so use **Added to Team** when the team matters.

Two things to know about who a workflow acts for:

* A workflow runs with its creator's record access. If a rep who only sees Product A's records builds a workflow, it runs for Product A's records only, whatever its trigger. Have an admin build workflows that must cover every team.
* A workflow never starts on a change it made itself. An **Assign to team** step in another workflow does start **Added to Team**.

## Customers shared between products

A deal belongs to the product whose pipeline it is in: a deal created in a pipeline that only Product B's team can see is on Product B's team alone, even when its contact is also Product A's customer. A sequence that belongs to a team stops for a meeting booked on that team's scheduling pages (or on a page with no team), not for one booked on another team's page.

A contact can be on up to 10 teams. When a Product A customer fills in Product B's form, the contact is added to Product B's team and keeps Product A's. Both teams see the contact. It keeps one owner, so keep each product's work on its own deal, in that product's pipeline, with its own owner. To let a rep from each product own the contact together, turn on [Multiple owners](https://docs.useorbitcrm.ai/guides/multiple-owners.md), and pay each product's reps on their own deals with a [commission plan per product](https://docs.useorbitcrm.ai/guides/commissions.md#plans-per-product).

**Assign to team** keeps the current owner by default when that owner is on the team being assigned. Choose **Always keep the owner** on the step if a second product must never take a contact away from its first rep.

## With the API or MCP

Everything above can be done by your own code or an AI agent. The [CRM API reference](https://docs.useorbitcrm.ai/developers/api/crm.md#teams-and-pipeline-access) has the details; the [MCP tools](https://docs.useorbitcrm.ai/mcp/tools.md) carry the same operations.

| Step | API | MCP tool |
| - | - | - |
| Create a team | `POST /api/v1/member-groups` with `name`, `user_ids`, `rotation_ids` | `create_member_group` |
| List a product and its team | `POST /api/v1/users/products` with `name`, `key`, `team_id` | Settings or the API |
| Sync a product's users and accounts | `PUT /api/v1/users` and `/api/v1/workspaces` with `product`, or an API key tied to the product | `upsert_product_user`, `upsert_product_workspace` |
| Change its members and who receives leads | `PUT /api/v1/member-groups/:id/members` | `set_member_group_members` |
| Restrict a pipeline to a team | `PUT /api/v1/pipelines/:id/access` | `set_pipeline_access` |
| Limit what a member sees | `PATCH /api/v1/members/:user_id/access` | `set_member_access` |
| Put a form or booking page on a team | `PATCH /api/v1/forms/:id` or `/api/v1/scheduling-pages/:id` with `member_group_id` | `set_form_team`, `set_scheduling_page_team` |
| Put a sequence or workflow on a team | `member_group_id` on create or update | `create_sequence`, `update_sequence`, `create_workflow`, `update_workflow` |
| Create a record on a team | `team_ids` on `POST /api/v1/contacts`, `/companies`, `/deals` | `create_contact`, `create_company`, `create_deal` |
| Change a record's teams | `team_ids` on `PATCH` (replaces the list) | `update_contact`, `update_company`, `update_deal` |
| Add or remove many records | `POST` or `DELETE /api/v1/member-groups/:id/records` | `add_records_to_team`, `remove_records_from_team` |
| Import records onto a team | `team_ids` on `POST /api/v1/contacts/import`, `/companies/import`, `/deals/import` | `import_contacts`, `import_companies`, `import_deals` |
| List a team's records | `?team_id=` on the contact, company and deal lists | `list_contacts`, `list_companies`, `list_deals` |
| Build the workflows | `POST /api/v1/workflows` with a `team_added` trigger or an `assign_team` step | `create_workflow` (`get_workflow_schema` describes both) |

Changing teams, their members, pipeline access and member access needs a credential whose owner is a workspace admin.

Create a contact for Product A from your own system:

```bash theme={null}
curl -X POST https://app.useorbitcrm.ai/api/v1/contacts \
  -H "Authorization: Bearer $ORBIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "email": "ada@example.com", "first_name": "Ada", "team_ids": ["PRODUCT_A_TEAM_ID"] }'
```

A workflow that runs once for each contact joining Product A:

```bash theme={null}
curl -X POST https://app.useorbitcrm.ai/api/v1/workflows \
  -H "Authorization: Bearer $ORBIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Product A: new leads",
    "member_group_id": "PRODUCT_A_TEAM_ID",
    "nodes": [
      { "key": "start", "type": "trigger", "provider": "team_added", "config": { "object": "contact", "team_ids": ["PRODUCT_A_TEAM_ID"], "enrollment": "once" } },
      { "key": "task", "type": "automation", "provider": "create_task", "config": { "title_template": "Call {{first_name}}", "due_in_days": 1, "assignee_mode": "contact_owner" } }
    ],
    "edges": [{ "source_node_id": "start", "target_node_id": "task" }]
  }'
```

The workflow is saved as a draft. Activate it with `PATCH /api/v1/workflows/:id` and `"status": "active"`.

## Limits

* A record can be on up to 10 teams. A form, booking page, sequence or workflow belongs to one team, or to the whole workspace.
* A workspace can have up to 100 teams.
* An import puts the records it creates or updates on the teams you choose for the whole import. There is no per-row team column: split a file by product and import each part with its team.
* Tasks are not on teams. A task is seen by its assignee and follows the access setting for tasks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.