> 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/usage-and-live-map.md).

# Enterprise Usage, Live Map & Activity Log

See which logins are connected in the RTKdata Enterprise Portal, follow live sessions and GPS tracks on the map, and read your activity log.

Three views answer "is this actually being used": **Usage** for consumption and limits, **Usage > Live Map** for what is happening right now, and **Usage > Activity** for what has happened.

***

## Usage

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

| Card                     | What it tells you                                                                                                               |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| **Total Licenses**       | Every login on your account                                                                                                     |
| **Connected Now**        | Logins with a live connection this moment                                                                                       |
| **Not Connected**        | Active logins without a live connection                                                                                         |
| **Avg Auth Failures**    | Average failed sign in attempts per active login over the last 30 days                                                          |
| **Parallel Connections** | Connections beyond what your logins allow. Anything above 0 means more receivers are online at once than there are data streams |
| **Active Trials**        | Trial logins running right now                                                                                                  |

The **Used vs Unused** bar shows the share of your active logins connected right now. Its **not connected** count is a link that filters the table below to exactly those logins.

**Usage by Tag** charts weekly connections for your top [tags](https://docs.rtkdata.com/enterprise-portal/devices.md#tags), or your top devices if you do not use tags. **Composition** charts the mix of active, inactive and trial logins over time. Both offer a **Custom** range.

The **Licenses** table breaks it down per login: mountpoints, product, connected, last used, connected time over 30 days, auth failures, GGA received, streams, and parallel connections against the stream count. **Export CSV** downloads every login, regardless of the current filter.

***

## Live Map

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

Every session across your account, live ones and each login's last known position.

| Marker                   | Meaning                                                   |
| ------------------------ | --------------------------------------------------------- |
| Green: **Live (Fixed)**  | Connected and holding RTK FIX                             |
| Orange: **Live (Float)** | Connected but not converged                               |
| Grey: **Offline**        | Not connected right now, shown at the last known position |

The cards above the map give **Live Now**, **Sessions (6h)**, **Avg Fix Rate** and **Avg Session** duration. The dropdown (**All licenses** by default) narrows the map and the session log to one login.

Select a session, on the map or with **View on map** in the **Session Log** below it, and the **Positions** panel plots its recorded path, coloured by **RTK fixed**, **RTK float** and **No fix**. That turns "it does not work on site" into "the track shows float only in that one corner of the site".

The **Session Log** lists each session with its start, login, mountpoint, fix rate, duration, baseline, outcome, client and caster, and filters by outcome. Data can be up to 30 seconds behind.

***

## Activity

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

A read only, chronological log of what happened to your logins and invoices, newest first, searchable and filterable by **When** and **Type**. Events about a login link to it.

***

## Reading fix rates

The fix rate is the share of a session that reached RTK FIX. A consistently low figure on one login is almost never a network problem:

* Check **GGA received**. Without the receiver's position the caster cannot select a correction stream. See [NTRIP & GGA Essentials](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md).
* Check **Parallel connections**. Receivers competing for too few streams knock each other off, and none will converge.
* Check the sky view at the site. Trees, buildings and metal structures all cost convergence.

***

## Next

* [Support & Diagnostics](https://docs.rtkdata.com/enterprise-portal/support.md)
* [Fleets & Contingents](https://docs.rtkdata.com/enterprise-portal/fleets.md): reading a fleet's utilization


---

# 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/usage-and-live-map.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.
