Reports, analytics, exports and audit activity

Prerequisites and authority

Use an individual staff account with the action permission and required organization module/license. Viewing a menu does not establish permission to mutate records.

Read reports with their context

Reporting & Analytics includes Overview, Subscribers, Revenue & Finance, Subscriptions, Network, Locations and Reports in the inspected navigation. Several areas require advanced analytics or reporting entitlements as well as permissions.

1. Select the period and applicable location or other filters.
2. Confirm the timezone and whether data is live or summarized.
3. Inspect the underlying records before interpreting a change.
4. Export through the supported action and retain the filter context.
5. Reconcile important totals with the authoritative payment/subscription records.

Revenue can differ from entitlement value when manual grants, complimentary access, imported subscriptions, refunds or pending payments are involved. Do not call every subscription a paid sale. Subscriber and active-session counts also answer different questions.

Network analytics depend on sampling and router reachability. A stale graph is not proof that traffic stopped. Compare the last successful sampling run and the relevant router status.

Exports can contain customer information. Share only what the recipient needs and redact public examples. Record the report period and generation time so another operator can reproduce the result.

Audit Logs and System Activity explain actions and technical events; they are not interchangeable with financial reporting. Use Administrative session and audit investigation when reconstructing a change.

Related guides

Related guides: Staff accounts, roles and permissions, Administrative session and audit investigation, System operations and task controls, Roles and permission matrix.