Monitor usage and limits
Boldo separates member presence, plan capacity and AI consumption. Choose the screen that answers your question before interpreting a number or changing a subscription.
| Question | Screen | What it measures |
|---|---|---|
| When do members use Boldo? | Organization settings > Usage report | Online presence over periods and activity duration |
| How much capacity remains? | Organization settings > Information > Inventory | Repository and member counts against plan limits |
| How much AI has been consumed? | Organization settings > AI Assistant > Usage | AI budget and consumption by member, with models used |
Invoices and subscription changes belong to billing. A presence duration is not a charge, and a message count is not a unit price.
Read the presence report
The Usage report requires Administrator or Owner type and a plan that includes it. Editors and Viewers do not receive a personal version of this administration page.
- Open Usage report.
- Set the start and end dates for the period you want to examine.
- Select Precision from the available hour, day or month steps.
- Hover over a bar to inspect the number of members online during that period and the available names.
- Read each member's Distinct active periods and Activity duration in the table.
- If loading fails, click Retry and check the selected dates before interpreting an empty result.
The initial range starts at the beginning of the day seven days before today and ends today. It is not a promise of an exact 168-hour window. Dates cannot extend into the future, and the interface keeps the range in order.
Available precision adapts to the range so the chart remains manageable. A long interval does not offer every fine-grained step. Changing precision changes the number of distinct active periods; an active period is an interval containing at least one segment of online presence. Away and offline states are excluded. Activity duration totals online time and rounds up to the next minute; it is not bar count multiplied by bar width.
Presence does not measure edits, completed tasks or individual productivity. Names in a large bar's tooltip may be limited even when its total count is larger. An empty range does not prove that nobody has ever used the organization.
Read repository capacity
Open Information and inspect Inventory and the displayed plan limits. Owner, Administrator and Editor members consume non-Viewer seats; Viewers have a separate limit.
The asset counter covers nonarchived assets in the real repository. Archived assets and scenario copies do not add to that count. Real visualizations are counted across personal and shared spaces, not just the shared catalog. Active scenarios have their own counter.
A creation operation can exceed a limit through the quantity it adds, even if some capacity remains before it starts. Review the planned addition and current total rather than assuming every bulk action counts as one item.
Do not delete business data merely to test a quota. Check which objects the relevant counter includes, then decide whether to archive eligible assets, adjust the intended operation or review the plan.
Read AI consumption
Under AI Assistant > Usage, compare the selected interval and per-member consumption, with the models listed with the Boldo budget card. Current month follows the budget period and its anchor date, which may differ from a calendar month. 12 months combines that period and the eleven preceding periods. The budget card always shows the current budget period, even when the report uses 7, 30 or 90 days or 12 months.
Messages counts assistant replies. Share of Boldo usage measures the member’s share of Boldo-hosted generation and compaction tokens, not their share of messages. Use the selected interval when comparing the report’s rows.
Boldo-hosted generation and compaction consume the included budget. Your provider credentials and custom endpoints use their own arrangements. Deleting conversations does not reset the usage ledger. See AI configuration for providers and availability.
Diagnose a refused action
- Check the selected organization and the action's context: real repository, scenario, personal or shared content.
- Verify that the subscription is active and the feature is included.
- Check any organization activation switch and individual authorization for that feature.
- Check the member's type and effective permissions.
- Compare the relevant counter plus the requested addition with its limit.
- Retry only after resolving the specific cause, or send the displayed error to support.
An already exceeded plan limit can restrict further changes. A canceled or unpaid subscription is a different cause from a missing permission or exhausted AI budget. Record the message and screen instead of treating every refusal as a quota problem.