Setting up teams in Garba

Team Setup

Structure your organization in Garba

Teams allow you to control what users can see and how information is shared across your organization. Admins and Managers can create teams, assign users, and define visibility rules.

What teams control

Teams define:

• Visibility of meeting summaries and analytics

• Visibility of public past and upcoming meetings

Every user belongs to one team, and each team has an access level that determines who can see their meetings.

Team Access Levels

• All teams – Everyone in the organization can see the team’s public meetings

• Own + selected teams – Visible to the team itself and the specific teams you allow

• Own team only – Only users within that team can see the meetings

• Only you – Meetings visible only to the meeting owner

Note: Private meetings always remain private, regardless of team access settings.

How to create a team

1. Go to Settings → Account → Teams → Add Team

2. Name the team (e.g., Sales, CS, Implementation)

3. Set Team Meeting Access

4. Add users to the team

5. Add meeting types to the team

2. Recommended Team Configurations

Tip: Choose whether managers belong to their team or have their own.

Managers who join the team they lead can keep meetings private by default and make them public only when needed.

1. Cross-functional collaboration

Recommended for most organizations

Ideal for handovers between Sales → CS → Implementation → Support.

• Team Meeting Access: Own + selected teams

• Example flows:

  • Sales → visible to Customer Success

  • CS → visible to Implementation

  • Implementation → visible to Support

Outcome:

• Teams see only what’s relevant

• Clean handovers with no oversharing

• Better alignment across the customer journey

Important:
Users should still mark sensitive meetings as Private.

2. Full transparency

Best for small teams or organizations focused on shared learning

• Team Meeting Access: All teams

Outcome:

• All customer-facing teams see each other’s meetings

• Ask Garba, Strategic Insights, and Playbook scoring become more accurate

• Great for open collaboration cultures

Important:
Sensitive meetings still need to be marked Private.

3. Team-only visibility

For groups handling confidential or sensitive information

• Team Meeting Access: Own team only

Outcome:

• Only the team sees internal or client-specific discussions

• Useful when privacy outweighs transparency

Use cases:

• Leadership teams

• HR

• Strategy/consulting functions

• Departments with strict confidentiality needs

Note:
This limits organization-wide insights.

4. Individual-only visibility

Rare and generally not recommended

• Team Meeting Access: Only you

Outcome:

• No shared visibility

• Limited collaboration

• Insights become isolated to the individual

Use only when:
A role has strict, non-shareable confidentiality requirements.