> 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/configuration/configuration-panel/license-management.md).

# License management

The **License** page of the configuration panel is where you check which license WriteBackExtreme is running on, and where you replace it when you renew or when your subscription changes. This is the page to use for every license change after the first installation.

### Check your current license

The **Current license** card shows what the installed license allows:

* **Expires at** — the date the license runs out.
* **Modules** — the WriteBackExtreme modules the license unlocks.
* **Max users** — how many users you may create in the management console.

Blocked and deleted users do not count towards **Max users**.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-5320f451b5cd483ae53a9845e9255216ba6921b1%2FLicense%20information.png?alt=media" alt=""><figcaption></figcaption></figure>

### Replace the license

Download the new license from the [Apps for Tableau Enterprise Portal](https://my-appsfortableau.infotopics.com/products), then apply it in the same form you used during setup:

{% stepper %}
{% step %}

### Open the License page

Open the configuration panel and choose **License** under **Setup**.
{% endstep %}

{% step %}

### Add the new license

Either paste the contents of the license into **Please type or paste the license into this field**, or click the upload area and select the `.lic` file. Only `.lic` files are accepted.

The license is validated the moment you paste or upload it. On success you see **Given license is valid**.
{% endstep %}

{% step %}

### Restart WriteBackExtreme

Restart the application so it picks up the new license. On Windows you can do this from the panel's home page with **Restart WriteBackExtreme**; on Linux restart the service.
{% endstep %}
{% endstepper %}

### Where the license lives

Whichever route you take, the license ends up in the `wbe.config.toml` configuration file, under `app_license` in the `[writeback-extreme.env]` section. The configuration file sits next to the application binary: on Windows in the installation folder, on Linux in `/usr/local/share/writebackextreme/`.

{% tabs %}
{% tab title="Windows" %}
Open the configuration panel by running `WriteBackExtreme.exe` as administrator, then go to **License**.
{% endtab %}

{% tab title="Linux" %}
There is no graphical panel on Linux. Open the installer routes for 15 minutes and use the panel in a browser:

```bash
sudo /usr/local/share/writebackextreme/writebackextreme-amd64 install:enable
```

Then open `https://your-writebackextreme-domain.com/installer` and go to **License**. See [Configuration panel](https://docs.infotopics.com/configuration/configuration-panel.md) for the full procedure.

As an alternative you can edit `app_license` in `/usr/local/share/writebackextreme/wbe.config.toml` directly and restart the service.
{% endtab %}

{% tab title="Docker" %}
The container has no configuration panel. Change the `WBE_LICENSE` environment variable and recreate the container. The container refuses to start when `WBE_LICENSE` is empty.
{% endtab %}
{% endtabs %}

### Expiry and the grace period

WriteBackExtreme warns you before a license runs out and keeps working for a short while afterwards:

* From **30 days** before the expiry date the management console shows a banner telling you how many days are left.
* In the final **14 days** before expiry the license is flagged as a warning, but everything keeps working.
* After the expiry date you still have a **14-day grace period**. Only when the expiry date is more than 14 days in the past does WriteBackExtreme treat the license as expired.

{% hint style="warning" %}
Do not plan a renewal around the grace period. Replace the license before the expiry date so your users never see a warning.
{% endhint %}

### Check the license from the management console

The management console has a read-only view of the same information under **Info & license**, including the company and e-mail the license was issued to. Use the **License status** button there to re-check the license without opening the configuration panel. You cannot replace a license from the management console.

{% content-ref url="/pages/5MKkAvIhCDr2E8JjDHy0" %}
[Info & license](https://docs.infotopics.com/features/management-console/info-and-license.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/configuration/configuration-panel/license-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.
