# Managing groups

URL: https://kywi-docs-production.up.railway.app/governing/managing-groups
Type: docPage

A group only ever targets a content-permission grant or owns an approval-chain step; its type and default role aren't read by anything that grants access.

A group is a named bucket of users, and it's consumed in exactly two places across the whole platform: as the target of a [content-level permission grant](/governing/content-level-permission-overrides/), and as the owner of one step in a multi-approver [approval chain](/governing/bypassing-the-queue-who-can-transition-directly/). It carries no role of its own and no site scope — putting someone in a group only gives them somewhere else to be targeted from, not new authority by itself.

## The type and default role aren't read anywhere

The group form lets you set a type — public or private — and a default role for members. Both are stored on the group. Neither is read by anything that decides access: no permission check, no membership rule, and no route consults them, and a member who joins is never assigned the default role because of it. Treat those two fields as labels for your own bookkeeping, not as settings with an effect.

## Type and default role look like access controls — they aren't

It's easy to set a group's type to "private" or give it a default role and assume that's doing something to who can reach what. It isn't. The only thing that controls access is what the group is targeted by — a content permission grant or an approval-chain step — not anything configured on the group itself.

## Membership only ever adds

Adding or removing someone from a group is a plain membership row, and it carries no override of its own. Being in a group can only *add* whatever a grant targets that group with — it never takes away something a member's role already gives them. There's no way to use group membership to restrict a user below their role.

## Who can manage groups

Creating, editing or deleting a group, and adding or removing its members, all sit behind the same threshold: site admin, on every route. That's the same floor as setting up content permission grants and [managing users](/governing/managing-users-roles-site-access/) — an editor can be a member of a group but can't create or reshape one.

Like role and site membership, a user's group list is part of what's baked into their access token at sign-in — removing someone from a group doesn't narrow a session already in progress until the token refreshes. See [Managing users, roles, site access](/governing/managing-users-roles-site-access/) for how long that takes.
