# Usage details

The **Usage Details** section provides insights into the account’s platform usage. It allows administrators to monitor consumption, analyze trends, and review usage across projects and services.

***

### Overview

<figure><img src="/files/En8ybMvRac2vXHWGVUnH" alt=""><figcaption></figcaption></figure>

The Usage Details overview summarizes key usage metrics for the selected time period.

Displayed metrics may include:

* Number of projects
* Number of users
* Storage usage
* Data transfer volume
* Encoding and transcoding time
* AI service usage

The displayed values reflect total usage across the account.

***

### Filtering and Time Range

Usage data can be filtered to refine the displayed results.

You can:

* Select a custom **date range**
* Filter by **project**
* Filter by **usage category** (e.g. storage, data transfer)

This allows detailed analysis of usage patterns.

***

### Usage History and Trends

Usage data is visualized using charts to show changes over time.

This helps to:

* Identify usage peaks
* Track growth or seasonal trends
* Support capacity planning and cost optimization

***

### Project-Level Usage

<figure><img src="/files/XSKvjRATjuaiUsPjLd0t" alt=""><figcaption></figcaption></figure>

The Usage Details section also supports project-level analysis.

You can:

* Review usage per project
* Compare usage across different content pools
* Identify projects with high resource consumption

***

### Access and Availability

* Usage Details are available at the **account level**
* Only users with appropriate permissions can access usage data
* Availability and granularity of data may depend on enabled modules and services


---

# Agent Instructions: 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:

```
GET https://docs.3q.video/user-guide-new-ui/account/usage-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.