> ## Documentation Index > Fetch the complete documentation index at: https://docs.clarifeye.ai/llms.txt > Use this file to discover all available pages before exploring further. # Usage > Track your organization's consumption and set alerts and limits. Clarifeye measures consumption in **CCU**. Organization admins follow it on the **Usage** page and set alerts and limits so nobody is surprised. The Usage page is available to organization admins. Members see their own consumption, limit and reset date on their **My Account** page. ## Usage Open your organization and click **Usage** in the sidebar. Pick a month with **Select month** (the last 12 months are available), then switch between the **Overview** and **Details** tabs. ### Overview * **Total CCUs**, broken down into **Parsing**, **Pipeline LLM**, **Assistant LLM**, **Work with Clara**, and **Interviews**, plus the number of active users. * **Parsed Pages**: pages parsed with the advanced (billed) parser, and the total across all parsers. * **Token Usage**: input and output tokens for conversations, Work with Clara, interviews, and document processing. * **Projects**: consumption for each knowledge store, with its alert and block limits. Select a store to open its own usage page. A **Cross-store conversations** row shows usage that isn't attributed to a single store. * **Current Monthly Users**: the number of active users right now, excluding Clarifeye staff. Click **Download CSV** to export the selected month. ### Details Use **Details** to find where consumption comes from: * Filter by date range (**From** and **To**), **Knowledge store**, **User**, and **CCU bucket**. * **Group by** knowledge store, user, conversation, model, task, or CCU bucket. Click a group to drill down into it. * The events table lists every metered event, with its store, user, model, value and CCU. Usage by Clarifeye staff is grouped under a single **Clarifeye.ai users** entry. ## Usage limits and alerts In the **Alerts** section of the Usage page, the **Usage alerts** card sets three kinds of thresholds. Leave a field empty to turn it off. | Threshold | What happens | | - | - | | **Organization balance**: **Alert when remaining CCU drops below** and **Alert when remaining % drops below** | Organization admins get an email. These alerts are informational and never interrupt service. | | **Per-user limits**: **Notify the user at** and **Block the user at** | The user gets an email and in-app alert at the notify level. At the block level, their metered actions are refused. | | **Per-store limits**: **Notify the store admins at** and **Block the store at** | The store's admins get an alert at the notify level. At the block level, every metered action in the store is paused, including document processing and connector syncs. | Per-user and per-store limits are amounts of CCU per billing period, and the notify level must be lower than the block level. They're defaults: you can override them for a single target. * **For a store**: in the **Projects** table, click the pencil icon in the store's **Limits** column and choose **Org default**, **Custom**, or **No limit**. * **For a member**: open the member from the organization's [Members](/guides/organization-settings#members) page. * **For a service account**: open it from **Service accounts**. See [Service accounts](/guides/service-accounts#set-a-usage-limit). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.