# Usage Review personal or organization usage and configure eligible daily coding allowances. ## Where to find it Open **Account > Usage**. Address: `/account/usage`. ## Use this page Review personal feature usage by month; billing viewers can switch to organization totals and people. Manage personal daily coding limits; billing managers can define tiers with daily allowances, assign people and grant unlimited user allowances within the organization cap. Usage metering helps administrators and finance understand which features consume resources, who initiated work, and which customer the work relates to. It can support usage reviews and billing reconciliation alongside the existing Billing page. Open **Usage** from the account menu or Billing. **My usage** shows only the signed-in member's attributed activity. Members with billing visibility can choose **Organization** to see totals and filter by person. Managing organization limits separately requires billing-management permission. Availability depends on the release installed for your organization; an unavailable report is not zero usage. ### What can be measured | Feature | Measurement | How to interpret it | | --- | --- | --- | | Chat | Model tokens | Token usage from recorded chat invocations; provider counters and costs remain separate. | | Customer Profiles operations | Profile operations | Work associated with a customer, including background work that may have no initiating user. | | Customer Profiles monthly usage | Active customer-month quantity | Quantity from the monthly commercial statement; this is a tenant-level measure and cannot always be broken down by person or individual customer. | | SMS | Message segments | Actual provider evidence is required for settled usage; estimated segments remain provisional. | | Build | Coding credits | Usage linked to coding reservations; raw model tokens and provider costs are separate measures. | These measurements cover their supported source records. They do not imply that every connector, feature, historical period, or background action is metered. Your organization is the account boundary; a customer grouping refers to a customer identifier recorded by a source within that organization. A user or customer breakdown is available only when the source has the required identity evidence. Unknown attribution stays unattributed. Renaming or deactivating a member does not move their past usage to someone else. ### Review your usage 1. Open **Usage**, choose **My usage** or the authorized **Organization** view, and select a UTC calendar month and feature. Organization viewers can narrow the results by person. Personal reports show allowances and quantities without dollar amounts. Select the current month to view or update today's daily coding allowance and personal controls. 2. Confirm which sources and dates are covered. An empty result is not proof of zero consumption; a partial first month or missing historical evidence may remain incomplete. 3. Review feature quantities and allowance credits separately. Detailed dollar spending remains in authorized billing and administration views. Different units cannot be added into one usage total. Internal provider costs, shared cost allocations, pricing internals and source references are excluded from this page. Missing charges are unknown, not free usage. 4. Review recent activity and any truncation notice. Totals include the complete filter, even when only the latest 100 events are displayed. Ask your Topline contact for unresolved items and late corrections to be reconciled to their source evidence before using the results for a billing decision. A corrected record retains revision history, and retrying the same source event does not create another charge. For example, a chat token total describes measured consumption. It does not on its own establish the amount owed. A missing SMS actual remains pending even if an operational segment estimate is available. ### Tiers, daily allowances and recovery Daily coding limits reset at **00:00 UTC**. Usage shows the next reset in your local time. Settled coding charges count on the UTC day they reconcile; reserved or pending work continues to count until it settles or is released, even across midnight. A reset can therefore leave less than the full daily allowance available. - Administrators with billing-management permission define named usage tiers, each with a daily coding allowance. They choose a default tier and assign a different tier to selected people. Choosing the default for a person restores inheritance. Editing a tier changes the allowance for its members; lowering it below usage already committed can block new work until reset. - An administrator can grant an **Unlimited user allowance** override. It removes that person's tier daily allowance and administrator per-person monthly allowance restrictions. Organization access, monthly spending caps, paid-usage pause and concurrency limits still apply. It never authorizes unlimited organization spending or bypasses a member's own pause or tighter daily limit. - Every member can set a tighter personal daily limit or pause their own new coding work. Clearing a personal limit restores the administrator's allowance; it does not raise that allowance or change organization settings. Personal pause remains in place until the member deliberately resumes. - The organization's monthly spending cap, existing administrator limits and access controls still apply. A daily reset does not refill a depleted monthly organization budget. **Billing** remains the place for authorized administrators to manage the monthly organization budget and paid-usage policy. Members see their effective tier, daily allowance, usage and next reset. Tier names and allowances are organization-defined; these controls do not create a subscription price, charge a card or change the organization's commercial plan. If no tier is assigned, existing organization controls remain authoritative. When blocked, read the reason before retrying. For a personal daily limit, wait for the displayed reset or adjust your own restriction within the administrator's limits. For an administrator limit or a paused organization, contact your admin. For pending work, let the task settle or investigate its status. A missing coding plan requires administrator setup; saving a personal limit never creates a price or enables billing. Existing tasks still consume their authorized reservations. Starting a task requires enough remaining credits for its initial reservation. If the full tier allowance is smaller than that reservation, a daily reset will not help: an administrator must raise the tier allowance or change the assignment. Daily spending controls currently apply to coding. The other meters provide visibility; a displayed quantity does not imply a configurable daily spending cap for chat, profiles or SMS. ### Availability and billing decisions To use metering for your organization, Topline must confirm that the required release and database changes are installed, source capture is healthy, and the requested period has sufficient coverage. A member without a stable attribution identity receives an explicit unavailable-attribution state rather than other people's activity. Organization totals can include unattributed background work. Viewing a report does not enable a feature, choose a price, or activate usage-based billing. Any billable feature still needs its existing enablement process and an approved commercial policy. Ask your Topline contact to review those options and the applicable price and effective date before activation; metering has no universal billing-on control. A closed metering month freezes the reviewed measurement evidence. Invoice approval remains a separate process. Late usage or corrections stay visible for review and do not silently rewrite a closed invoice. Existing billing statements remain authoritative; metered copies must not be charged a second time. ## Related guides - [Billing](/docs/billing) - [Question assistance](/docs/question-assistance) ## Access, states, and recovery Personal views are bound to the authenticated identity. Daily coding allowances reset at 00:00 UTC; pending work and monthly organization caps still apply. Unknown data remains unknown, and errors offer retry or a specific recovery path. Controls and availability depend on the active account and your permissions. If a page is unavailable, verify account access before changing configuration.