> 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.md).

# Management console

The management console is where you set WriteBackExtreme up: the connections to your databases, the schemas that write back to them, and the users and groups allowed to use them. It is a web application that you can open in your own browser or in a window inside your Tableau dashboard, and it runs on-premise or in your private cloud, behind your own firewall, along with the rest of the extension.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-048cf06d839359d180c5f38f14e6a944b421723d%2FScreenshot%202025-03-11%20at%2015.13.20.png?alt=media" alt=""><figcaption></figcaption></figure>

## Who gets in

Signing in to the management console needs either the administrator flag or at least one role. A user with neither can use the extension, but gets no further than the console's sign-in page.

Roles decide which screens you see, and they are scoped to the groups you belong to: a connection manager manages the connections of their own groups, a user manager the users and groups of theirs. Administrators see everything.

{% 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 %}

## What you will find in the sidebar

| Page                   | What it is for                                                                          |
| ---------------------- | --------------------------------------------------------------------------------------- |
| **Dashboard**          | The landing page, with what you have access to.                                         |
| **Schemas**            | The write-back scenarios themselves: tables, fields, permissions, workflows and audits. |
| **Connections**        | The connections to your databases.                                                      |
| **Users**              | Everybody who uses the extension, their roles and their groups.                         |
| **Groups**             | The groups that access is granted through, and their row-level security.                |
| **Security**           | How people sign in: username and password, SAML, OAuth, Tableau, Power BI.              |
| **Tableau Sync**       | Bringing users and groups over from Tableau Server or Tableau Cloud.                    |
| **Workflows**          | What happens after a write-back: notifications, stored procedures, approvals.           |
| **Audits**             | Who changed what, per schema.                                                           |
| **Info & License**     | Version, licence, statistics, logs and the changelog.                                   |
| **Advanced settings**  | Settings that affect the whole installation.                                            |
| **Data & AI Services** | AI configurations, agents and semantic models.                                          |

At the top of every page sits **Download .trex**, which gives you the manifest file you add the extension to a Tableau dashboard with.

## Banners you may see

WriteBackExtreme puts a banner above the page when something needs your attention. A licence that expires within fourteen days, or a licence whose user limit has been reached, shows up here — [Info & license](https://docs.infotopics.com/features/management-console/info-and-license.md) explains what to do about either. So does a deprecated SAML configuration, and the warning that an insecure authentication method is enabled, which means pincode or no authentication is switched on. [Setup security](https://docs.infotopics.com/features/management-console/setup-security.md) covers those.

## The console and the front-end configuration

Setting up a write-back use case happens in two places. In the management console you create the connection and the schema: where the data lives, what may be written and by whom.

With that in place, you add the extension to a Tableau dashboard and configure its behaviour and appearance there — what we call the front-end configuration. The extension connects to the back-end and signs you in by itself, then walks you through picking your schema. From there, you are writing back.

{% content-ref url="/pages/O6VKnExMwz0KNx4gzm68" %}
[Tableau extension](https://docs.infotopics.com/features/tableau-extension.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.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.
