Company Settings

Teams

Create hierarchical teams, manage direct members, and use teams for access control in Bigmind.

Teams organize the people in your company into the working structure Bigmind should use for access, filters, coaching, meetings, deals, accounts, and reporting. A team can have direct members, a parent team, and child teams.

#Teams vs. Managers

Teams and managers serve different purposes:

  • Teams: The operational structure used for access control and team-scoped views.
  • Manager: A person-level reporting field used for HR and reporting-line permissions such as "People who report to them".

For most access control, use teams. Keep manager assignments accurate for reporting-line use cases.

#Manage Teams

To create or update teams:

  1. Go to Settings > Team Members.
  2. Open the Teams area.
  3. Create a team, add an optional description, and choose a parent team if it belongs under another team.
  4. Add direct members to the team.

A member can belong to more than one team. This is useful for cross-functional teams such as Sales Enablement, RevOps, or leadership groups.

#Hierarchy and Membership

Team access is hierarchical. When a permission policy grants access to a team, Bigmind includes:

  • Direct members of that team.
  • Direct members of every child team below it.
  • Each person only once, even if they appear in multiple teams.

The team detail page shows direct members separately from sub-teams so you can see who belongs to the selected team itself.

#Use Teams in Permission Policies

Permission policies can use teams for data access across meetings, emails, deals and accounts, coaching, and insights:

  • Their teams: Gives a member access to the teams they directly belong to, plus child teams.
  • Selected teams: Gives a member access to specific teams selected in the policy, plus child teams.
  • People who report to them: Uses the manager reporting line, not team membership.

For more detail, see Permission Policies.

#CRM-Synced Teams

HubSpot and Salesforce teams can be created in Bigmind from the CRM integration settings. CRM-sourced teams keep their CRM membership in sync with Bigmind, while still being visible in the normal Teams page.

  • HubSpot: Bigmind can sync HubSpot teams and their members. HubSpot does not expose team hierarchy through the API, so hierarchy can be arranged in Bigmind.
  • Salesforce: Bigmind can sync Salesforce groups, members, and hierarchy. Salesforce-sourced hierarchy is managed from Salesforce.

See HubSpot Teams and Salesforce Teams for CRM-specific setup.

#Best Practices

  • Build your main revenue hierarchy first, then add cross-functional teams where needed.
  • Use clear team names that match how people talk about the organization.
  • Use descriptions to explain non-obvious teams, especially cross-functional access teams.
  • Review team membership when people move roles, territories, or functions.
Updated 5/17/2026