> 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/reseller-hub/customer-portal.md). # Customer Portal: Credentials for Your End Customers What your end customers see: a magic link sign in, a read only view of their own NTRIP credentials and session history, and the emails the portal sends them, all under your company name. Your customers can look up their own NTRIP credentials without calling you. Send them a login link, and they get a small, read only view of the licenses you provisioned for them. *** ## Sending the link **Send login link** sits on the customer record, in the customer list's row actions, and in the dashboard action bar. Select several customers in the list to send links to all of them at once. It emails a **magic link** to the customer's address. The customer needs an email address on their record for this. Without one, the button is unavailable and you deliver the credentials yourself from the license's [connection details](/reseller-hub/licenses.md#connection-details). After a link is sent, the button waits a few minutes before it can send again. The **Login** column on the customer list shows **Invited** once a link went out and **Active** once the customer has used it. *** ## What the customer sees They click the link in the email and land signed in. No password to create, nothing to remember. The link works once and is valid for 15 minutes. Once you have sent a first link, the customer can also request a new one themselves on the portal's sign in page with **Send magic link**. ![The customer portal sign in](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-eb225de2a0b63d218f655438cdcd01c044c2809e%2Freseller-hub-customer-login.png?alt=media) Once in, they are greeted by name and told whose credentials these are ("Your NTRIP credentials from" your company name). Each license shows its name, caster, number of data streams, status and time to renewal. ![The customer portal](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-ad2bda86dd91b13ab0d4abbefa8b6470169320a6%2Freseller-hub-customer-portal.png?alt=media) Opening a license shows its caster, data streams, start and renewal dates, the **Connection details** with **Copy all**, and a read only history of its recent sessions (start time, mountpoint, fix rate, duration and outcome). While a new license is still being provisioned, the credentials show as not available yet. The session ends after 30 minutes, or when the customer uses **Sign out**. *** ## What the customer cannot see The portal is deliberately narrow: | They see | They do not see | | --------------------------------------------------- | ---------------------------------------- | | Their own licenses and status | Anything about your other customers | | Their NTRIP host, mountpoint, username and password | Your prices or your bills from RTKdata | | Renewal date per license | The live map or your usage figures | | The session history of their own licenses | Anything that lets them change a license | There is no way for a customer to change, renew or cancel anything from this view. Every commercial action stays with you. *** ## When to use it * **At handover.** Send the link with the first license, so the customer always has a way back to their own credentials. * **On a repeat call.** "I have lost the password" becomes one click rather than a copy and paste. * **After an API order.** A customer provisioned through the [API](/reseller-hub/api.md) can be pointed at the portal for the details. *** ## The emails your customers receive The portal sends your customers three emails, and nothing else. None of them mentions RTKdata: each one carries your company name in the header, the text, the footer and as the sender name. Your customers cannot reply to them, so questions come to you. | Email | Subject | Sent when | | ------------------------------------------- | ----------------------------------------------- | -------------------------------------------------------------------------------------------- | | [Credentials](#credentials-email) | Your NTRIP credentials | You use **Send Creds** on a license | | [Login link](#login-link-email) | Your NTRIP credentials login link | You use **Send login link**, or the customer requests a new link on the portal sign in page | | [Caster migration](#caster-migration-email) | Your NTRIP connection is moving to a new caster | You assign a migrated license to its customer with **Also migrate to the new caster** ticked | Customers without an email address on their record receive none of these. You then pass the connection details on yourself. ### Credentials email The full connection details for one license: host, port, the four SMART mountpoints, username and password. It contains no portal link, so it works on its own. ![The credentials email](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-537d2dce648eae2c2dc7d57f4b6f419a073faa55%2Freseller-hub-email-credentials.png?alt=media) ### Login link email A button that signs the customer in to their [portal view](#what-the-customer-sees). The link works once and is valid for 15 minutes; the email says so, and tells the customer to ignore it if they did not ask for it. ![The login link email](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-9db6cc3483c089145fa14418db7904e34b0b891d%2Freseller-hub-email-login-link.png?alt=media) ### Caster migration email Only for licenses taken over from the previous RTKdata reseller portal. When such a license was migrated without a customer, you attach it to the right one with **Assign customer** on the license (this can be done once). With **Also migrate to the new caster** ticked, the customer gets the new host, port and mountpoint to enter in their device. Their username and password stay the same. ![The caster migration email](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-1cdb6f63e9b37afa0eb4e1ec5d2e236112aad99e%2Freseller-hub-email-caster-migration.png?alt=media) *** ## Explaining the values The portal shows the same values as the license detail page, with the same **What do these mean?** and **RTK Coordinate System** explanations: | Value | What it is | | ----------------------------- | -------------------------------------------------------------------------------------------------------- | | **Host** | The NTRIP caster address and port the receiver connects to | | **Mountpoint** | The correction stream, chosen from a dropdown. **SMART** picks the right datum from the rover's position | | **Username** and **Password** | The sign in for the caster | All of them go into the receiver's or field app's NTRIP client settings, usually under "NTRIP" or "RTK correction source". Your customer can follow the [Quick Start](/get-started/quick-start.md) or the guide for their exact device in the [Integration Hub](/integration-hub/integration-hub.md). *** ## Branding The portal and the login link email carry **your company name**, so the customer sees the credentials as coming from you. Your own logo, sender address and custom domain are not available yet. *** ## Next * [Customers](/reseller-hub/customers.md) * [Licenses & Provisioning](/reseller-hub/licenses.md) --- # 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/reseller-hub/customer-portal.md?ask=&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.