Exports and data visibility
Download currently supported records, cases, notes, or one member's history within caller permissions and server scope.
- Audience
- senior reviewer · team lead · server admin
- Availability
- premium preview · private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Export only what the viewer may see
The Export dashboard currently links to records, cases, notes, and a specific member's history, with CSV or JSON format and supported filters. Each endpoint evaluates the selected server, caller access, and export-specific feature gate.
Confirm purpose, scope, and audience
The caller needs server dashboard access plus the required export permission/feature. Notes, cases, behavior context, and user history can be redacted or omitted according to narrower visibility rules.
Open Export in the selected server, choose one supported dataset, set a narrow date/action/member filter, and select CSV or JSON before downloading.
- A legitimate server moderation purpose for the export.
- Permission for the chosen dataset and any sensitive fields it can include.
- A secure destination and retention plan controlled by your server team.
Create and inspect a focused export
Choose one supported dataset
Select records, cases, notes, or one member's history and verify the selected server.
Check: The request targets a documented export endpoint.
Narrow the scope
Apply date, action, status, or member filters that the current panel exposes.
Check: The extract contains only data needed for the stated purpose.
Download and inspect
Choose CSV or JSON, download once, and inspect headers, timestamps, source labels, omissions, and redaction before using it.
Check: The user understands what the file actually contains.
Store and dispose of the file
Store, share, and remove the downloaded file under the server's authorized process.
Check: Exporting does not widen the audience or create indefinite unmanaged copies.
Safe export examples
The caller receives the currently supported, server-scoped fields visible to their role in the selected format, or an explicit access/validation failure.
- Export one date range of moderation records for an authorized review.
- Download case rows while expecting restricted evidence to remain omitted or redacted.
- Require a Discord user ID before exporting one member's history.
Choose the narrowest supported export
| Dataset | Use | Sensitive considerations |
|---|---|---|
| Moderation records | Date/action/source/member scoped audit review. | Reasons, actor/target IDs, source labels, and Case links. |
| Cases | Case list/report for authorized review. | Restricted evidence and comments can be omitted/redacted. |
| Staff notes | Authorized note review. | Staff-authored context and personal data require narrow handling. |
| One member’s history | Server-scoped history for a specific Discord user ID. | Must not become a global profile or unrelated-data dump. |
| Case-specific export | A single Case report where the Case control permits it. | Visibility and evidence access still apply field by field. |
Create and validate an export
State the purpose
Name the review, date range, member, Case, or compliance need.
Check: The export has a legitimate, specific purpose.
Choose one dataset
Avoid combining unrelated records when one dataset answers the question.
Check: The data minimum is smaller.
Apply filters
Set date, action, status, source, or member filters currently exposed.
Check: The extract excludes unrelated rows.
Choose format
Use CSV for tabular review and JSON when structured fields are required.
Check: The format matches the workflow.
Download once and inspect
Check filename, headers, server ID, timezone/timestamps, source labels, redaction, and row count.
Check: The file content matches the request.
Secure and dispose
Store/share only with authorized people and remove the copy under the server’s process.
Check: Export does not create indefinite unmanaged copies.
Interpret omitted and redacted fields
| Reason | Meaning | Response |
|---|---|---|
| Viewer permission | The caller cannot export a field/item they cannot view. | Use the visible summary or hand off to an authorized reviewer. |
| Record visibility | A Case, note, or evidence item has narrower visibility. | Do not infer or reconstruct it. |
| Source unavailable | The source message/file no longer exists or cannot be read. | State the gap and retain provenance metadata. |
| Dataset schema | The selected export intentionally contains only supported fields. | Do not promise a universal archive. |
| Point-in-time state | The export reflects data at download time. | Record the export time and regenerate only when necessary. |
Recover from a wrong, missing, or duplicate export
The export is empty or missing expected rows
What you see: The file downloaded but does not contain the expected data.
What may be happening: Selected server, dataset, filters, date/time interpretation, permission, source availability, or point-in-time state can narrow the result.
What to do
- Confirm the server, dataset, member ID, and filters.
- Compare a small dashboard result with the export.
- Check whether the missing record is hidden, redacted, or outside the date range.
- Report a reproducible schema mismatch without sending the sensitive file.
The export contains too much data
What you see: The file includes unrelated records or a wider range than intended.
What may be happening: Filters were omitted/misread or the wrong dataset/server was chosen.
What to do
- Stop sharing the file.
- Delete the unintended local copy under the server process.
- Create a narrower export once.
- Report any unauthorized exposure through the security/privacy path using identifiers only.
Explain omissions and redactions
Exports reflect current stored data, filters, redaction, and local runtime defaults. They do not promise indefinite retention, cross-product import compatibility, complete off-platform history, or recovery after the source is removed.
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
- Confirm dataset, server, filters, and required member ID.
- Read the endpoint's access or validation message.
- Compare a small export with the corresponding dashboard view.
- Report missing fields without requesting owner-level or cross-server access.
Protect copies outside ModFlow
Export formats, row caps, date windows, and redaction vary by dataset and permission. An export is a point-in-time copy: later correction, deletion, permission loss, disconnect, or retention cleanup in ModFlow does not retract files already downloaded or shared by an authorized recipient.