> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/documentation/partner-portal/partner-portal-detailed-guides/dashboard-billing-and-licensing.md).

# DASHBOARD, BILLING, & LICENSING

## DASHBOARD

The Dashboard provides a central, read-only view of all organisations managed under your partner account. It is designed for monitoring overall activity, licence allocations, agent health, and product usage, without allowing any direct changes or actions of your managed organisations.

* **Number of Licences:** Shows allocated licences per product for each organisation and their activation status. Click **Sync** to refresh the table with the latest licence information.
* **Agent Status:** Summarises agent activity and highlights potential risks. Click **Sync** to refresh the table with the latest agent data.
* **Management Console Usage:** Displays usage statistics, including last login and user details.
* **DISCOVER Usage:** Reports DISCOVER product usage across organisations. Click **Sync** to refresh the table with the latest data.

## BILLING

The Billing section provides visibility into subscription activity across partners and organisations allowing you to monitor future billing events and review past notifications.

### Alert History

The Alert History view provides a record of previously triggered billing alerts. It allows you to audit notifications that have already been sent and verify that alerting is functioning as expected.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FBKniZSFZKZyseohYBKId%2Fimage.png?alt=media&amp;token=fc462bf1-bbe6-4e2f-b84f-51c200e1aed1" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="282.333251953125">Field</th><th>Description</th></tr></thead><tbody><tr><td>Partner</td><td>The name of the partner.</td></tr><tr><td>Organisation</td><td>The name of the organisation under the partner.</td></tr><tr><td>Product</td><td>The product associated with the billing alert.</td></tr><tr><td>Licence type</td><td>The type of licence associated with the alert.</td></tr><tr><td>Expiry date</td><td>The date the licence expires.</td></tr><tr><td>Days prior</td><td>The number of days before expiry when the alert was triggered.</td></tr><tr><td>Status</td><td>The delivery status of the billing email sent to the user.</td></tr></tbody></table>

### Upcoming Alerts

The Upcoming Alerts view lists billing alerts that are scheduled for delivery. Use it to identify licences approaching expiry and prepare for renewals before notifications are sent.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FaNGOMGWG8HESKyxrlZzg%2Fimage.png?alt=media&amp;token=a08205a8-f064-4bd5-b619-aca319d272af" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="282.333251953125">Field</th><th>Description</th></tr></thead><tbody><tr><td>Partner</td><td>The name of the partner.</td></tr><tr><td>Organisation</td><td>The name of the organisation under the partner.</td></tr><tr><td>Product</td><td>The product associated with the licence.</td></tr><tr><td>Licence type</td><td>The type of licence associated with the alert.</td></tr><tr><td>Expiry date</td><td>The date the licence expires.</td></tr><tr><td>Days remaining</td><td>The total number of days remaining before the licence becomes invalid.</td></tr><tr><td>Schedule date</td><td>The date the billing alert email will be sent to the user.</td></tr><tr><td>Days prior</td><td>The number of days before expiry when the alert is scheduled.</td></tr></tbody></table>

## LICENCE STATUS

The Licence Status section shows licence allocation and life cycle status across organisations maintained by the Partner. Use it to identify inactive, activated, and expired licences.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FTQeosdeXglSBD0Hz99Bs%2Fimage.png?alt=media&amp;token=2385fabf-1ac0-4a5e-a8e2-87dd4f61ef59" alt=""><figcaption></figcaption></figure>

The page includes licences for GuardWare INSIGHT, DISCOVER, and PROTECT. Search records directly or filter them by partner or organisation.

<table><thead><tr><th width="232.333251953125">Field</th><th>Description</th></tr></thead><tbody><tr><td>Partner Name</td><td>The partner assigned to the licence.</td></tr><tr><td>Organisation</td><td>The organisation using the licence.</td></tr><tr><td>Product</td><td>The GuardWare product covered by the licence.</td></tr><tr><td>Licence type</td><td>The licence category or entitlement type.</td></tr><tr><td>Status</td><td>The current life cycle state of the licence.</td></tr><tr><td>Total Agents</td><td>The number of agents using the licence.</td></tr><tr><td>Active Agents</td><td>The number of active agents.</td></tr><tr><td>Assigned Date</td><td>The date the licence was assigned.</td></tr><tr><td>Activation date</td><td>The date the licence was activated.</td></tr><tr><td>Expiry date</td><td>The date the licence expires.</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guardware.com/documentation/partner-portal/partner-portal-detailed-guides/dashboard-billing-and-licensing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.