> 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/info-and-license.md).

# Info & license

**Info & License** is the page you open to answer "which version are we on?", "how many user spots are left?" and "what went wrong?". It is for administrators only.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-a7fba3c4c54e13e7b3dc714b7f19e59ca1dfd3da%2FConsole_InfoLicense.png?alt=media" alt=""><figcaption><p>Info &#x26; License on 6.3.4</p></figcaption></figure>

## Version

The card at the top names your WriteBackExtreme version and the operating system it runs on. Have both to hand when you contact support. The changelog at the bottom of the page lists what changed in each release.

## Statistics

Four tiles count your **Connections**, **Schemas**, **Users** and **Groups**, and each links through to its page. A quick sanity check after an upgrade or a migration.

## License

The **License** card shows what your licence covers:

| Row                        | What it tells you                                          |
| -------------------------- | ---------------------------------------------------------- |
| **Company** and **E-mail** | Who the licence is registered to.                          |
| **Expired at**             | The expiry date, or **Never**.                             |
| **Module(s)**              | Which WriteBackExtreme modules you may use.                |
| **Max users**              | **Unlimited users**, or how many of your spots are in use. |

**License status** re-checks the licence and reports back that the information has been updated. Use it after a renewal, so the console picks the new licence up without a restart.

From 30 days before expiry, the page warns you how many days are left, and from 14 days the warning appears above every page in the console. *No license found* means WriteBackExtreme could not read a licence at all — check the licence with the button, or install it again.

There is no field here to paste a licence key into. A licence is installed with the installer or as a licence file on the machine; [Update license](https://docs.infotopics.com/getting-started/update-license.md) covers how.

## Logging

The logs are the first place to look when something behaves in a way you did not expect. They are kept for **30 days**.

**Logs** gives you two buttons:

* **System logs** — WriteBackExtreme's own logs: the management console and the extension, database connections, the SSO and OAuth process, API errors. Pick a file on the left, then click a line to read it in full.
* **Workflow logs** — what happened when a schema's workflows ran.

Inside either, you can search the lines and page through them, and each entry shows its **Level**, **Time** and **Content**. Filtering on level is the fastest way to a problem: errors first, then the warnings around them.

**Download logs** packs every log file into a single zip, which is the quickest way to attach them to a support ticket.

The same files are on disk, so you can also read them without the console. On Windows look in `<installation folder>\.wbe-runtime\storage\logs`, and on Linux in `/usr/local/share/writebackextreme/.wbe-runtime/storage/logs`.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-79c6f94706e210ff515cfd3e7f382955a8852bba%2FScreenshot%202024-02-28%20at%2013.23.38.png?alt=media" alt=""><figcaption></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/management-console/info-and-license.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.
