What you end up with
For each product or business unit:
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.
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).
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. 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.
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
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:
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
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, and pay each product’s reps on their own deals with a commission plan 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 has the details; the MCP tools carry the same operations.
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:
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.