> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/reference/work-and-time-management/product/advanced-analytics/technology-usage.md).

# Technology Usage

We360.ai Technology Usage — understand how software and tools are adopted and used across the organization.

The **Technology Usage** module shows how software applications and tools are actually used across your organization. It turns app-usage data into insight about adoption, licensing, and where technology is helping — or hindering — productivity.

## What It's For

* **Rationalize software spend** — see which paid tools are widely used and which sit idle, so you can right-size licenses and renewals.
* **Measure adoption** — track whether newly rolled-out tools are being adopted across teams.
* **Guide tooling decisions** — compare how different teams rely on different applications to inform standardization.

## Working With the Data

* Break usage down by application, team, or time period.
* Identify under-used licensed software as a candidate for reclaiming or removing.
* Combine with [Business Intelligence](/reference/work-and-time-management/product/advanced-analytics/business-intelligence.md) to relate tool usage to productivity outcomes.

{% hint style="info" %}
Technology Usage is part of the [Advanced Analytics](/reference/work-and-time-management/product/advanced-analytics.md) suite and builds on the same app & URL tracking used elsewhere in the portal.
{% 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 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.we360.ai/reference/work-and-time-management/product/advanced-analytics/technology-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.