> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/features/management-console/group-management.md).

# Group management

Groups are how WriteBackExtreme decides who reaches which data. You put users into groups, you assign connections and schemas to groups, and from then on giving somebody access is a matter of adding them to the right group.

You need the **user manager** role or an administrator account to open **Groups**.

## Rules

* A group contains one or more users.
* A group can be used by one or more schemas.
* Permissions and row-level security are set on the group.

## The groups overview

The list shows **Name**, **# of users** and **# of connections** per group. The row menu gives you:

* **Edit…** — opens the group form.
* **Members** — the **Assign users to group \<name>** dialog, where you tick the users who belong to this group.
* **Remove…** — deletes the group.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-7c5d3fe056ef6c1493d5e558b3c666be7d2e9c84%2FConsole_Groups_List.png?alt=media" alt=""><figcaption><p>The groups overview</p></figcaption></figure>

If you are not an administrator, the list only shows the groups you are in yourself.

**# of connections** is read-only here: a connection's groups are set on the connection, under **Authorized Groups**. See [Connections](https://docs.infotopics.com/features/management-console/connections.md#groups-and-schema-permissions).

### The Everyone group

**Everyone** is created by WriteBackExtreme itself and contains every user. It cannot be deleted and its members cannot be edited, which is why it has no **Members** or **Remove…** entry. Because everybody is in it already, you cannot assign it by hand in the user form either.

## Create a new group

Click **New** to create a group, or **Edit…** in a row menu to change one, and fill in **Group name** — at least three characters.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-8126da5de836cb424406db089488b2ddf143ee2d%2FConsole_Groups_Detail.png?alt=media" alt=""><figcaption><p>A manually created group</p></figcaption></figure>

A new group you create without picking members starts with you as its only member, so you can always reach what you just set up.

Groups that came from Tableau show a note saying so. Renaming one has no lasting effect: the next sync writes the Tableau name back over it. Rename the group in Tableau instead.

## Entitlements for Row-level Security

Entitlements are how a group gets row-level security: a property and a value, which WriteBackExtreme matches against your data to decide which rows the group's members may see and write.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-4d1d97ac5b08de454683f5def1cda69a77f74e28%2FConsole_Groups_Entitlement.png?alt=media" alt=""><figcaption><p>Adding a new Entitlement</p></figcaption></figure>

Open the group, click **New entitlement** and fill in:

* **Property name** — the column or attribute to filter on, for example `Region`, `Category` or `Department`. Spell it the same way everywhere; the match is literal.
* **Property value** — the value the group is entitled to, for example `South` or `Sales`.

Add as many pairs as the group needs. Entitlements can also be set per user, in the user form, and a user's entitlements and their groups' entitlements apply together. [Row Level Security](https://docs.infotopics.com/features/management-console/schemas/row-level-security.md) explains how the schema uses them.

{% hint style="warning" %}
Adding a single rule changes how data is loaded for the schemas this group reaches, so check a dashboard afterwards. Also make sure both fields are filled in: an entitlement with an empty property or value is accepted without a warning and then matches nothing.
{% endhint %}

## Automatic role synchronisation

For a group that is synchronised from Tableau, the group form has **Select the roles to assign to users in this group**. Users who arrive in this group on the next sync are given those roles automatically — useful when, say, everyone in your Tableau **Designers** group should be a schema manager in WriteBackExtreme.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-efe47ef035b0c2385993bc474afdf1a340e721d7%2FConsole_Groups_TableauSynced.png?alt=media" alt=""><figcaption><p>A Tableau-synchronised group</p></figcaption></figure>

Two things to know. Roles are only ever added, never taken away: removing a role here does not strip it from users who already have it. And the option exists only for Tableau groups — a group you created by hand shows *Automatic role synchronisation is not available for manually created groups*.

{% content-ref url="/pages/vZuufkDZ3B4MivkyYNzS" %}
[Tableau sync](https://docs.infotopics.com/features/management-console/tableau-sync.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/features/management-console/group-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
