Activity
Explore metadata-only native and supplemental imported member, voice, message, role, channel, and server events.
- Audience
- moderator · senior reviewer · team lead
- Availability
- free · private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Use Activity as an audit trail
Activity is ModFlow's metadata-only operational event ledger. It combines events observed directly by ModFlow with supplemental imported activity, groups related signals, and keeps routine activity separate from the Moderation Log.
Choose a narrow activity scope
Activity requires the separate activity.view team permission. Access to the Moderation Log does not automatically grant Activity after administrators customize team permissions.
Open Activity in the selected server dashboard, then choose native, imported, family, type, member, actor, channel, source, or date filters.
- The intended server selected.
- The activity.view permission.
- A concrete event, member, actor, source, channel, or time-range question.
Filter, inspect, and verify an event
Choose the signal scope
Select native, imported, or both, then narrow by event family and type.
Check: The explorer shows only the relevant metadata events.
Resolve people and context
Use readable subject and actor labels while treating source providers separately from actors.
Check: Primary rows stay readable without flooding the interface with raw Discord IDs.
Open exact details
Open an event to review safe metadata, timing, correlation, and collapsed provenance.
Check: The event retains its exact native or imported identity without becoming a moderation risk panel.
Check coverage gaps
Check collection status, native/imported counts, retention, and coverage-gap messaging before drawing a conclusion.
Check: Downtime, disabled collection, truncated scans, and import-only history are not mistaken for completeness.
Activity investigation examples
Authorized staff can inspect readable operational history, distinguish native observation from imports, and follow exact provenance without exposing ordinary message content.
- Confirm when a member started and stopped streaming.
- Compare a native voice move with a corroborating imported event.
- Filter role or channel changes during a specific incident window.
Know which metadata events Activity can represent
| Family | Examples | Content boundary |
|---|---|---|
| Member | Join, leave, profile/nickname/role metadata changes. | Identifiers and transitions; not private messages. |
| Voice | Join, leave, move, mute/deafen, stream/video state. | State/timing metadata; not audio or video content. |
| Message metadata | Edit/delete metadata and supported reaction-removal events. | No ordinary message body, attachment names/URLs, or media. |
| Role | Create, delete, or update metadata. | Role identity and changed fields; not hidden role-channel content. |
| Channel | Create, delete, update, or permission-related metadata where supported. | Channel identity/transition; not message history. |
| Server | Supported guild configuration/structure changes. | Allowlisted operational metadata only. |
| Imported activity | Supplemental supported provider observations. | Source-labeled, non-authoritative supplement. |
Investigate an event without over-collecting
Define the incident window
Choose the shortest useful start/end time and event family.
Check: The query avoids unrelated member activity.
Filter by exact identity
Use member, actor, channel, source, and event type where known.
Check: The result remains attributable.
Open exact detail
Read transition fields, timestamps, correlation, and provenance.
Check: The event is understood without exposing content.
Compare related records
Open the linked moderation/Case record only when the event is relevant to a decision.
Check: Metadata remains context, not automatic evidence of misconduct.
Document coverage
State native/imported scope, retention, and any collection gap.
Check: Absence is not overstated as proof.
Distinguish native and imported activity
| Dimension | Native | Imported |
|---|---|---|
| Observer | ModFlow Discord gateway listeners. | Configured external source/provider. |
| Provenance | Direct server event identity and timestamp. | Provider, source channel/message, parsed event, confidence. |
| Authority | Primary ModFlow observation for supported events. | Supplemental; does not replace missing native observation. |
| Completeness | Can have downtime, disabled collection, Discord gateway gaps, or retention limits. | Can have inaccessible history, unsupported formats, edits, deletions, or limited-scan gaps. |
| Use | Operational chronology and context. | Corroboration or historical supplement. |
Read retention and coverage warnings
The documented default Activity retention is 180 days. Older events can be absent even when they once existed. A collection-status notice can also identify disabled collection, downtime, import-only coverage, or query limits.
| Check | Why |
|---|---|
| Selected server | Activity never creates a universal cross-server history. |
| Date and 180-day boundary | The event may be outside retention. |
| Native/imported filter | The event can exist in only one source class. |
| Family/type filter | A voice move will not appear under moderation actions. |
| Collection status | Disabled collection or downtime creates honest gaps. |
| Viewer permission | activity.view is independent from Moderation Log access. |
Distinguish absence from restricted visibility
The default retention window is 180 days. Collection downtime, a disabled native collector, Discord gateway gaps, inaccessible import history, and query limits can leave gaps.
Something is missing or looks wrong
What you see: The current view does not contain the record, field, source, or output you expected.
What may be happening: Server scope, viewer permission, filters, source availability, feature gates, or stale state can change what the product may show.
What to do
- Clear filters and check the collection-status notice.
- Compare native and imported scopes without treating imports as authoritative replacements.
- Confirm the 180-day retention boundary and event time.
- Ask an administrator to verify activity.view rather than widening Moderation Log access.