> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope.console/analytics/ai-usage.md).

# AI Usage

The AI Usage view shows which AI applications are being used across your organization, who is using them, and how much. It gives IT and security teams the visibility they need to enforce AI policy and manage risk.

AI Usage requires no extra setup. As part of the dope.swg engine, the dope.security agent identifies AI application traffic directly on the endpoint during normal traffic inspection and reports it to dope.console. There are no additional sensors, deployments, or data collection.

{% hint style="info" %}
All AI Usage data is shown over a rolling **seven-day window**.
{% endhint %}

<figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FT9OiFshTmAgycMLBDMWX%2Fai-usage-view.png?alt=media&amp;token=3b4b43bd-9852-4f72-b181-4eefc27d90bb" alt=""><figcaption></figcaption></figure>

## Opening the AI Usage view

1. In dope.console, go to **Analytics**.
2. Use the view selector in the top right of the page and choose **AI Usage**.

## Summary tiles

The top of the page shows four headline metrics for the last seven days:

| Tile                       | What it shows                                                                   |
| -------------------------- | ------------------------------------------------------------------------------- |
| **Total AI Requests**      | The combined request count across all AI applications.                          |
| **Total Active Users**     | The number of users in your organization who used at least one AI application.  |
| **Distinct AI Apps**       | The number of unique AI applications seen across all endpoints.                 |
| **Total Data Transferred** | The total ingress and egress data to and from AI applications across all users. |

## Apps tab

The **Apps** tab lists every AI application in use, ranked by adoption and request volume, so you can quickly see which tools matter most and spot unsanctioned ones.

For each application you can see:

* **Transactions** – the number of requests made to the app
* **Users** – the number of users who accessed the app
* **Volume** – the amount of data transferred

Select an application to open its detail panel, which shows the total number of users of that app and its top users by volume.

## Users tab

The **Users** tab shows which users are generating the most AI traffic, and how AI usage is spread across your organization.

For each user you can see:

* **User name / email**
* **Transactions** – the user's total AI requests
* **Transaction share** – the user's share of all AI requests

Select a user to see every AI application they accessed, along with the request count for each.

## Exporting a report

Select the **download** button at the top of the page to generate an AI Usage report with a single click. The report is ready to share outside the console with CISOs, IT leadership, compliance teams, or auditors.

## Taking action

AI Usage is the visibility layer of AI governance. Once you know which AI apps are in use, you can act on it with dope.security's enforcement tools:

* **Control which AI applications are allowed** with a [dope.swg Policy](broken://pages/8fdc1ac441f6d48760d2da5852cfc944dd40f7ff).
* **Restrict approved AI tools to enterprise accounts** with [Cloud Application Control](broken://pages/ed4f53371ff2f6836c8deee896c0c554c13bebf6).


---

# 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://inflight.dope.security/dope.console/analytics/ai-usage.md?ask=<question>&goal=<user_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.