Teams
Create workspace teams such as Sales, Ops, and Management so routing and handoff have clear owners.
Use Teams to confirm the operational groups that can own routing and handoff, such as Sales, Ops, and Management.
What Teams is for
Teams groups workspace users into operational ownership units. The captured state shows three starter groups: Management, Ops, and Sales.
Use this screen when a workflow, agent, or admin process should route work to a team instead of one person.
What each control changes
Create team opens the form for a new group. The table shows each team, how many users are assigned, who the members are, and row actions for later changes.
Name teams by the job they own: Sales for revenue handoff, Ops for operational review, Management for approval or escalation.
Operational outcome
A small set of clear teams makes routing easier to explain. Operators can see which group owns a handoff before work starts moving through automations.
Operational playbook
Create teams only when they will be used by routing, handoff, review, or permissions. Do not mirror the whole org chart if the teams do not affect product behavior.
After creating a team, add the right members and use that team consistently in workflow ownership, escalation paths, and operating reviews.
Best practices
Keep the first team model simple: Sales, Support or Ops, and Management are usually enough to teach ownership.
Review teams before launching a workflow that assigns tasks, escalates a conversation, or requires manager approval.
Troubleshooting
If a team does not appear where you expect, confirm that it exists here, has the right members, and that the workflow or setting supports team-based ownership.
If a handoff reaches the wrong people, fix the team membership first, then review the workflow routing rule.
FAQs
What does Teams control?
Teams lets admins define ownership groups such as Sales, Ops, Management, Support, or Implementation.
Who should use this page?
Workspace admins and implementation owners who decide how work should be routed or handed off.
How should this page fit into onboarding?
Start with a few practical groups that match real work. Add members once the ownership model is clear.
What should I verify before using this in production?
Verify that each team has a real purpose, an owner, and members who can receive or review the work.