> 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/dashboard.md). # Reseller Dashboard: KPIs & Quick Actions The Reseller Hub dashboard: active licenses, trials, renewals, overdue balances, your tier and the live map, with quick actions and a layout you can rearrange yourself. The dashboard is your landing page after sign in. It answers three questions at a glance: what is running, what needs attention, and what is about to be billed. ![The Reseller Hub dashboard](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-4474209faf920869911671e85d1640472181d689%2Freseller-hub-dashboard.png?alt=media) *** ## The default cards | Card | What it tells you | | --------------------------- | ------------------------------------------------------------------------------------------------------------- | | **Active licenses** | Licenses currently provisioned and running, with a trend line | | **Active trials** | Trials running right now | | **Renewals** | Renewals due, and how many have already completed this month | | **Expiring within 30 days** | Licenses that need a renewal decision soon | | **Overdue** | Bills past their due date, with the outstanding amount | | **Next collective invoice** | New licenses, renewals and upgrades from this month that are not on a bill yet, before VAT | | **Conditions** | Your current discount tier, your base price, and how many more active paid licenses take you to the next tier | | **Sessions (30d)** | RTK sessions across every customer in the last 30 days | | **Avg fix rate (30d)** | How much of that session time reached RTK FIX | | **Mission control** | Live (Fixed), Live (Float) and Offline counts across your fleet right now | Cards with a coloured edge want attention: amber for something approaching, red for something already overdue. Every card with an arrow icon drills through to the page behind the number, so **Overdue** lands you in Billing rather than in a generic list. *** ## Quick actions The action bar above the cards does the everyday jobs without a detour through a list page: * **Add Customer** - create a customer record * **Add License** - pick a customer (or create one on the spot), then provision a paid license or start a trial * **Send Login Link** - email a customer the magic link to their own [customer portal](/reseller-hub/customer-portal.md) view * **Export** - download all your **Licenses (CSV)** or **Customers (CSV)** The slider icon next to the buttons lets you reorder or hide them. *** ## Live map and session log The **Live Map & Session Log** row carries a compact version of the [Live Map](/reseller-hub/usage-and-live-map.md): your customers' sessions, colour coded as **Live (Fixed)**, **Live (Float)** or **Offline**, the **Positions** panel with the recorded path of whichever session you select, and the session log underneath. It is the quickest answer to "is this customer actually using what they bought". Like every row, it can be collapsed with the arrow next to its title. *** ## Rearranging the dashboard The dashboard layout is yours to change. Use the pencil icon at the top right to enter edit mode, where you can: * drag cards into a different order * resize a card, or merge two into a wider one * collapse a whole row you do not need * add cards from the catalog, or remove ones you never look at The catalog holds more than the default set, for example Outstanding balance, Credit exposure, Used vs unused, API status, License growth, Recent activity and trend charts for your portfolio, API traffic and session volume. Four built-in layouts are ready to use: **Billing**, **Compact**, **Operational** and **Combined**. You can save your own named layouts too, with a separate default for desktop and for phone. If you switch between layouts often, turn on **Show a dropdown next to Edit layout** in the layout menu to get a one-click switcher. Your layout is saved to your own login, not to the whole company. *** ## Banners A banner across the top of the dashboard means a bill is overdue and your account has moved onto the payment reminder ladder: | Banner | When | What it means | | -------------------------------------------- | --------------- | ------------------------------------------------------------------------------------- | | **Payment reminder** | 7 days overdue | A reminder only, nothing is blocked yet | | **Credit hold: new provisioning is blocked** | 14 days overdue | No new licenses and no new trials until the bill is paid | | **Renewals blocked** | 30 days overdue | Renewals and auto renew stop as well | | **Service cut pending** | 60 days overdue | RTKdata reviews the account and may suspend running licenses. This is never automatic | Each banner names the bill and how many days it is overdue. Paying the outstanding bill clears it. See [Billing](/reseller-hub/billing.md#when-a-bill-is-overdue). *** ## Next * [Customers](/reseller-hub/customers.md) * [Licenses & Provisioning](/reseller-hub/licenses.md) * [Usage & Live Map](/reseller-hub/usage-and-live-map.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/dashboard.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.