> 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/user-management.md).

# User management

Everyone who uses WriteBackExtreme is a user in the management console. Open a dashboard with the extension in it and, if your username is not known yet, you are registered as a standard user in the **Everyone** group — which means you see the schemas shared with that group, and nothing else.

Users are kept in the console for two reasons. WriteBackExtreme is licensed per user, so every person who needs the extension has to be registered. And because users sit in groups, group membership is how you decide which schemas somebody can use.

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

## Rules

* A user belongs to one or more groups.
* Permissions are set per group, not per user. The administrator flag is the exception.
* To use the extension, a user must exist in the management console.
* Row-level security can be set on a user, on a group, or on both.
* A user without a role and without the administrator flag cannot open the management console at all.

## The users overview

The subtitle above the list tells you where you stand on your licence: **Unlimited users**, or **User license: \<active> / \<max>**, turning red when there are no spots left, followed by the number of inactive users.

The table shows **Display name**, **Platform username**, **# Groups**, **# Roles**, **Active**, **Last login** and the row menu. Administrators show **All** for groups and roles, because they reach everything regardless.

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

A red **locked** chip next to **Last login** means the account is temporarily locked after failed sign-ins; hover it to see until when.

Beside the list you will find:

* **New** — create a user. When your licence is full this is replaced by *Cannot create new users due to license user limit.*
* **Sync users via Tableau sync** — jumps to [Tableau sync](https://docs.infotopics.com/features/management-console/tableau-sync.md). Administrators only.
* **Export** — downloads `WriteBackExtreme_users.csv` with each user's display name, platform username, administrator flag, roles, groups and last login date. Handy for a licence review or an access audit.

Above the table, **Filter by group** and **Filter by role** narrow the list. Administrators stay listed whatever you filter on.

### Bulk actions

Tick the checkbox on two or more rows and a **Bulk actions** bar appears with **Add groups**, **Add roles**, **Remove roles** and **Remove groups**. This is the quickest way to give a new team access, or to take a role away from everyone who no longer needs it.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-fb96b039c323af8952c70651b7ce5839ac5c3507%2FConsole_Users_BulkActions.png?alt=media" alt=""><figcaption><p>The Bulk actions bar</p></figcaption></figure>

Bulk actions skip administrators and your own account, so you cannot lock yourself out or change a colleague's administrator rights by accident.

## Create or edit a user

Click **New**, or **Edit…** in a row menu.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-014ffad5a09dd5759034553985dc4c7103f09d45%2FConsole_Users_Form.png?alt=media" alt=""><figcaption><p>The user form</p></figcaption></figure>

| Field                                                                     | What it does                                                                                                                                                                                               |
| ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Display name**                                                          | The name shown in the extension.                                                                                                                                                                           |
| **Platform username**                                                     | How WriteBackExtreme recognises the person signing in. This has to match the username in your source platform exactly, or be mapped there with a calculated `USERNAME()` field. Usually an e-mail address. |
| **Password**                                                              | Optional, and only used by username + password sign-in.                                                                                                                                                    |
| **Confirm Password**                                                      | Has to match.                                                                                                                                                                                              |
| **User is administrator**                                                 | Full access to everything, regardless of groups. Only an administrator sees this switch, and you cannot set it on your own account.                                                                        |
| **Select the roles associated with this user**                            | Which parts of the management console the user may open. See [Roles](#roles).                                                                                                                              |
| **Select the groups associated with this user**                           | Which connections and schemas the user reaches. A new user starts in **Everyone**.                                                                                                                         |
| **User is temporarily inactive (unlicensed) and can't use the extension** | Frees the user's licence spot and blocks the extension for them. You cannot set this on your own account.                                                                                                  |

Below the fields sits **Entitlements for Row-level Security**, which works the same as on a group. [Group management](https://docs.infotopics.com/features/management-console/group-management.md#entitlements-for-row-level-security) describes it.

{% hint style="warning" %}
**Platform username** is what ties a person to their data. Change it and the extension no longer recognises that user: they are registered again as a new, empty account.
{% endhint %}

### Password rules

A password has to be at least **12 characters** and contain all four of: an uppercase letter, a lowercase letter, a number and a special character. The form tells you which rule you still fail, and the same rules are checked again on the server.

### Sign-in attempts

After **5** failed sign-ins in a row, the account is locked for **15 minutes**. Nobody has to unlock it: the lock lifts by itself, and a successful sign-in clears the counter. Locked accounts carry the **locked** chip in the overview.

### The licence limit

Saving a user who takes up a licence spot fails with *Cannot save user due to license limit reached* when your licence is full. Mark a user who no longer needs the extension as temporarily inactive to free their spot, or ask your account manager for more.

## Roles

A role decides which parts of the management console a user may open. Roles are assigned per user, in the user form or through a bulk action.

* **Connection manager** — creates and edits connections, within their own groups.
* **Schema manager** — creates and edits schemas, within their own groups, and works with semantic models.
* **User manager** — creates and edits users and groups. They never see administrators, and they can only assign groups they are in themselves.

Administrators reach every screen and every group, and need no roles.

{% content-ref url="/pages/dG2noYHqcyjvZYCxo3vm" %}
[Which role opens which screen](https://docs.infotopics.com/features/management-console/user-management/access-and-roles.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/user-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.
