Skip to content
  • There are no suggestions because the search field is empty.

User Groups: Overview

What are User Groups?

User Groups give Organization Admins a flexible way to organize people across teams so you can:

  • Target training and assignments to specific cohorts.

  • Analyze performance for cross‑functional segments.

  • Communicate and report on outcomes for the right audience.

User Groups are separate from Teams:

  • Teams usually mirror your formal structure (e.g., Revenue Operations, Enterprise Sales West).

  • User Groups are flexible, outcome‑driven cohorts that can span any teams.

Examples of User Groups:

  • “New AEs (0–6 months)”

  • “Enterprise sellers – Healthcare”

  • “CSMs in pilot regions”

  • “Managers only”

A single user can:

  • Belong to multiple User Groups.

  • Remain in all their existing teams and roles; User Groups do not change permissions.


Who can see and manage User Groups?

User Groups are managed at the organization level and respect your existing roles and permissions.

Organization Admins

Organization Admins have full control over User Groups for their organization. They can:

  • Create, rename, and delete User Groups.

  • Add or remove users from any User Group.

  • Use User Groups as filters in Analytics and related admin views across all teams in the organization.

  • Use User Groups as recipients for certain communications and scorecards (where supported).

User Group settings live in the same All Organization configuration areas where Org Admins already manage members and roles.

Team Admins

In the initial release:

  • Team Admins cannot create, edit, or delete User Groups.

  • They can use User Groups as filters in Analytics, but:

    • Only within the scope of the teams they already manage.

    • User Groups do not give them broader, org‑wide visibility.

Members

Regular Members:

  • Do not see or manage User Groups as an admin setting.

  • May belong to one or more User Groups.

  • Are affected only in how they appear in admin views (for example, Analytics and scorecards).

  • Do not gain extra access or permissions by being in a User Group.


What can you do with User Groups?

This first version of User Groups focuses on three main capabilities for Organization Admins:

1. Organize users across teams

Org Admins can define User Groups based on:

  • Role or level (e.g., “Frontline managers”, “New SDRs”).

  • Segment (e.g., “Enterprise sellers – Healthcare”, “Mid‑market AEs NA”).

  • Program or initiative (e.g., “Pilot cohort – Q2”, “Leadership program participants”).

Key behaviors:

  • A User Group is a named collection of existing organization members.

  • A User Group can include users from multiple teams.

  • Membership in a User Group does not change:

    • Organization membership.

    • Team membership.

    • Org Admin / Team Admin / Member roles.

When a user is removed from the organization, they are automatically removed from all User Groups and no longer appear in User Group‑based analytics or filters.


2. Maintain User Group membership

Org Admins use the existing organization member list to manage User Groups.

  • Add users

    • Add existing members to one or more User Groups.

    • Users keep all current team memberships and access; this is an additional grouping only.

  • Remove users

    • Remove users from a User Group without affecting:

      • Their organization membership.

      • Their team assignments.

      • Their role (Org Admin, Team Admin, Member).

Changes to User Group membership update immediately in Analytics and any other experience that supports User Group filtering.


3. Use User Groups in Analytics and reporting

The first place you will actively use User Groups is in Analytics and related reporting.

User Group filters

On supported dashboards and reports (for example, Overview, Adoption, Engagement, Individual Progress, and report cards), you’ll see a User Group filter.

When you select a User Group:

  • All charts, tables, widgets, and exports scope to members of that User Group, limited by your existing permissions.

  • Other filters (user, assignment, team, etc.) automatically adjust to show only data for that subset of users.

How scope and permissions work

User Groups always respect your existing role and access:

  • For Organization Admins

    • User Group filters apply across the entire organization.

    • Metrics include only users who:

      • Are in the selected User Group, and

      • Belong to your organization.

  • For Team Admins

    • User Groups never expand visibility beyond the Team Admin’s teams.

    • Results are always the intersection of:

      • The Team Admin’s teams, and

      • Members of the selected User Group.

This ensures Team Admins cannot see users, assignments, or analytics outside their existing team scope.

Scorecards and digests

In the initial implementation:

  • Org Admins can send Member Scorecards to all users in a User Group by selecting that group as the recipient.

  • All users in that User Group who have a “Member” role in Brevity will be enrolled in the corresponding scorecard email cadence.

  • Any links in those digests still enforce existing permissions when opened.


How User Groups interact with your org and teams

User Groups are a layer on top of your current structure. They do not change how organizations, teams, or roles work.

  • Removing a user from the organization:

    • Automatically removes them from all User Groups.

    • Removes them from User Group‑based Analytics and filters.

  • Removing a user from a team:

    • Does not remove them from any User Groups.

    • They will no longer appear in analytics for teams they are no longer a member of, even if they remain in a User Group.

All existing role and permission rules remain in place:

  • Only Org Admins can manage User Groups.

  • Team Admins see only data for their own teams, even when using User Group filters.

  • Being in a User Group never grants extra access or admin capability.


Security, RBAC, and data protection

User Groups are designed to not introduce any new paths to sensitive data.

  • No role escalation

    • Being added to a User Group does not change a user’s org‑level or team‑level role.

    • No one gains Org Admin or Team Admin powers via User Groups.

  • No cross‑team or cross‑org leakage

    • Team Admins cannot use User Groups to see:

      • Users outside their teams.

      • Assignments, meetings, or analytics outside their teams.

  • Secure links and digests

    • Any links from Analytics, Scorecards, or digests that use User Groups land on views that respect your current RBAC and scoping rules.


What’s not included in the initial release

To set expectations for this first version:

  • Team Admin or “Group Admin” management of User Groups is not supported.

  • Delegated group‑level roles (for example, a “User Group Owner” or “User Group Admin”) are not available yet.

  • Automatic actions based on User Groups (for example, “whenever someone joins this User Group, auto‑assign this course”) are not part of this initial release.

  • Additional surfaces (for example, Meetings or Home dashboard) will be documented separately as they’re integrated.

The initial focus is on:

  • Creating and managing User Groups.

  • Filtering Analytics using those groups.

  • Directly assigning content to User Groups as a unit (where supported).


Next step: Learn how to set up and use User Groups

Now that you understand what User Groups are and how they behave, you can move on to the step‑by‑step setup guide:

→ Next: How to create and manage User Groups in Brevity