--- title: Usage & Activity description: Track your credit consumption and activity, or review usage across your team. product: v0 type: guide prerequisites: - /docs/quickstart related: - /docs/pricing - /docs/teams - /docs/account --- # Usage & Activity The **Usage & Activity** dashboard at [v0.app/settings/usage](https://v0.app/settings/usage) shows credit consumption and activity for your personal account or team. On eligible team plans, Owners and members with the Billing role can also review team-wide data. ## What you see on the page The page looks different depending on your account, team role, plan, and billing model. | Account type and role | What the page shows | | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | Team **Owner** or **Billing** role on a Plus, Business, or Enterprise team | Team-wide and personal activity. On credit-based billing, the **Credits** tab also shows team-wide consumption. | | Any other member of an eligible team | Only their own activity. On credit-based billing, the **Credits** tab shows only their own consumption. | | Personal Free or Premium account | Personal activity and, on credit-based billing, personal credit consumption. | | An unsupported plan or billing model | The legacy usage view or a message explaining that usage data isn't available. | Credit-based accounts have **Credits** and **Activity** tabs. When credit data isn't available, the page shows **Activity** only. Owners and members with the Billing role can switch the Activity tab between **Team** and **Self**. Other members and personal accounts only see their own data. When team-wide access is available, the **licenses** badge next to the page title reports how many team members are assigned a v0 seat. ## Selecting a date range The date selector applies to whichever tabs and activity views are present, and the range carries over when you switch between them. Presets are: * **This billing cycle** (default) — only offered on credit-billed teams * **Last 7 days** * **Last 30 days** * **Last 90 days** Use the calendar icon to pick a custom start and end date, then click **Apply**. The label to the left of the selector always shows the resolved range, for example `May 1 – Jul 30, 2026`. Ranges can reach back up to 365 days. Earlier dates are not selectable, because windows that wide cannot be aggregated. ## Credits tab This tab appears when the selected account or team is billed in credits. It reports credits actually debited, split by where they came from: * **Monthly Credits** — the per-seat monthly allotment (plus daily bonus credits). Spent first, and rolls over for one month. * **Shared Pool Credits** — the team-wide purchased pool (including redeemed coupon credits). Covers the overflow once monthly credits run out, and expires one year after purchase. ### Consumption chart A stacked bar per day, with monthly credits in black in light mode or white in dark mode, and shared pool credits in blue. Days with no activity are still shown so the axis stays continuous. Hover a bar to see the monthly, shared pool, and total amounts for that day. ### Team credit usage Owners and members with the Billing role see every member with v0 access and their **Monthly Credits** and **Shared Pool Credits** for the selected range. Team totals appear in the section header, and every column is sortable. ### Per-message drill-down Click any row to see that member's individual charges. The chart above the table narrows to just that member, and the table shows: | Column | Description | | --------- | -------------------------------------------------------------------------- | | **Date** | When the charge was recorded | | **Event** | The billed event, linking to the message when you have access to that chat | | **Kind** | Monthly Credits, Shared Pool Credits, or both | | **Model** | The model that served the request | | **Cost** | Credits consumed | Charges waived because they were an auto-fix with v0 are struck through and tagged **FREE**. Click **Back** to return to the per-member view. Chat links only appear for team Owners and for your own chats. Everyone else sees the event name as plain text. ### Data freshness Credit data is aggregated, so the timestamp under the tables shows when it was last updated. Use the refresh button next to it to pull the latest numbers. ### Your credit usage Team members without team-wide access and personal accounts see a chart and transaction table for their own consumption. The table includes the event date, event type, credit source, model, and cost. Events link to chats you can access, and waived auto-fixes are struck through and tagged **FREE**. Use **Download** to export your transactions for the selected range. The CSV includes `Timestamp`, `Source`, `Type`, `Model`, `Chat ID`, `Cost`, and `Free Fix` columns. ## Activity tab The Activity tab reports how v0 is being used rather than how many credits were spent. It is available even when the Credits tab is not. ### Team activity Owners and members with the Billing role can select **Team**, then group activity by **Users** or **Projects**. Three summary cards cover the selected range: * **Active users** — members with at least one day of v0 activity * **Total chats** — chats with user-message activity * **Total messages** — messages sent across the team When grouped by **Users**, the table breaks the range down per member: | Column | Description | | ------------------ | -------------------------------- | | **Email** | Team member | | **Chats** | Chats with activity in the range | | **Messages** | Messages sent in the range | | **Days** | Days with at least one message | | **First Activity** | First message in the range | | **Last Activity** | Most recent message in the range | When grouped by **Projects**, the table shows each project's chat count, message count, active days, and first and last activity. Project names link to their project pages when they are still available. Collaborative chats count once in team and project chat totals. Messages remain attributed to the members who sent them. ### Your activity Select **Self** to review your own activity. This is the only activity scope available to personal accounts and team members without team-wide access. The summary cards show your **Active days**, **Total chats**, and **Total messages**. By default, activity is grouped by **Projects**. The table includes chat and message counts, active days, and first and last activity for each project: * Chats without a Vercel project are combined under **Draft chats**. * Activity for deleted, transferred, or inaccessible projects is combined under **Unavailable projects**. This row doesn't link to a project. * Available projects and the Draft chats row link to their corresponding pages. You can instead group by **Chats** to see each chat's project, message count, active days, and first and last activity. Available chat and project names link to their pages. Deleted, transferred, or inaccessible records are labeled as unavailable and aren't linked. ## Exporting and visualizing * **Download Table** exports the currently selected credit or activity table as CSV. * **Visualize with v0** is available for team-wide tables. It opens a new chat with the table's data attached so you can generate charts and reports. * Personal credit usage has a **Download** action that exports your transactions. For team-wide credit reporting, **Download All Transactions** exports every credit transaction in the range with `Timestamp`, `Source`, `Email`, `Type`, `Model`, `Chat ID`, `Cost`, and `Free Fix` columns. If any part of the dataset fails to load, no file is downloaded, so a partial export isn't presented as complete. ## Enterprise trials Credit consumption isn't logged during an Enterprise trial, so credit usage stays empty until the trial converts. Team and personal chat activity remain available in the Activity tab throughout the trial. Learn more about how credits work --- For a semantic overview of all documentation, see [/docs/sitemap.md](/docs/sitemap.md) For an index of all available documentation, see [/docs/llms.txt](/docs/llms.txt) For agent-facing discovery, including API and MCP surfaces, see [/docs/agents.md](/docs/agents.md)