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

# Groups

> Grant access to many members at once. A group's membership combines hand-picked members with an optional attribute rule.

A **group** is a named set of members you can grant access to as a unit. Instead of granting ten people Viewer on a project, grant the group once—everyone in it inherits the access, and new members pick it up automatically.

Groups live in **Settings → Groups**. Only Owners and Admins can create or edit them.

## What a group's membership is

A group's members come from two sources, combined:

* **Manual members** — people you add by hand.
* **Rule-matched members** — people whose [attributes](/docs/permissions/attributes) match the group's rule.

The two add together. A member belongs to the group if they're hand-picked **or** they match the rule.

### Membership modes

When you create a group, you pick how membership is decided:

| Mode         | Who belongs                                                               |
| ------------ | ------------------------------------------------------------------------- |
| **Manual**   | Only the people you add by hand.                                          |
| **Everyone** | Every member of the company, automatically.                               |
| **By rule**  | Anyone whose attributes match the rule (plus any manual members you add). |

## Building a rule

A **By rule** group matches members against their [attribute](/docs/permissions/attributes) values. A rule is a list of conditions:

```
(attribute, operator, values)
```

* **Attribute** — which member attribute to check (for example, `etablissement`).
* **Operator** — `equals` or `is one of`.
* **Values** — the values that count as a match.

Conditions **combine with AND**: a member matches when they satisfy every condition. Within one condition, a member matches when **one of their attribute values** is among the condition's values.

A member with **no value** for an attribute the rule checks does not match. Rules fail closed—they never accidentally include someone whose attribute is blank.

<Note>
  Rules are evaluated live, every time access is checked. Change a member's attributes (or the rule), and their group membership updates on the next request—there's no sync to wait for.
</Note>

## What you can assign to a group

Anywhere you grant a member access, you can grant a **group** instead:

* **Resource permissions** — give the group Viewer, Editor, or Admin on a folder, project, database, entity, app, file, or integration. The grant reaches every member. See [Permissions](/docs/permissions/overview).
* **Row-level security audiences** — target a [row policy](/docs/permissions/row-level-security) at a group, so the whole group sees the same subset of rows.

## Manage a group

From **Settings → Groups**:

1. **New group** — name it, optionally add a description, and choose a membership mode.
2. Expand a group to see its **manual members** and its **effective members** (manual plus rule-matched, with a `via rule` badge on the dynamic ones).
3. Add or remove manual members from the expanded view.
4. Edit the rule or delete the group with the row actions.

## Next

* [Attributes](/docs/permissions/attributes) — the member values that power group rules.
* [Permissions](/docs/permissions/overview) — grant a group access to a resource.