Platform usage analytics (Master)
The operator screen that consolidates, across all organizations, who is really using the product (engagement), which resources they consume and which accounts are dormant, with aggregate metrics only, never the customers’ business data.
Usage analytics is a screen EXCLUSIVE to the platform operator (Master profile), under Platform → System usage. It aggregates ALL organizations to answer three questions: who is really using the product, what they are consuming and who stopped using it. Like every Master screen, it shows only aggregate metrics and counts, never the content of a customer’s business data, and one organization’s usage is never exposed to another.
Overview (KPIs)
At the top sit the platform indicators: active vs. total organizations, dormant organizations, total and active users, DAU/WAU/MAU (distinct users active over 1, 7 and 30 days) and total storage. They are computed from the audit trail (logins and actions) and from the real storage of attachments.
Engagement by organization
The engagement table shows, per organization: status (active, at risk or dormant), engagement score, users active in 7 and 30 days, total users, action volume over the last 30 days, breadth of features touched and the date of the last login. It all comes from the audit trail, so it depends on the organization recording accesses and actions.
Resource consumption
The consumption section sums, for the current month, usage events per metric (storage, API, compute, egress and AI tokens), with platform totals and a ranking of the largest consumers of each resource. Values are net of reversals. When per-request metering is off this section may appear empty; storage, however, always reflects the real attachments.
Dormant accounts
The last section lists organizations and users idle for more than N days (adjustable threshold: 14, 30, 60 or 90), sorted from the most to the least dormant. It includes those who signed up but never used it and those who stopped, with the date of the last access and the “days dormant”. It is the list to act on churn.
- Review “at risk” organizations weekly before they turn dormant.
- Use the consumption ranking to understand cost and capacity per customer.
- Adjust the day threshold to separate those who cooled off from those who truly left.