> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User Groups

> Organize members into default role-based and custom groups that can be @-mentioned on tickets and assigned as approvers — target teams as a unit instead of person by person.

User Groups let you address a team as a single unit. Mention an entire squad on a ticket or assign a whole team as an approver — instead of tagging five people one at a time and hoping you didn't miss anyone.

<Info>
  User Groups must be explicitly enabled for your organization. Contact your Gradial team to get access.
</Info>

***

## 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:

| Scope            | What it covers                                                                                                                                                 |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Organization** | Visible across the organization — right for standing teams that work everywhere                                                                                |
| **Workspace**    | Belongs to exactly one workspace — right for teams scoped to one brand or project (e.g., a "Spring Launch Team" that should only appear where that team works) |

***

## 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

**To create a custom group:**

1. Go to **Organization Settings → People → Groups**
2. Click to create a new group
3. Name the group and choose its scope (organization or a single workspace)
4. Add members
5. Save

Group lifecycle and membership changes are audit-logged.

***

## 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](/docs/platform/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

| Action                                 | Who can do it                              |
| -------------------------------------- | ------------------------------------------ |
| View groups                            | All organization members                   |
| Create, edit, and delete custom groups | Org owners and admins                      |
| Edit group membership                  | Org owners and admins (custom groups only) |

***

## 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 →](/docs/integrations-administration-and-setup/managing-access/roles) — the role model that powers default groups
* [Adding Team Members →](/docs/integrations-administration-and-setup/managing-access/manage-team-members) — inviting users and configuring access
* [Mentions →](/docs/platform/mentions) — the @ picker where groups appear