Imports from configured sources
Monitor approved external sources, review ambiguous moderation, and route supplemental activity into Activity.
- Audience
- team lead · server admin
- Availability
- premium preview · private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Reconcile trusted external records
Imports configures approved Discord source channels or categories and separates incoming history into Needs Review, confirmed Moderation, and Imported Activity. It is a source-health and reconciliation workflow; routine imported activity belongs in Activity instead of becoming correction work.
Verify the source before importing
Only authorized server staff can configure sources, preview rows, or run supported reconciliation. Feature entitlement/preview and access to the selected Discord sources are both required.
Open Imports, confirm source health, and begin in Needs Review before changing any classification.
- An approved source channel/category in the same server.
- Knowledge of the source bot or log family and expected record shape.
- A review plan for unknown or low-confidence preview rows.
Preview, reconcile, and record provenance
Check source health
Confirm configured channels or categories, provider labels, observed status, and explicit moderation/activity/unknown counts.
Check: A stale or misconfigured source is visible before review begins.
Review ambiguous moderation
Use Needs Review for low-confidence moderation or unknown rows that could represent moderation.
Check: Routine activity and unrelated unknown noise do not inflate the moderation review queue.
Confirm attribution
Read Source and Actor separately, then save a correction only when the target, actor, family, and action are supportable.
Check: The provider never masquerades as the moderator.
Inspect supplemental activity
Use Imported Activity summaries and open the filtered Activity explorer for event detail.
Check: Imported operational history remains supplemental and does not flood the Moderation Log.
Import review examples
Ambiguous moderation is reviewable, confirmed imported moderation remains source-labeled, and routine imported activity is summarized and handed off to Activity.
- Review a low-confidence mute without treating the source bot as the actor.
- Open imported stream events in Activity by provider and event type.
- Leave unrelated unknown status messages outside moderation review.
Check source health before reviewing rows
| Check | Meaning | Safe action |
|---|---|---|
| Configured source ID | The channel/category currently selected for import. | Resolve the ID to the intended Discord object. |
| Provider/log family | The parser expected for source messages. | Confirm messages actually use the supported format. |
| Access/observation status | Whether ModFlow can read the source and has recent observations. | Repair source permission before reconciling missing history. |
| Moderation/activity/unknown counts | How preview rows were classified. | Focus review on ambiguous moderation, not routine noise. |
| Last observed/time window | Coverage recency and scan boundary. | State the limit; do not assume older history was scanned. |
Understand preview classification and attribution
| Destination | Contains | Review rule |
|---|---|---|
| Needs Review | Low-confidence moderation or unknown rows that could represent moderation. | Confirm target, actor, action, occurrence time, source, and confidence before publishing. |
| Moderation | Confirmed supported moderation incidents. | Keep source/provider labels and compare for duplicates. |
| Imported Activity | Supplemental operational events. | Open in Activity; do not reclassify as moderation by default. |
| Unrelated unknown/noise | Messages that do not support a moderation/activity interpretation. | Keep outside the moderation queue. |
| Field | Meaning |
|---|---|
| Provider/source bot | Where the observation came from. |
| Actor/initiator | The moderator/system represented as requesting the action, when supportable. |
| Executor | The bot/system that applied the action, when represented. |
| Target | The member/user affected. |
| Occurrence time | When the source says the incident happened. |
| Source message | The Discord channel/message that supports provenance. |
| Confidence | Parser confidence; not truth or guilt. |
Reconcile records without duplicates
Review source and row
Confirm the source message, target, action, actor, reason, and occurrence time.
Check: The row is supportable.
Search existing history
Check native and imported records for the same incident window and target/action.
Check: A likely duplicate is identified before publication.
Resolve contradictions
Hold low-confidence or conflicting observations in review.
Check: ModFlow does not invent missing actor/target data.
Publish or dismiss
Confirm the supported moderation row, route routine activity to Activity, or leave unsupported noise out.
Check: The correct product history receives the row.
Verify chronology/source label
Open Moderation Log or Activity and confirm occurred-at ordering and provenance.
Check: A later backdated import does not distort incident chronology.
Know import limits and reserved backfills
- Edited, deleted, unusual, or unsupported source messages can be skipped or classified as unknown.
- Discord permissions and channel history availability limit what can be reviewed.
- A parsed record can still contain wrong or ambiguous source data.
- Imports supplement native ModFlow records; they do not replace missing native observation.
- Low confidence must remain visible and must not be silently converted into a definitive actor or target.
- Changing historical-import operating procedures remain reserved and are not documented here.
Handle unsupported or conflicting records
Parsing depends on supported external log shapes and accessible Discord history. Edited, deleted, unusual, or unsupported messages can be skipped or classified as unknown; imports cannot fill every native collection gap or prove the original event was correct.
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 the source channel/category and provider.
- Check Needs Review before changing a confirmed moderation row.
- Open Imported Activity in Activity rather than reclassifying it by default.
- Remove or correct a source configuration through the supported control when provenance is wrong.
Treat presets as parsers, not endorsements
Named import presets describe supported parsing templates; they do not mean the external product sponsors ModFlow or that ModFlow has a direct provider partnership. Imported raw logs, unresolved rows, corrected mappings, and resulting moderation records can have different retention and visibility.