> 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/dashboardusage/getting-started/requirements.md).

# Requirements

### Network and server

There are prerequisites and things you’ll need before the installation:

* A web domain, for example, `<https://extension.company.com>` (create a DNS entry) which points to the host of the extension.
* Ensure the server is accessible solely via a VPN or within the company's internal network.
* SSL certificates for the above domain (the installation requires the domain’s `.crt` and private `.key` file, or a `.pfx` file).
* Server Resources: 4 vCPU, 8Gb, 50Gb application disk space, 100Mbps or 1Gbps network-interface.
* Firewall rules permit access on port 443 (HTTPS) to the server (or any other port you configure in the startup commands of the extension server). Both internal, external, network and server-firewall.
* A license (license.lic or LICENSE) from our portal ([https://my-appsfortableau.infotopics.com](https://my-appsfortableau.infotopics.com/)).
* Windows: Administrator access on Microsoft account (for the custom add-in setup).
* Linux: Sudo/Root permissions to register the `service`.
* Read the security page and make sure you are compliant: [here](/dashboardusage/getting-started/security.md)

{% hint style="success" %}
When using a network/internal domain, the traffic of DashboardUsage is available exclusively within the network (e.g., via VPN). Users outside the network cannot access the application (recommended!).
{% endhint %}

{% hint style="warning" %}
Please note that Tableau requires extensions to be running on HTTPS/SSL connection and therefore required!
{% endhint %}

### Database

Dashboard Usage requires a database to store dashboard information. All data is stored locally, so you'll need to have a database setup. Currently supported databases are:

1. Microsoft SQL Server
2. MySQL
3. PostgreSQL

### Files

You will need the following files that come with Dashboard Usage. You can download these from the enterprise portal. From the portal, you can pick the operating system of your choice.

1. An .env file
2. A .trex file
3. A binary build file (specific to your operating system)


---

# 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/dashboardusage/getting-started/requirements.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.