Group Types
Default role groups
Gradial automatically maintains a group for each role at both the organization and workspace level:
Membership in these groups is computed from role assignments and workspace access, and stays in sync automatically — when someone’s role changes, their default group membership follows. Default role groups are read-only: use them to see or select the people in a role, not to grant a role. Their membership can’t be edited directly.
Custom groups
Org owners and admins can build reusable groups of organization members that mirror how your team actually works — squads, regional teams, agency partners, launch teams. Custom groups are the best choice when the same people need access to several workspaces. Assign a group to one or more standard workspaces, or leave it unassigned until you need it.Granting Workspace Access with Groups
Assigning a custom group to a workspace gives its eligible members Workspace Member access. A group assignment does not grant Workspace Admin, Owner, or Viewer access, and it does not change anyone’s organization role. Group-based access is effective Member access — it doesn’t create a direct workspace-membership record for each person. Access takes effect immediately when a group is assigned, so review the group’s membership before assigning it.When a group changes
Managing Groups
Groups are managed from Organization Settings → People → Groups. The Groups tab provides:- Tabs and filters by scope, type, and member
- Inline member editing for custom groups
- Create and edit dialogs for building new groups
- Go to Organization Settings → People → Groups
- Click to create a new group
- Give the group a name and, optionally, a description
- Add at least one current organization member
- Optionally assign the group to one or more workspaces
- Save
Group Mentions
Groups appear in the @ mention picker anywhere mentions work. Mentioning a group notifies every member of the group who has access to the ticket, in one action — the author is excluded from their own mention’s notifications.“@Web Squad — can you review the updated hero copy on the summer campaign pages before Friday?”Because default role groups stay in sync with roles, mentions like @Admins or @Designers always reach the current set of people in that role — the mention never goes stale as the team changes. See Mentions for how the mention picker works.
Group Approvers
Workspace-scoped groups can be assigned as a ticket’s approver. Any member of the group can complete the approval, so reviews never wait on one person’s availability. Group approvers are supported everywhere individual approvers are: ticket creation, editing, bulk operations, filters, and Excel upload.Removing a legacy workspace-scoped group from its workspace can set affected Task approvers to No approver. Restoring the group’s scope does not restore those approver assignments automatically, so reassign approvers after the change.
Permissions
Only people who can manage organization settings — normally Organization Owners and Admins — can create, edit, delete, or assign custom groups.
Limitations
- Default role groups are read-only — membership is synced from roles and can’t be edited directly.
- Group assignments grant Member access only — use a direct workspace role for Admin or Viewer access.
- Same-organization only — a custom group can contain only members of its own organization, and can be assigned only to active standard workspaces in that organization. Admin workspaces can’t have group assignments.
- Only workspace-scoped groups can be approvers — org-scoped groups can be mentioned but not assigned as ticket approvers.
Related
- Roles & Permissions → — the role model that powers default groups
- Adding Team Members → — inviting users and configuring access
- Mentions → — the @ picker where groups appear