Groups and permissions
Two admin levers for keeping a larger organization tidy: groups (a way to organize users and delegate invitations) and permissions (who's allowed to do what).
Groups
A group is a named set of users in your organization, managed at Groups. A user can be flagged group admin for a group, which lets them invite people into that group without being a full org admin — handy for delegating onboarding to team leads. (Groups are about organizing people and delegating invites; for round-robin host pools you want a team, which is a separate thing.)
Permissions
The Admin Center → Permissions tab controls who in the organization can:
- Create shared events (templates and team-level event types),
- Manage workflows,
- Invite users — and there's an allowed email domains list, so invitations are limited to addresses on your domains.
Each is set to a scope like everyone or admins (and group admins).
How to do it
- Groups: Groups → create a group, add members, and mark any group admins.
- Permissions: Admin Center → Permissions → set each "who can…" scope and the allowed email domains; save.
Common pitfalls
- Group ≠ team. Adding people to a group does not put them in a round-robin team — those are managed separately on the Teams page.
- Invitations blocked by domain. If "allowed email domains" is set and you invite an outside address, it's rejected — add the domain or invite a matching address.
- "I can't change a setting." Permissions and most Admin Center settings are admin-only; a group admin can manage their group but not org-wide permissions.
Last updated May 11, 2026.