> 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/setup-security.md).

# Setup security

**Security** is where you decide how people prove who they are before the extension lets them write back. Each method is a card on the left; click one to open its panel, fill it in, and click **Apply config**. A green tick on the card means the method is enabled.

You need an administrator account to open **Security**.

Why authenticate again inside an authenticated Tableau environment? The extension runs in its own frame in your dashboard and cannot read the username from Tableau, so it needs a layer of its own.

{% hint style="info" %}
**Apply config** saves straight away. There is no separate save button at the top of the page: once the toast says the settings are updated, the method is live.
{% endhint %}

## The seven methods

| Method                  | What it does                                                                                                              | Applies to            |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| **Username + Password** | The built-in accounts from [User management](https://docs.infotopics.com/features/management-console/user-management.md). | Extension and console |
| **Single Sign On**      | SAML, with any identity provider that speaks it.                                                                          | Extension and console |
| **OAuth**               | Google, Auth0, Okta, Microsoft or SalesForce.                                                                             | Extension and console |
| **Tableau Auth**        | Checks the username and password against Tableau's REST API.                                                              | Extension             |
| **Power BI Auth**       | Accepts the Microsoft Entra token a Power BI report sends.                                                                | Extension             |
| **Pincode**             | One shared pincode for everybody. Deprecated.                                                                             | Extension             |
| **No Authentication**   | No check at all. Testing only. Deprecated.                                                                                | Extension             |

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-fd4b5fc9299a5fd589459df25b46070d92e78b62%2FConsole_Security_Overview.png?alt=media" alt=""><figcaption><p>The seven security methods</p></figcaption></figure>

You can have several methods enabled at the same time, and each enabled method becomes a button on the sign-in page. Two exceptions: switching anything else on removes **No Authentication**, and switching the last method off falls back to username and password, so you are never left without a way in.

We recommend [Tableau sync](https://docs.infotopics.com/features/management-console/tableau-sync.md) to get your Tableau users into WriteBackExtreme, whichever sign-in method you choose.

## Username + Password

The default. Users sign in with the **Platform username** and password set in [User management](https://docs.infotopics.com/features/management-console/user-management.md), which also lists the password rules. When you sync users from Tableau, an administrator has to set a password for each of them before they can use this method.

The panel also has **Disable Username + password login for Management-Console**, which is only available while the method itself is switched off. It closes the username and password route into the management console while leaving it open for the extension.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-2bd92092e1e5a16eedc077443a500f7a67794761%2FConsole_Security_UsernamePassword.png?alt=media" alt=""><figcaption><p>The Username + Password panel</p></figcaption></figure>

{% hint style="danger" %}
Disabling username and password sign-in for the management console can lock you out permanently if your OAuth or SAML configuration turns out to be wrong. Test your other method, in the console itself, before you tick this.
{% endhint %}

## Single Sign On (SAML)

WriteBackExtreme is a generic SAML service provider, so any identity provider that supports SAML works. It applies to the management console as well as the extension.

{% content-ref url="/pages/490TbbFBYfn5C2abhlth" %}
[SSO Setup](https://docs.infotopics.com/features/management-console/setup-security/sso-setup.md)
{% endcontent-ref %}

## OAuth

Sign-in through Google, Auth0, Okta, Microsoft or SalesForce. You can add several configurations, each with its own button on the sign-in page. This applies to the management console as well.

{% content-ref url="/pages/YyUyl1yuY9YapxrZN0Qi" %}
[OAuth Setup](https://docs.infotopics.com/features/management-console/setup-security/oauth-setup.md)
{% endcontent-ref %}

## Tableau Auth

Through Tableau's REST API, WriteBackExtreme checks a username and password against your Tableau Server or Tableau Cloud. Fill in your Tableau Server or Online URL — without `https://` and without slashes — along with **Tableau Site** and **Tableau API version**; all three are needed before you can apply.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-1e10f2ba5fe82459256b6db6ec57e860b3bd5224%2FConsole_Security_TableauAuth.png?alt=media" alt=""><figcaption><p>The Tableau Auth panel</p></figcaption></figure>

{% hint style="warning" %}
This only works for local Tableau accounts, so accounts with authentication mode **Tableau**. You will find that mode on the **Users** page of Tableau Server or Tableau Cloud. People who sign in to Tableau through an identity provider cannot use this method — use SAML or OAuth for them.
{% endhint %}

## Power BI Auth

For the Power BI extension: a report passes the reader's Microsoft Entra token, and WriteBackExtreme exchanges it for a session.

{% content-ref url="/pages/hoUOp6tNWpMp0m3Pil5f" %}
[Power BI authentication](https://docs.infotopics.com/features/management-console/setup-security/power-bi-auth.md)
{% endcontent-ref %}

## Pincode

One pincode of four to six digits, shared with everybody who may use the extension. Two checkboxes go with it: whether administrator accounts may use the extension too, and whether anyone may access it, which registers unknown usernames automatically in the **Everyone** group.

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

{% hint style="danger" %}
Pincode authentication is deprecated since 6.2.0 and will be removed in the next major release. While it is enabled, the management console shows *Action required: insecure authentication method detected* on every page. Move to SAML or OAuth.
{% endhint %}

## No Authentication

No check at all: whoever opens the dashboard can write back. Use it on a closed test environment without real data, and nowhere else. Enabling it switches every other method off.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-3ea43c613f3ed14f600d75639726d82b67f0f59c%2FConsole_Security_NoAuth.png?alt=media" alt=""><figcaption><p>The No Authentication panel</p></figcaption></figure>

{% hint style="danger" %}
No authentication is deprecated since 6.2.0 and will be removed in the next major release, and it raises the same insecure-authentication banner as pincode. Never use it in production.
{% endhint %}


---

# 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/setup-security.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.
