> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/visibility/overview.md).
# Overview
Which browser-based applications and AI tools are in use across the organization: App Discovery and Portfolio Overview.
Visibility shows which applications and AI tools people use across the organization, and whether those tools earn their license budget. It works from the browser extension[^1] alone, so it starts as soon as the extension is deployed and needs no content to be built first. This section covers App Discovery and Portfolio Overview.
{% content-ref url="/pages/wHkexeXXbTSpfCo6v7UR" %}
[Portfolio Overview](/visibility/portfolio-overview.md)
{% endcontent-ref %}
## Where Visibility fits
Visibility is the first step of a loop that runs through all of Userlane: Visibility measures, Assistance acts, and Intelligence proves. App Discovery shows which applications are in use, so you can see where people struggle or where licenses go unused. Assistance then acts inside the applications that need it, and Intelligence measures whether that worked. Those results flow back into Portfolio Overview, where usage across the estate and evidence from each application sit side by side.
Portfolio Overview is the executive view across the estate.
{% hint style="warning" %}
**Visibility covers browser-based applications.** Userlane sees applications and AI tools used in Google Chrome or Microsoft Edge on devices where the extension is deployed. Desktop applications, native mobile applications, and server-side processes are outside its scope.
{% endhint %}
## Relevant articles
{% content-ref url="/pages/LCQejl2Si2P5rS4eFClz" %}
[Visibility, Assistance, and Intelligence](/getting-started/orientation/visibility-assistance-and-intelligence.md)
{% endcontent-ref %}
{% content-ref url="/pages/ZbAA5aBZMukn2qqLRZji" %}
[Roll out the extension](/deployment/rollout/roll-out-the-extention.md)
{% endcontent-ref %}
{% content-ref url="/pages/jPETkIUJrpI9g82NbAIg" %}
[App Discovery: find duplicate tools and redirect users](/best-practices/app-discovery-find-duplicate-tools-and-redirect-users.md)
{% endcontent-ref %}
## FAQ
What is Visibility?
Visibility is the part of Userlane that shows which browser-based applications and AI tools are in use across the organization. It includes App Discovery and Portfolio Overview.
Does Visibility need content to be built first?
No. Visibility works from the browser extension alone. Usage data appears once the extension is deployed, with no guides, tasks, or other content required.
Can Visibility be used without Assistance and Intelligence?
Yes. Visibility works from the browser extension alone and needs no content in individual applications. Assistance and Intelligence are added application by application.
Does Visibility detect desktop applications?
No. Visibility covers browser-based applications and AI tools in Google Chrome and Microsoft Edge. Desktop applications and native mobile applications are not visible.
{% hint style="info" %}
**Looking for something else?**
Try [Assistance overview](/assistance/overview.md), [Intelligence overview](/intelligence/overview.md), or [How Userlane is deployed](/deployment/rollout/how-userlane-is-deployed.md).
{% endhint %}
[^1]: The browser extension is the Chrome or Edge extension that delivers Userlane and collects usage data from browser-based applications.
---
# 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.userlane.com/visibility/overview.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.
