> 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/devices.md).

# Enterprise Devices: NTRIP Logins, Bulk Create & Renewals

Create device logins in the RTKdata Enterprise Portal, one by one or in bulk, read their connection details, and renew or archive them.

A device is one NTRIP login with one data stream, for one receiver. If several receivers should share a number of connections, use a [fleet](https://docs.rtkdata.com/enterprise-portal/fleets.md) instead.

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

***

## Adding a device

Use **Add device** on the Devices page or the dashboard.

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

| Field            | Meaning                                                                                                                                 |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Pricing**      | **Standard terms**, or one of the products agreed for your account with its own price and term                                          |
| **Data streams** | Always one for a device                                                                                                                 |
| **Term**         | **Monthly** (1 to 11 months) or **Annual** (1 to 5 whole years)                                                                         |
| **NTRIP login**  | The username and password. Type your own, or use **Generate login** to have both made for you. A login cannot be changed after creation |
| **Price**        | What the device costs, before you confirm                                                                                               |

**Create device** provisions the login on the caster and the device appears in your list right away, named after its username. It is billed on [this month's invoice](https://docs.rtkdata.com/enterprise-portal/billing.md).

If the caster does not answer in time, the device shows **Provisioning** with a **Retry provisioning** action. Retrying never creates a second one.

Whether you can buy this way depends on your account:

* **Purchase order accounts** order devices through a [quote](https://docs.rtkdata.com/enterprise-portal/quotes.md). The dialog tells you so and links to the request form.
* **Product accounts** buy from their agreed products only, **Standard terms** is then not offered.

***

## Creating many devices at once

**Bulk create** makes up to 500 logins in one go.

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

| Field                          | Meaning                                                                                                                                                           |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Number of devices**          | How many logins to create                                                                                                                                         |
| **Pricing**, **Term**          | The same choices as for a single device, the dialog shows the total before you confirm                                                                            |
| **Tags**                       | Tags every new device gets, see [Tags](#tags)                                                                                                                     |
| **Username prefix** (optional) | With prefix `site-` and first number 1, the usernames run `site-0001`, `site-0002` and so on. Without a prefix, the logins get your account's generated usernames |
| **First number**               | Where the numbering starts                                                                                                                                        |

Passwords are random. The job runs in the background, and **Recent bulk jobs** on the page follows its progress, retries anything that failed, and offers the logins as a download once it has finished. Each device is billed like one added by hand. Sending a job again never creates anything twice.

***

## The device list

Three tiles sit at the top: **Active Devices**, **Expiring Soon** and **Overdue**. The chips above the table are quick filters with their own counts: **All**, **Active**, **Trials**, **Expiring soon**, **Expired**, **Suspended**, **Renewed** and **Pending**.

The table shows each device's mountpoints, caster, how it was created (**Portal** or **API**), plan, data streams, start, expiry, last use and connected time over the last 30 days. Use **Date**, **Expiry**, **Caster**, **Auto renew**, **Source** and **Tags** to narrow it down, and **View** to choose columns.

**Export** downloads your **Devices and fleets (CSV)**. To hand out logins, select rows and download their credentials as CSV or Excel. Passwords are read at that moment and are never stored in the portal. Both need the export right, see [Team & Rights](https://docs.rtkdata.com/enterprise-portal/team.md).

A device showing **Legacy Caster** was taken over from an earlier setup. It switches to **RTKdata Caster** by itself when it first connects there, with the same credentials.

### Tags

Tags group devices and fleets your way, for example by site or project. Add them on a row or on a device's page, tag many rows at once by selecting them, and use **Manage tags** to rename, recolour or delete them. The **Tags** filter narrows every list, and the **Usage** page charts your top tags.

***

## The device page

![A device page](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-8165b3ce970031420d1701d8f9cfa77114650687%2Fenterprise-device-detail.png?alt=media)

The left card holds the facts: type, plan, mountpoints, caster, how it was created, tags, price, dates and the **Auto renew** switch. The right card holds the signal: **Connected now**, **Last seen**, **Auth failures (30d)**, **GGA received (30d)** and **Parallel connections**, with **Report an issue** to go straight to [Diagnostics](https://docs.rtkdata.com/enterprise-portal/support.md). **Usage, 30 days** charts the connected hours per day, and the **Session Log** lists every recorded session.

***

## Connection details

**Show credentials** reveals what to enter on the receiver. It needs the right to show passwords, see [Team & Rights](https://docs.rtkdata.com/enterprise-portal/team.md).

![The connection details card](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-678451ba0aba3ffbb448c59df3086d1d96a56916%2Fenterprise-device-credentials.png?alt=media)

| Value                      | What it is                                                                                                                                                                          |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Host**                   | The caster address and port, `caster.rtkdata.com:2101`                                                                                                                              |
| **Mountpoint**             | The correction stream. **SMART** picks the national datum from the receiver's position, **SMART\_ITRF2020**, **SMART\_ITRF2014** and **SMART\_WGS84** force a fixed reference frame |
| **Username**, **Password** | The login for the caster                                                                                                                                                            |

Each field has its own **Copy** button, and **Copy all** takes the whole set. The [Integration Hub](https://docs.rtkdata.com/integration-hub/integration-hub.md) shows where these values go on most hardware and field software.

> **One stream, one connection.** A second receiver using the same device login disconnects the first every few seconds, which looks like an unstable network rather than a licensing problem. If receivers need to share, use a [fleet](https://docs.rtkdata.com/enterprise-portal/fleets.md).

A login's credentials cannot be reset. If they may be compromised, [open a ticket](https://docs.rtkdata.com/enterprise-portal/support.md).

***

## What you can do with a device

The actions depend on its state, and some depend on your account.

| Action                       | What it does                                                                                                                                    |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Renew**                    | Extends the term, billed in that month. You can change the term while renewing, the stream count stays one                                      |
| **Auto renew**               | Renews the device by itself two days before its term ends, so it never drops out. A notification tells you five days before that                |
| **Upgrade**                  | Moves to a longer term. The longer term starts when the paid time ends, and is charged in full                                                  |
| **Suspend** / **Reactivate** | Stops the login working and brings it back with the same credentials                                                                            |
| **Archive** / **Unarchive**  | Takes the login out of use: it stops connecting right away, while its term, auto renew and billing continue. Unarchive any time to use it again |
| **Convert**                  | Turns a trial device into a paid one with the same login                                                                                        |

### When a term ends

A device expires on its end date and stops connecting at that point. There is no grace period, with one exception: on a purchase order account, a device still on an open [renewal quote](https://docs.rtkdata.com/enterprise-portal/quotes.md#renewal-quotes) keeps running for up to 30 more days. An expired device keeps its credentials, so you can still renew it later.

### Devices added by RTKdata

RTKdata can add a device to your account free of charge. It shows who added it, with a note if there is one. It ends on its date unless RTKdata extends it, so it cannot be renewed or upgraded from your side.

***

## Trial devices

You cannot start a trial on your own, RTKdata grants your account free trial streams. See [Trials](https://docs.rtkdata.com/enterprise-portal/fleets.md#trials).

***

## Next

* [Fleets & Contingents](https://docs.rtkdata.com/enterprise-portal/fleets.md): sharing streams between receivers
* [Billing](https://docs.rtkdata.com/enterprise-portal/billing.md): how this turns into one monthly invoice
* [Support & Diagnostics](https://docs.rtkdata.com/enterprise-portal/support.md): when a receiver will not connect


---

# 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/devices.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.
