Activity History
Understand what the Activity page records, how it differs from live panels, and when audit history is the right source of truth.
Activity is durable history
The Activity page records organization-level operational history that should remain available after the live moment has passed.
Current activity categories include:
- access events
- database events
- player-admin events
- server status events
Admins can also filter the page by server when they want a narrower audit trail.
Activity is not the live console
EnderDash has several time-oriented surfaces, and they serve different jobs:
- Console is for log lines and command output
- Events is for structured live event streams
- Activity is for durable audit and operational history
If you need to answer "what just happened right now?", live panels are often the better source. If you need to answer "what changed, who changed it, and when?", Activity is the right page.
Why Activity is admin-only
Activity can include sensitive operational data across the whole organization, not just a single granted server.
That is why the page follows the elevated organization-role model instead of ordinary member access.
HTTP API relationship
The same activity data model is also exposed through the HTTP API, with the same general access expectations.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on