User Groups must be explicitly enabled for your organization. Contact your Gradial team to get access.
Group Types
Default role groups
Gradial automatically creates a group for each role at both the organization and workspace level: Owners, Admins, Brand Managers, Designers, Members, and Viewers. Membership in these groups is computed from roles and stays in sync automatically — when someone’s role changes, their default group membership follows. Default role groups are read-only: you can mention them and view them, but their membership can’t be edited directly.Custom groups
Org owners and admins can build groups that mirror how your team actually works — squads, regional teams, agency partners, launch teams — at either scope: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
- Name the group and choose its scope (organization or a single workspace)
- Add members
- 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.Permissions
Limitations
- Default role groups are read-only — membership is synced from roles and can’t be edited directly.
- A workspace group belongs to exactly one workspace — there are no multi-workspace groups.
- 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