> For the complete documentation index, see [llms.txt](https://docs.oort.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oort.io/understanding-check-failures/oort-insights/identity-posture-management-insights/unused-application-for-a-user.md).

# Applications with Limited Adoption

Detects applications that have been used by less than 90% (customizable) of the assigned users within 30 days(customizable), as configured in the check settings. Removing user access reduces unnecessary access and risk in case of account compromise, improves security posture, and can save licensing costs.

#### **Recommended Actions**

Before revoking access to a particular application, inform the assigned user(s), or their manager, that the app is not utilized and make sure the application is no longer needed. Remove access at the identity source where user access to the application is managed. If the app utilization rate is very low, consider decommissioning it entirely.

If you have many applications failing this check, focus on addressing impacted sensitive applications first. To do so, go to Applications and toggle to select the desired apps as sensitive, then update the check's settings here to only consider sensitive apps.

**Configurable Check Settings and Default Settings**\
\
Only sensitive apps: false

App usage timeframe: 30

Ignore bookmark apps: true

Utilization threshold: 90

Ignore List: empty

Include List: empty

**Compatibility**

[Microsoft Entra ID](/integrations/azure-active-directory-integration.md)

[Okta](/integrations/okta-data-integration.md)

Duo


---

# 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.oort.io/understanding-check-failures/oort-insights/identity-posture-management-insights/unused-application-for-a-user.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.