> 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/analysis/usage.md).
# Usage Analysis
Monitor portfolio growth, user and workflow counts, application concentration, and security posture.
Use Usage to understand the shape and governance of the application portfolio.
***
## Set the scope
Open **Filters** to choose an **Organization**, **Team**, **Group**, or **Custom Field** value. The scope applies to the Usage KPIs, application-count trend, ranking, and distribution data. Selecting a Team also selects the Organization that contains it.
Clear the filters for the organization-wide view.
## KPI Cards
Four cards summarize the selected scope:
1. **# of users** — current user count and its change since January.
2. **# of on/offboardings this year** — completed onboarding and offboarding workflows in the current year.
3. **My Apps** — approved and under-review applications, with the change since January.
4. **Shadow Apps** — unapproved and newly discovered applications, with the change since January.
Use the cards as starting points, then open **Users**, **Onboarding/Offboarding**, **Applications**, or **Shadow IT** from the sidebar to investigate the records behind a value.
***
## Number of Apps
The monthly stacked chart shows counts for:
* **Approved** applications.
* **Under review** applications.
* Preview segments for future months in the current year.
Use the three year buttons above the chart to switch between the current year and the previous two years.
This chart measures the size and authorization state of the application portfolio. It is not an active-versus-inactive license chart.
***
## Application Ranking
Use the buttons above the table to rank up to five applications by:
* **Most user** — highest user count.
* **Least user** — lowest user count.
* **Recent** — most recently discovered.
Each row includes user coverage, Super Admin, and criticality. Select a row to open the application and inspect its users, owners, costs, and security details.
***
## Usage Distribution
The **Usage distribution (by number of apps)** chart shows how approved and under-review applications are distributed. Switch between:
* **Teams**
* **Organizations**
The chart displays the largest groups and combines the remainder as **Others** where needed.
## Security & Compliance Distribution
Use the selector to count approved and under-review applications by:
* Hosting type
* Criticality
* GDPR
* Security Level
* MFA Configuration or Enforcement
* SSO Configuration or Enforcement
* Lifecycle status
* Access Modes
* Discovery source
Use the result to find missing metadata and security-policy gaps. For example, select **MFA Enforcement**, then open the relevant applications to investigate those marked **Not Provided** or not enforced.
***
## Data Coverage
The Usage tab combines application inventory, directory, workflow, and recorded usage information. Keep its inputs current:
* Synchronize Google Workspace or Microsoft Entra ID so user and organizational counts stay current.
* Deploy the [Browser Extension](/docs/browser-extension/browser-extension.md) and monitor active installations where browser activity is part of your usage evidence.
* Maintain app approval, ownership, criticality, and security fields so rankings and distributions remain useful.
* Keep [Integrations](/docs/integrations/integrations.md) connected; a lost connection can leave previously synchronized values visible without refreshing them.
{% hint style="info" %}
No activity signal is proof only that Boza did not observe activity through the enabled sources. Verify coverage and business context before changing access or reclaiming a license.
{% endhint %}
## Recommended Review Flow
1. Start with organization-wide KPIs and note unexpected changes since January.
2. Use the Organization, Team, or Group filters to locate where the change occurred.
3. Check **Most user**, **Least user**, and **Recent** rankings.
4. Review security and compliance distribution for missing or weak controls.
5. Open the affected applications, or start an [Access Review campaign](/docs/user-management/access-reviews.md) when designated reviewers need to formally confirm access.
---
# 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/analysis/usage.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.
