> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/platform/dashboard.md).
# Dashboard
The Dashboard is the first screen you see after logging in to Boza. It provides a high-level snapshot of your organization's SaaS landscape — applications in use, license efficiency, cost totals, and upcoming renewals — so you can spot trends and take action without digging through individual pages.
***
## KPI Cards
Summary cards run across the top of the Dashboard:
1. **Total Users** — the total count of tracked users across your organization.
2. **My Applications** — the number of distinct SaaS applications in your managed portfolio.
3. **Cost YTD** — current recurring monthly subscription cost multiplied by the completed months of this year. The current month is excluded.
These cards update automatically as subscriptions, users, and cost data change. Hover the information icon beside **Cost YTD** to see the period it covers and how it is calculated; the full set of cost definitions is in [Metrics and Data Freshness](/docs/resources/metrics-and-data-freshness.md#cost-metrics).
***
## Most Used Apps
A horizontal bar chart ranks the applications with the highest usage across your organization. Each bar represents one application and its relative activity level compared to others.
Use this chart to:
* Identify which tools your teams rely on the most.
* Spot applications that may warrant a higher-tier subscription based on demand.
* Compare usage across similar tools (e.g., two project management apps) to consolidate where possible.
***
## License Usage
A monthly bar chart (January through December) breaks down license consumption into **Used** and **Unused** segments for each month. A year toggle lets you switch between years (e.g., 2024, 2025, 2026) to compare trends over time.
Use this chart to:
* Track how license utilization changes month to month.
* Identify seasonal patterns — for example, lower usage during summer months.
* Justify license downgrades or upgrades during renewal discussions by referencing historical data.
{% hint style="info" %}
If you notice a persistent gap between Used and Unused licenses, consider rightsizing those subscriptions. Even a small reduction in unused seats can lead to meaningful cost savings over a year.
{% endhint %}
***
## Apps per Team
A pie chart shows how applications are distributed across your organizational teams. Each slice represents one team and its share of the total application count (e.g., Business Team 52.8%, Engineering 42.8%, Group 4.4%).
This visualization helps you understand:
* Which teams have the broadest software footprint.
* Whether application distribution aligns with team size and function.
* Where shadow IT might be concentrated if a team's app count seems unusually high.
***
## Alerts
The Alerts panel on the right side of the Dashboard lists upcoming subscription renewals. Each alert displays:
* **Renewal date** — when the subscription is due for renewal.
* **Subscription name** — the specific plan or contract being renewed.
* **Application name** — the linked SaaS application.
Click any alert to navigate directly to the subscription details. Use the **Show all** link at the bottom of the panel to view the complete list of upcoming renewals.
{% hint style="info" %}
Review the Alerts panel regularly so you have enough lead time to renegotiate terms, adjust seat counts, or cancel subscriptions you no longer need before they auto-renew.
{% endhint %}
***
## AI Assistant
A purple **AI Assistant** button is available in the top navigation bar. Click it to open an AI-powered assistant that can answer questions about your SaaS data — for example, "Which applications have the lowest usage this quarter?" or "How much are we spending on design tools?"
The assistant draws from the same data visible across your Boza workspace, so its answers stay consistent with what you see in the Dashboard, Applications, and Users pages.
***
## Best Practices
* **Start your day here.** The Dashboard is designed to surface the most important signals first. A quick scan of the KPI cards and Alerts panel takes seconds and can flag issues early.
* **Use the License Usage chart before renewals.** Pull up the relevant year and review month-by-month trends so you enter renewal conversations with data, not estimates.
* **Cross-reference the pie chart with team growth.** If a team's headcount has grown but its app share has not changed, they may be underserved. If the opposite is true, there may be redundant tools to consolidate.
* **Act on alerts promptly.** Subscriptions that auto-renew without review are one of the most common sources of wasted SaaS spend.
{% hint style="info" %}
The Dashboard reflects live data from your connected integrations and browser extension signals. If numbers look stale, verify that your integrations are active under **Integrations** in the sidebar.
{% endhint %}
---
# 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://boza.gitbook.io/docs/platform/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.
