Groups & Team Licenses

Whether you’re selling team licenses to companies, running cohort-based bootcamps, or organizing students into classes — the Groups module gives you the structure you need. It brings team management, seat-based licensing, and cohort-based learning into BricksMembers, so you can manage shared access, synchronized schedules, and group discussions without juggling spreadsheets or third-party tools.

Who Uses Groups?

Groups fit a wide range of use cases:

• Course creators — Run cohort-based bootcamps where everyone starts together
• Corporate trainers — Sell team licenses so companies can train their employees
• Universities & schools — Organize students into classes with shared schedules
• Membership sites — Let members form study groups or communities
• B2B SaaS — Provide seat-based access for company accounts

What Are Groups?

Groups are containers for members who share access levels, schedules, and content. Think of them as teams, classrooms, or cohorts where:

• Members automatically receive shared access levels when they join
• Drip content can use the group’s start date instead of individual enrollment dates
• Leaders can manage their team members and review submissions
• Comments and discussions stay scoped to group members only
• Seat-based licensing controls how many people can join

Getting Started

Enable the Module

1. Go to BricksMembers → Settings
2. Find the “Groups” card in the Modules section
3. Toggle it on and save settings

Once enabled, a new Groups menu appears under BricksMembers.

Create Your First Group

You can create groups manually or automatically when customers purchase team licenses.

Manual creation:

1. Go to BricksMembers → Groups
2. Click Create Group
3. Fill in the details: name (e.g. “Spring 2026 Cohort”), type, owner, total seats, default levels, optional start and expiration dates
4. Click Create Group

Automatic creation via seat rules: Go to BricksMembers → Groups → Seat Rules, create a rule that matches your product, and when someone purchases, a group is created with the purchaser as owner.

Understanding Group Roles

Each group member has a role:

• Owner — The group creator (or purchaser via seat rule) with full control; cannot be removed
• Leader — Can view member submissions and notifications, and manage invites and members on frontend pages where leader actions are configured
• Member — Standard participant with access to group content

Leaders and owners can review submissions from group members, receive email notifications when members submit work, and view all comments within the group context.

Managing Members

Open a group from BricksMembers → Groups, scroll to the Members section, and add people by email or by selecting an existing user. Choose the role (Member or Leader) and click Add Member.

Invitations

You can invite by email or create shareable join links.

Email invitations: Click Invite by Email, enter the address, choose the role, and optionally send the invitation immediately. The invitee receives an email with a unique link; when they click it, they’re added to the group. In limited-seat groups, each pending email invite reserves one seat until claimed, deleted, or expired.

Join links: Click Create Join Link, set optional limits (max uses, expiration), and share the URL. Anyone with the link can join until limits are reached. Join links don’t reserve seats — claims fail if the group is full at claim time.

Seats and Capacity

Groups use seat-based licensing: Total Seats is the maximum allowed, Used Seats is how many are filled, and Available Seats is what’s left. When all seats are used, new members can’t join until someone leaves or you increase the total.

Drip Content with Groups

For cohort-based schedules, set a Start Date on your group, create a drip rule, and set Cohort Source to “Group”. The drip uses the group’s start date as Day 0, so different cohorts see content unlock according to their group’s schedule, not their individual enrollment date.

Building with Bricks

Dynamic Tags

Display group information anywhere with these tags:

• {brm_group:id} — Group ID
• {brm_group:name} — Group name
• {brm_group:type} — Group type
• {brm_group:role} — User’s role in the group
• {brm_group:member_count} — Total active members
• {brm_group:available_seats} — Remaining seats
• {brm_group:status} — Active, archived, or expired

Conditions

Control element visibility based on groups (all conditions use the user’s active group for the current post):

• Is Group Member — Show when the user belongs to a group that grants access to the current post
• Has Group Context — Same as Is Group Member
• Group Role — Show based on owner, leader, or member role
• Group Status — Show based on group status (active, archived, expired)
• Group Type — Show based on group type (e.g. cohort, team)
• Group Has Seats — Show if the group has available capacity

Query Loops

Two custom query types are available:

BRM: Group Members — List all members of a group. Enter the Group ID (use {brm_group:id} for the current user’s group, or a static ID).

BRM: User Groups — List groups a user belongs to. Enter User ID (leave empty for current user, or use a specific ID).

Form Actions

Add a Bricks form and choose from these BRM actions:

• Assign Group Seat (BRM) — Add a user to a group by email; configure group ID and map the email field
• Claim Invitation/Join Link (BRM) — Let users claim invitations; set token source to form field or URL parameter
• Invite Group Member by Email (BRM) — For leaders/owners: send email invitations from the frontend
• Create Group Join Link (BRM) — For leaders/owners: generate shareable join links
• Remove Group Member (BRM) — For leaders/owners: remove a member from the group

The last three require the current user to be owner or leader of the target group.

Comment Scoping

When the Groups module is enabled, comments are automatically scoped: new comments are tagged with the commenter’s active group, users only see comments from their own group, and admins see all. Posts without group context show all comments normally. This creates private discussion spaces within each cohort.

Group Types

Go to BricksMembers → Groups → Group Types to add types like Cohort, Team, Class, or Study Group. Use them to filter and organize groups.

Common Use Cases

Bootcamp cohorts — Each cohort has its own start date, drip unlocks on that date, students see only their cohort’s comments, and leaders can review assignments.

Corporate team licenses — A customer purchases a team license via seat rule, becomes the group owner with X seats, invites team members, and everyone gets access to training content.

Study groups — Create groups in the admin or via seat rules; leaders share join links for self-service enrollment and group-scoped discussions.

Best Practices

• Set realistic seat limits based on your support capacity
• Use expiration dates to auto-archive groups when programs end
• Assign leaders thoughtfully — they have management capabilities
• Test invitation flows and verify email delivery before launching
• Plan group types for consistent organization

Troubleshooting

Members not getting access? Check that the group has default levels configured, the member’s status is “active”, and the group status is “active”.

Invitations not working? Check if the invitation has expired, the user’s email matches (for email invites), max uses hasn’t been reached (for join links), seats are available in limited groups, and guest/post-claim redirect pages are configured in BricksMembers → Settings (Groups section).

Drip not using group dates? Verify the drip rule has “Cohort Source” set to “Group”, the group has a start date, and the user is an active member of the group.