Account & support
Review activity, analytics, and transaction history as an administrator
Use the protected administration screens to review aggregate traffic, account-access and privileged-action history, orders, refunds, and Business subscription records.
Use the administration area only when your role is authorised to handle operational, financial, or security records. The product separates aggregate public-traffic reporting from security audit history and payment ledgers so an operator can investigate a real account or transaction without treating every public visitor as an identified person.
Example only · authorised operator view
Activity, analytics, and transaction history
Each view answers a different operational question. The example uses fictional data and documentation-safe IP ranges.
Public traffic
Aggregates are available only when the optional first-party collector is enabled.
Exact public visitor IPs are not retained in the traffic dashboard.
Security and access events
Exact IP context is available only on a persisted account-access or privileged-action audit record.
Filtering access is protected by the administrator’s role and audit permissions.
| Admin area | Use it for | Recorded context | Record type |
|---|---|---|---|
| Analytics | Aggregate demand and product signals | Anonymous sessions · coarse network prefix · no exact public IP | Optional aggregate |
| Activity & access history | Security and support investigation | Recorded sign-in or privileged event · 203.0.113.45 | Protected audit |
| Orders & refunds | Payment and refund reconciliation | Order reference · captured state · persisted refund record | Financial ledger |
| Business subscriptions | Workspace plan and entitlement review | Plan · seats · provider subscription reference · verified status | Entitlement ledger |
Choose the record that answers the question
- 1Open Admin → Analytics for aggregate paid revenue, order counts, user growth, onboarding signals, top documents, and optional first-party public traffic. Public traffic is retained as short-lived anonymous sessions, page paths, referrer hosts, browser families, and coarse network prefixes—not exact public visitor IP addresses.
- 2Open Admin → Activity & access history when a permitted security investigation needs retained account-access events or privileged-panel changes. Filter by account/admin email, path, or IP address, and treat the rows as recorded history rather than proof of a person’s real-world identity or current location.
- 3Open Admin → Orders or Finance for document-order status, recorded refunds, the related payment provider identifiers, and bounded CSV exports. A row is a local operational record; reconcile an exception with the signed provider webhook and provider dashboard before changing a financial conclusion.
- 4Open Admin → Business subscriptions for the workspace entitlement ledger. It shows the local subscription binding, plan, seats, cadence, current status, and provider subscription reference. An active paid workspace is created only after the verified provider event reconciles that local record.
Handle IP and payment data carefully
- Use raw IP addresses only for a justified security, support, or compliance task and only from the protected access/audit views. Do not export or copy them into marketing lists, chat channels, or tickets that do not need them.
- Use the order reference, refund record, and provider reconciliation state together. Do not grant access, mark a refund as settled, or conclude that a charge succeeded from a browser return or a screenshot alone.
- Export only the filtered records required for the task, store them under the organisation’s approved retention process, and remove local copies when they are no longer needed.
- If optional public traffic analytics is disabled, the administration view deliberately hides historical aggregate session data as well as stopping new collection.