> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/enterprise-portal/enterprise.md).

# Enterprise Portal: Devices, Fleets & Billing for Your Company

The RTKdata Enterprise Portal: run your own devices and fleets on RTK corrections, with quotes, one monthly invoice and rights for your whole team.

The **Enterprise Portal** is where companies running RTKdata on their own equipment manage their account. You create logins for your devices and fleets, watch them connect in the field, and handle quotes, invoices and support in one place.

![The Enterprise Portal dashboard](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-dedaf2f7744300025d6e2674eefe712c252e5ee0%2Fenterprise-dashboard.png?alt=media)

> Every screenshot in this section shows example data. All names, logins and response times are made up, and prices and amounts are blanked out. Your own conditions are the ones agreed with RTKdata.

***

## Who this section is for

This section is written for **companies with an RTKdata Enterprise account** and the people who run it: fleet and field managers, purchasing and accounting, and developers connecting their own systems.

If you only need to connect one receiver, start at the [Quick Start](https://docs.rtkdata.com/get-started/quick-start.md). If you do not have an Enterprise account yet, see [Enterprise & Volume](https://docs.rtkdata.com/commercial/enterprise-and-volume.md).

***

## The words that matter

| Term                  | What it means                                                                          |
| --------------------- | -------------------------------------------------------------------------------------- |
| **Data stream**       | One live connection to the correction service at a time                                |
| **Login**             | One NTRIP username and password, the credentials you enter on a receiver               |
| **Device**            | One login with one data stream, for one receiver                                       |
| **Stream contingent** | A pool of data streams for one term, bought or ordered as one item                     |
| **Fleet**             | One login holding several streams from a contingent, so several receivers can share it |

Rule of thumb: **use a device when a login belongs to one receiver, use a fleet when many receivers should share a number of connections** and you want to shift capacity without buying more.

***

## What is in this section

| Page                                                                                 | What it covers                                                        |
| ------------------------------------------------------------------------------------ | --------------------------------------------------------------------- |
| [Getting Started](https://docs.rtkdata.com/enterprise-portal/getting-started.md)     | Signing in, completing your account setup, finding your way around    |
| [Dashboard](https://docs.rtkdata.com/enterprise-portal/dashboard.md)                 | The numbers on your landing page, and arranging them your way         |
| [Devices](https://docs.rtkdata.com/enterprise-portal/devices.md)                     | Creating logins one by one or in bulk, connection details, renewals   |
| [Fleets & Contingents](https://docs.rtkdata.com/enterprise-portal/fleets.md)         | Buying streams, creating fleets, moving streams, trials               |
| [Billing](https://docs.rtkdata.com/enterprise-portal/billing.md)                     | The monthly invoice, payment, what happens when an invoice is overdue |
| [Quotes & Purchase Orders](https://docs.rtkdata.com/enterprise-portal/quotes.md)     | Requesting and ordering quotes, PO numbers, renewal quotes            |
| [Usage & Live Map](https://docs.rtkdata.com/enterprise-portal/usage-and-live-map.md) | Connections, fix rates, tracks and the activity log                   |
| [Support & Diagnostics](https://docs.rtkdata.com/enterprise-portal/support.md)       | Finding out why a login fails, tickets, your support agreement        |
| [Team & Rights](https://docs.rtkdata.com/enterprise-portal/team.md)                  | Inviting colleagues and deciding what each of them may do             |
| [API](https://docs.rtkdata.com/enterprise-portal/api.md)                             | Connecting your own systems with API v2                               |

***

## Good to know before you start

* **Your account can differ from this page.** RTKdata sets up each account for its contract. If something described here is missing for you, for example Fleets or self-service buying, your account was set up without it. Your own rights also decide which pages you see, see [Team & Rights](https://docs.rtkdata.com/enterprise-portal/team.md).
* **Logins do not change.** A login keeps its username and password for its whole life, including conversion and renewal.
* **Invoicing is monthly.** Whatever you create, renew or top up in a month lands on one invoice. Orders from a quote get an invoice of their own. See [Billing](https://docs.rtkdata.com/enterprise-portal/billing.md).
* **Help is built in.** Open **Help > Explain this page** on any page of your account for a short walk through of that page.


---

# 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.rtkdata.com/enterprise-portal/enterprise.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.
