Person Profiles

Use This Dashboard Area Safely

Use this guide when a safety, accountability, or follow-up record needs careful handling. In this guide, Person Profiles narrows that work to how to group reports about the same person without confusing identity, evidence, or accountability. Because this is a surfaces page, read it as part of the Report System learning path rather than as an isolated checklist.

A report is a written memory of something important. The goal is to protect people, keep facts clear, and leave enough context for future reviewers. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Trust and Safety staff and Partner admins. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /reports/profiles.
• Records or contracts involved: Person profiles, Profile links, Profile audit entries, and Incident reports.
• Main care point: Watch for incomplete facts, unfair wording, privacy exposure, or a decision that another reviewer cannot understand later.
• Proof worth keeping: report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the Report System situation, the owner, and the exact item involved in Person Profiles.
2. Read the current state before changing it: Use /reports/profiles to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the smallest action that matches the task: Keep Person profiles, Profile links, Profile audit entries, and Incident reports in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: Before handing off, save proof such as report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner so another reviewer can understand the facts without relying on memory.

Before You Leave The Screen

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on people, privacy, fairness, evidence, and the trustworthiness of the record.
3. Proof is findable: The handoff points to evidence that another reviewer can understand the facts without relying on memory.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Identify the report and scope. Search for the person using known identifiers before creating or linking a profile. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the existing facts before acting. Review similarity suggestions and existing linked reports carefully. Pause here and confirm the note is factual, fair, and reviewable.
3. Step 3 - Make the smallest factual update. Link reports only when the identifiers or evidence support the connection. This keeps the report useful to the next reviewer instead of only to the person writing it.
4. Step 4 - Check fairness, privacy, and risk. Update profile notes with neutral, factual context and avoid private details that are not needed. The next action should still protect privacy, evidence, and due process.
5. Step 5 - Verify the saved record and history. Save, then confirm the linked report count and visible identifiers are correct. A later reviewer should be able to understand this step from the saved record.
6. Step 6 - Hand off the next responsibility. If a link is wrong, unlink it with a note explaining the correction. This leaves a handoff trail another operator can understand.

Purpose

/reports/profiles helps staff group multiple reports about the same person. This is useful when a person uses different names, handles, accounts, or emails across incidents.

Profiles help show patterns, but they must be handled carefully. A wrong link can unfairly attach one person’s report history to another person.

What a profile can contain

• Display name.
• Known aliases.
• Handles or account names.
• Emails or contact identifiers.
• Notes.
• Linked incident reports.
• Changelog or audit entries.

Similarity suggestions

The dashboard may suggest potential matches when reports share identifiers. A suggestion is not proof. It is a prompt to check carefully.

Link and unlink rules

Action	Use when	Record effect
Create profile	A person needs a single identity record.	Creates profile and audit entry.
Link report	Evidence supports that the report belongs to the same person.	Creates profile link.
Unlink report	Link was wrong, outdated, or not supported.	Removes link and records history.
Update profile	New verified identifier or correction exists.	Updates profile and audit entry.
Delete profile	Profile is unsafe or no longer needed.	Removes profile links, not the reports themselves.

Common mistakes

• Treating similarity as proof.
• Adding private identifiers with no safety need.
• Linking reports across partners without enough context.
• Deleting a profile to hide past mistakes instead of documenting correction.
• Forgetting to review linked reports before a ban or network decision.