- Route leads. A lead from a form or booking page goes to the right team and is shared between its members in turn.
- Decide who sees what. People limited to their team’s records see the records on their teams, not everyone’s.
- Group settings. A team can host a booking page together and can be given access to a pipeline.
Records have teams
Every contact, company and deal has a Teams field. A record can be on one team, several, or none. You rarely need to set it by hand:
Teams are only ever added for you, never removed. Change them at any time in the Teams field on the record, or for many records at once with Teams in the bulk actions bar. Turn the automatic rules off under Settings → Contacts, Companies and Deals.
A contact who talks to two product lines can be on both teams. Both teams see the contact; it still has one owner, and each product’s work lives on its own deal. To give it a rep from each product, turn on Multiple owners.
The default team
A workspace with more than one team can name one of them its default: Settings → Team members → Teams → Make default. It catches what nobody put on a team, so one forgotten choice does not leave a lead where no rep sees it.- New forms, scheduling pages, sequences and workflows take a team when they are created. If the person creating it is on exactly one team, that team. Otherwise the default team. The Team choice shown while creating a form or a scheduling page starts on that team, and No team there keeps it workspace-wide. Change or clear the team in its settings at any time.
- A copy stays on the team of what it copies, or on none like it.
- New contacts, companies and deals that are still on no team ten minutes after they were created join the default team. The wait gives a record time to join the team of the form, booking page or product it came in through.
Route leads to a team
From a form or booking page
Open the form or scheduling page settings and choose its Team. Everyone who submits or books through it is put on that team.With a workflow
Use the Assign to team step to put a record on a team and pick its owner.1
Start from the form
Create a workflow with the Form Submission trigger and choose the form. Turn on the inbound webhook on the trigger if leads also arrive from another system.
2
Add Assign to team
Choose the team and Round robin between the team. Each new lead goes to the next person on the team who receives leads.
3
Choose what happens to leads that already have an owner
Keep the owner if they are on this team (the default), always keep the owner, or always reassign.
Who receives leads
In Settings → Team members → Teams, each member of a team has a Receives leads switch. Turn it off for a team lead who should see the team’s records without being assigned leads, or for someone on leave. If nobody on a team receives leads, records still go on the team, with no owner, and anyone on the team can pick them up.Run a workflow for one team
Start the workflow with the Added to Team trigger and choose the team. It runs when a contact, company or deal joins that team, however it gets there: a form or booking page that belongs to the team, an Assign to team step, its owner’s teams, a change by hand or in bulk, or the API. A record already on the team does not start a run. Use it for anything that belongs to one product line: its welcome sequence, its Slack alerts, a deal in its pipeline. Choose Once per record under Re-enrollment if a record that leaves the team and comes back should not run again. To treat teams differently inside one workflow, add a Filter or Router, choose the Contact’s teams field, then includes and the team.Record Created runs for every new record and cannot be limited to a team. A record usually joins its team a moment after it is created, so Added to Team is the trigger to use when the team matters.
Who owns the contact after a booking
By default, booking a meeting does not change a contact’s owner. To change that, go to Settings → Contacts → Owners → After a meeting is booked:- Don’t change the owner
- Make the host the owner if the contact has none
- Always make the host the owner
Limit people to their team
Open Settings → Team members, then ⋮ → Record access on a member. For contacts, companies, deals and tasks choose:
Two more switches finish the job:
- Also show records with no owner and no team. Turn it off so unrouted leads are only seen by people with full access.
- People: Their teams. They see only the people on their teams, the people who report to them and their manager, in the member list, the team list and owner pickers. They can assign records only to those people.
Give each team its own views
Saved views on Contacts, Companies, Deals and Tasks can belong to a team, and a list can open on the view you choose for each team. Share a view with certain teams. Open the view, then its menu (the arrow on its tab) and Who sees this view. Choose Certain teams and tick the teams. The view then shows in the tabs of those teams’ members only. Workspace admins and the person who made the view always see it. Workspace gives it back to everyone. Admins can do this for any shared view, and an editor for the views they made. A private view is only ever its creator’s. Choose the view a list opens on. Open the view (or the built-in one, such as All contacts), then its menu and Default view:- For me sets your own default. Anyone can do this, with any view they can see.
- For a team is for workspace admins: tick the teams whose members should open the list on this view.
team_ids on a view (POST /api/v1/views to create one, PATCH /api/v1/views/{id} to change one; MCP create_view / update_view), and /api/v1/views/defaults (MCP set_default_view). Like every API change, setting a default there needs an editor’s or admin’s credential; viewers set their own default in the app. See CRM API.
A default decides where a visit starts, not where people can go: anyone can switch to another view, and the list stays on the view they chose until they close the browser tab. A default for a view that someone cannot see (a view kept to another team, or a deleted one) is skipped for them.
A view is a way of looking at records, not a permission. Keeping a view to one team tidies the tabs of the others; it does not hide the records. To stop people seeing another team’s records, use record access.
With the API and MCP
Everything on this page can be set up by an agent or your own code:- Teams, their members and who receives leads:
member-groupsendpoints and thecreate_member_group,set_member_group_memberstools. - A record’s teams:
team_idson contacts, companies and deals, and ateam_idfilter on their lists. - Imports:
team_idson the contact, company and deal imports (import_contacts,import_companies,import_dealsover MCP) puts the records the import creates or updates on those teams. - Many records at once:
POSTorDELETE /api/v1/member-groups/{id}/recordswith up to 10,000 contact, company or deal ids puts them on a team or takes them off it, keeping their other teams. Over MCP:add_records_to_teamandremove_records_from_team. - A form’s or booking page’s team:
member_group_idonPATCH /api/v1/forms/{id}and/api/v1/scheduling-pages/{id}. Over MCP:set_form_teamandset_scheduling_page_team. - A sequence’s or workflow’s team:
member_group_idon create and update, over the API and MCP. - The routing workflow:
create_workflowwith anassign_teamstep.get_workflow_schemadescribes it. - A team’s own workflows:
create_workflowwith ateam_addedtrigger. - The booking and team rules:
update_crm_settings. - What each member may see:
list_membersandset_member_access(workspace admins only).