> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/user-guides/power-bi/users/dashboard.md).
# Dashboard
The Users Dashboard has two parts. Tiles showing your tenant's users - types and state. And a user data quality section showing status over time for some of the most commonly used user properties.
### Users Overview Tiles
Users Dasboard - User overview tiles
**Users:** Total number of users in your tenant.
* **Members:** Total number of member users
* **Guests:** Total number of guest users
**Active:** Users signed in the last 90 days
* **Members:** Member users signed in the last 90 days
* **Guests:** Guest users signed in the last 90 days
**Disabled:** Total number of disabled users in your tenant
* **Members:** Total number of disabled member users
* **Guests:** Total number of disabled guest users
**Inactive:** Users not signed in the last 90 days
* **Members:** Member users not signed in the last 90 days
* **Guests:** Guest users not signed in the last 90 days
### User Data Quality
User Data Quality over time. Lower percentages is better
The User Data Quality section tracks missing member user properties over time for these commonly used user properties:
* Company
* Department
* Manager
* Job Title
* Mobile Phone
* Office
When working with improving your data quality, you can get a quick overview of the effect in this dashboard.
{% hint style="info" %}
As the gauges and graphs show information about missing properties - you should strive to lowering the percentage!
{% 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://docs.bsure.io/user-guides/power-bi/users/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.
