> 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/power-bi-extension/authentication.md).

# Authentication

WriteBackExtreme needs to know who is using the report, so it can apply the right permissions and record who changed what. In Power BI there are two ways to establish that.

{% content-ref url="/pages/yrXMkVUsQVCXy8Jq4Bfj" %}
[Power BI SSO setup](https://docs.infotopics.com/features/power-bi-extension/authentication/power-bi-sso-setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/0Qrx3kkhp1fneGUATQ8I" %}
[Username setup](https://docs.infotopics.com/features/power-bi-extension/authentication/username-setup.md)
{% endcontent-ref %}

* **Single sign-on** passes a Microsoft Entra token from Power BI to WriteBackExtreme. You allow your tenant in the management console, and people are signed in without typing anything. This is the one to use where you can — and it is also what semantic model refreshing needs.
* **Username setup** puts the current user into the visual's **User** data well as a measure. Use it where SSO is not available, together with a username and password, a pincode, or no authentication at all.

The other methods WriteBackExtreme supports — username and password, pincode, OAuth and SAML — work in Power BI too. OAuth and SAML open their sign-in in a new browser window rather than a pop-up inside the visual.

The matching server-side settings live under [Power BI authentication](https://docs.infotopics.com/features/management-console/setup-security/power-bi-auth.md) in the management console.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-5e41bc6ad249eb4ffa76347c621b994bf73ffd8d%2FConsole_Security_PowerBIAuth.png?alt=media" alt=""><figcaption><p>The Power BI Auth panel in the management console</p></figcaption></figure>


---

# 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/power-bi-extension/authentication.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.
