Users and profiles
Find a member and review only the server-scoped summary, records, statistics, timeline, and notes your role may see.
- Audience
- moderator · senior reviewer · team lead
- Availability
- free · private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Read a member profile accurately
The Users surface searches members in the selected server and opens a profile drawer backed by server-scoped summary, statistics, timeline, notes, and linked moderation data. Each subview has its own access check and may expose less than another staff member can see.
Choose the right server and member
Opening Users requires selected-server dashboard access. Detailed profile, notes, behavior, export, and timeline endpoints can require additional effective team permissions.
Open Users in the selected server dashboard, search by visible name or Discord user ID, and confirm the member identity before opening the profile.
- The correct server selected.
- A member name or Discord user ID that belongs to the investigation.
- Permission for the specific profile detail or linked record you intend to inspect.
Inspect the profile in a useful order
Search and verify identity
Use the member search, then compare display identity and Discord ID before selecting a result.
Check: The profile opens for the intended member in the intended server.
Read the summary
Review only the fields shown, distinguishing current member information from ModFlow-authored summaries or counts.
Check: Staff understand which values are identity facts and which are server-scoped aggregates.
Open linked context
Use the available timeline, records, statistics, or notes views and follow each source to its own permission-aware record.
Check: A summary does not replace the underlying source record.
Handoff precisely
Share the server, Discord ID, relevant record link, and unresolved question with another authorized reviewer.
Check: The next reviewer can reproduce the same scoped lookup without copied private data.
Profile review examples
You can identify the member and the server-scoped records visible to your role while preserving the distinction between source events, staff notes, and aggregate fields.
- Search by Discord ID when two members have similar display names.
- Open a linked moderation record to verify the reason and actor behind a profile count.
- Treat an empty timeline as the current scoped result, not proof of a clean global history.
Verify member identity before interpreting history
| Field | Use | Common mistake |
|---|---|---|
| Discord user ID | Stable member identity for search, handoff, bans/unbans, and similarly named accounts. | Using only a display name or avatar. |
| Username/display name | Readable current identity within the selected server. | Assuming names are permanent or unique. |
| Server membership state | Shows whether the account is currently resolvable as a member. | Treating an absent member as a nonexistent user or absent history. |
| Current roles/team context | Explains current server access and staff/member status where visible. | Using a current role to infer what the member had at incident time. |
| Source labels | Distinguish native ModFlow, imported, staff-authored, and linked Case data. | Treating an external provider as the human actor. |
Search narrowly
Use the numeric Discord ID whenever it is available.
Check: The intended account is selected.
Compare visible identity
Check name, ID, server, and current membership before opening linked context.
Check: Similar names do not cause a mistaken profile review.
Preserve the ID in handoff
Name the server and numeric user ID rather than relying on a mention or screenshot.
Check: The next reviewer can reproduce the lookup.
Read the profile in a reliable order
| Step | What to look for | Caution |
|---|---|---|
| 1. Summary | Identity, server membership, visible counts, current status. | Counts are not conclusions. |
| 2. Moderation timeline | Chronological warnings, mutes, jails, bans, reversals, appeals, and linked Cases. | Filters and visibility can omit records. |
| 3. Active state | Current timeout, jail, ban, pending appeal/review, or scheduled work where available. | Refresh before acting; state can change while the profile is open. |
| 4. Notes | Attributable staff observations and handoffs. | Notes are not source evidence by default. |
| 5. Linked records | Case, evidence, transcript, import, or Activity references. | Each link rechecks its own access. |
| 6. Decision | The specific question you came to answer. | Do not turn a broad profile review into an open-ended dossier. |
Explain counts, timelines, and gaps
| Visible signal | What it means | What it does not prove |
|---|---|---|
| Zero visible actions | No matching visible records in the current server/view. | No off-platform history, no hidden records, or no conduct concern. |
| Several actions | Multiple stored events meet current filters. | That every action was correct, related, or still active. |
| Imported record | A supported external source contributed a normalized observation. | Native ModFlow observation or perfect actor attribution. |
| Staff note | A named staff member added context. | Independent evidence or verified fact. |
| Missing source link | The underlying message/file is unavailable or inaccessible. | The parent record was fabricated or that the content may be copied from an unauthorized source. |
| Redacted detail | The viewer is intentionally shown a safe summary. | Permission to infer or obtain the hidden field elsewhere. |
Create a useful profile handoff
| Part | Example |
|---|---|
| Scope | Server 123…; user 456… |
| Question | Confirm whether the current timeout should end after appeal approval. |
| Relevant records | Case #104, Appeal #42, mute action timestamp. |
| Current state | Appeal approved; timeout still visible; reversal not yet verified. |
| Limit | Senior-only attachment not visible to the handing-off moderator. |
| Next owner | Senior reviewer with appeal decision and mute reversal authority. |
Understand gaps and hidden records
Resolved Discord names and avatars can change, source records can be filtered or unavailable, and local server data does not establish a portable identity profile. Do not merge people solely by display name.
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 selected server and exact Discord ID.
- Clear search filters and refresh the profile.
- Open the source record through its own access check.
- Ask a team lead to verify the relevant server-scoped permission without widening access.
A profile does not imply a score
An ordinary server profile summarizes identity, membership, visible actions, and linked records. General behavior profiling and Moderator Performance Scorecards are separate default-off systems. A profile page does not imply that either controlled system is enabled or that a score exists.