> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/settings/organization-settings/usage.md).

# Usage

The **Usage** screen in Autify Genesis shows organization-wide AI usage and storage usage. Use the **Storage** and **AI usage** tabs to switch between the two views.

***

## Storage

The **Storage** tab shows total and per-workspace storage usage broken down by category.

<figure><img src="/files/kCFwsX0ajh6wt9jOR3xh" alt="Screenshot of the Storage tab"><figcaption><p>Storage tab</p></figcaption></figure>

### Organization storage

You can view organization-wide storage usage by category.

| Item          | Description                                  |
| ------------- | -------------------------------------------- |
| **Codebases** | Storage capacity used by codebases.          |
| **Files**     | Storage capacity used by uploaded files.     |
| **Total**     | Total storage usage across the organization. |

{% hint style="warning" %}
When storage usage approaches or exceeds the limit, a warning appears. When the limit is exceeded, file uploads are disabled, so delete unnecessary files or codebases to free up space.
{% endhint %}

### Workspace breakdown

You can view storage usage per workspace (codebase, files, total).

***

## AI usage

The **AI usage** tab shows the organization-wide AI usage. Organizations in managed mode see credits and request counts. Organizations in BYOK mode see token consumption and request counts instead. For organizations in managed mode, the **Managed Credits** section appears below AI usage.

<figure><img src="/files/LGw4m4T8ougtcRLfzvbq" alt="Screenshot of the AI usage tab"><figcaption><p>AI usage tab</p></figcaption></figure>

### Managed credits

For organizations using managed mode, you can see the managed credits granted to your organization listed **per grant**. Each row shows the following values.

| Item          | Description                            |
| ------------- | -------------------------------------- |
| **Granted**   | Credits granted in this grant.         |
| **Consumed**  | Credits consumed from this grant.      |
| **Remaining** | Credits still available in this grant. |

When multiple credit allocations exist, credits expiring soonest are consumed first. Expired or fully consumed credits also appear in the history.

{% hint style="info" %}
This section does not appear for organizations in **BYOK mode**. BYOK mode has no concept of managed credit grants. The main usage metric is fixed by organization mode: managed mode shows credits, and BYOK mode shows tokens.
{% endhint %}

### Switching the time range

Use the time range dropdown to select **Current month** or **Last 30 days**.

| Option            | Description                                             |
| ----------------- | ------------------------------------------------------- |
| **Current month** | Aggregated from the start of the month until now (UTC). |
| **Last 30 days**  | Aggregated over the last 30 days (UTC).                 |

{% hint style="info" %}
Usage is aggregated in UTC and displayed in local time.
{% endhint %}

### Usage totals

Displays the main usage metric for the selected period together with the request count. Managed mode shows credits. BYOK mode shows total tokens.

### Usage breakdown

Click **Breakdown by source**, **Breakdown by workspace**, or **Token mix** to view detailed breakdowns.

| Tab                        | Description                                                                                          |
| -------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Breakdown by source**    | Usage by chat, workflow, and embeddings.                                                             |
| **Breakdown by workspace** | Usage by workspace. Click a workspace name to open its detailed usage page.                          |
| **Token mix**              | Breakdown of input, output, cached, and reasoning tokens. Shown only for organizations in BYOK mode. |

Each tab can switch between **Chart** and **Table** views.

<figure><img src="/files/PyhyTP3hkS3sOnS04XWD" alt="Screenshot of the usage breakdown"><figcaption><p>Usage breakdown</p></figcaption></figure>

***

### AI usage alerts

By setting a credit usage threshold, you can show a warning banner when the organization's AI consumption exceeds the threshold.

Only **Owners** can change alert settings. **Admins** and **Members** can only view the current settings.

#### Configuring an AI usage alert

1. Enter the number of credits at which a warning should fire in **Credit threshold** (integer, 0 or greater).
2. Enter the number of days to aggregate in **Rolling window (days)** (1 to 365).
3. Click **Save**.

<figure><img src="/files/AldMhPIPPzxjonISNcVy" alt="Screenshot of the AI usage alert settings"><figcaption><p>AI usage alert settings</p></figcaption></figure>

{% hint style="info" %}
**Rolling window (days)** specifies the period of "the last N days, including today." When the total credit usage during this period exceeds the **Credit threshold**, a warning banner appears at the top of the screen.
{% endhint %}

#### Warning banner

When the threshold is exceeded, a warning banner appears at the top of the app. The banner shows the current credit usage and the configured threshold.

* Click **Dismiss** to hide the banner in that browser tab.
* Click **Manage alert settings** to open the alert settings screen.

#### Disabling alerts

To disable alerts, clear the **Credit threshold** field and click **Save**.


---

# 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://help.genesis.autify.com/settings/organization-settings/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.
