> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/discover/application-usage.md).

# Application Usage

Application Usage is Discover's main reporting view. It shows you how SaaS applications are actually being used across an organization — which is the foundation for tackling Shadow IT, right-sizing licenses, and flagging risky or non-compliant apps before they become a bigger problem.

With Application Usage you can:

* **Track adoption and usage** — see which applications are being used, by whom, and how often.
* **Identify unused or underused applications** — reclaim licenses and cut waste on software nobody's touching.
* **Optimize licensing spend** — make data-driven calls on right-sizing subscriptions.
* **Improve security and compliance posture** — catch unused or under-governed applications before they become a risk.

## Filters

Use the filters at the top of the report to scope results to a specific **Department**, **Job Title**, and/or **Employee**.

## Summary charts

The summary charts give you an at-a-glance breakdown of the selected date range:

* **Apps by Approval Status** — Approved, Restricted, or Pending Review
* **Apps by Risk Score** — Low, Medium, or High
* **Apps by Productivity** — Low, Medium, or High

## The application list

Every application with usage in the selected date range is listed with:

| Column                   | What it tells you                                                                |
| ------------------------ | -------------------------------------------------------------------------------- |
| Application name         | The app                                                                          |
| Category                 | Its classification                                                               |
| Status                   | Approved / Restricted / Pending Review                                           |
| Risk                     | Low / Medium / High                                                              |
| Productivity             | Low / Medium / High                                                              |
| Discovered (Web/Desktop) | Whether usage was picked up via browser traffic or a locally running application |
| User count               | How many employees used it in range                                              |
| Days Active              | A bar chart of usage across the range                                            |

Click into any application to see its details, and use **Edit** to adjust its status, risk, or category for that tenant — or for all companies at once (see below).

## Exporting reports

Export the current view as **PDF, CSV, or Excel**, or set it up as a **Scheduled Report** to land in your inbox automatically.

{% hint style="warning" %}
PDF export has been an intermittent pain point in real support cases — several partners have reported that CSV and XLSX exports work fine while PDF export does nothing, especially when a filter (like a single application) is applied. If a PDF export silently fails, try CSV/XLSX first and open a support ticket with the filter combination used.
{% endhint %}

## Customizing app classification

You can adjust an application's **status**, **risk level**, and **category** either for a single tenant or globally across **All Companies**. Click into the application, then **Edit**.

To set something globally so you don't have to reclassify it per client, switch the company selector to **All Companies** before editing — changes made while a single company is selected only apply to that company.

{% hint style="warning" %}
Category-editing has had rough edges in the field: some partners have hit an editor where the Category dropdown shows no options, or a change made under "All Companies" doesn't propagate down to individual tenants as expected. If you hit either of these, treat it as a bug report to Augmentt support rather than a configuration mistake on your end.
{% endhint %}

## Why an app or user might be missing

A few real-world gotchas worth knowing before you go looking for a bug:

* **A user shows zero applications.** The most common cause is that their device hasn't had the agent deployed yet, or their device's Windows/Mac profile doesn't map to an employee record — unmapped traffic shows up as anonymous company-level traffic instead of being attributed to that person.
* **An application shows usage you don't expect from a shared or admin account.** The agent reports what it sees in that account's browser history — it does not initiate application sign-ups on a user's behalf. If a generic/shared login (e.g. `ptsadmin`) shows usage of a consumer SaaS product, someone actually browsed there under that profile.
* **You can't see data older than roughly 3 months.** Application Usage reporting has a lookback window; if a partner needs older historical data for a specific app, that requires a support request rather than being self-serve in the UI.
* **No employees exist for the company yet.** Without at least one employee record, you can't get a meaningful per-user Application Usage view. You can create a generic employee manually and map devices to it as a workaround if the customer doesn't have Microsoft 365/Azure AD connected (on-premises Active Directory sync is not supported for this).

## Managing the underlying app data

Application status, risk, and category all live in the [App Catalog](/modules/discover/app-catalog.md) — Application Usage is the reporting lens on top of that same catalog data.


---

# 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://helpdesk.augmentt.com/modules/discover/application-usage.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.