Review detections and resolve conflicts
Understand what Canvas found, decide what stays visible, and resolve uncertain or conflicting detections.
Outcome
Every important detection is marked, kept, or routed to a next action before export or sharing.
Your progress
Mark each step as you complete it. This is saved only in this browser.
0 / 3 steps complete
Before you start
Visual frame
Review asset
Detection review and conflict storyboard
Synthetic detection data only. Categories use semantic colours so the review state, not decoration, carries the meaning.
Synthetic frame
Detection review
Work from the list, then verify the preview.
Review detections and resolve conflicts workflow frame
Instructional frame for this workflow. Use product screenshots or animation captures after the article copy is stable.
Guided steps
Follow the task, then check the result.
Scan the detection list
Start with the detection list instead of reading the whole document line by line. Look for high-risk categories first, then work through uncertain items.
Resolve each uncertain item
For each item, choose the action that matches your intent: redact it, keep it visible, or reclassify it if the category is wrong.
Confirm the document state
Before export, look at the document or output preview as a recipient would. The review list is a guide; the final output still needs human inspection.
Branch questions
Can you see the screen or control described in Review detections and resolve conflicts?
Completion check
Support boundary
Support can use by default
- Article slug and selected workflow step.
- Screen or action name, such as Canvas review, Vault resume, or Share package.
- Browser, viewport, file type category, and error category when relevant.
- Synthetic sample shape or redacted sample only after review.
- Intent ID
- Article slug
- App route
Requires your consent
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user
Not collected by default
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
Safe support summary
Copy a scrubbed handoff.
Redactorr KB support summary Article: /knowledge-base/review-detections-conflicts Selected issue: A review action does not change the document state. Playbook progress: 0/3 steps marked complete Safe context to include: - Article slug and selected workflow step. - Screen or action name, such as Canvas review, Vault resume, or Share package. - Browser, viewport, file type category, and error category when relevant. - Synthetic sample shape or redacted sample only after review. - Intent ID - Article slug - App route Requires explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture User note: - Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.
Article details
Review detections and resolve conflicts
Understand what Canvas found, decide what stays visible, and resolve uncertain or conflicting detections.
Outcome
Every important detection is marked, kept, or routed to a next action before export or sharing.
Before You Start
- Complete scanning first.
- Know what kind of document you are reviewing.
- Keep a human final review step before sharing.
1. Scan the detection list
Start with the detection list instead of reading the whole document line by line. Look for high-risk categories first, then work through uncertain items.
Check before you continue: You know which findings are confirmed, uncertain, or wrong.
2. Resolve each uncertain item
For each item, choose the action that matches your intent: redact it, keep it visible, or reclassify it if the category is wrong.
Check before you continue: No uncertain high-risk finding is left undecided.
3. Confirm the document state
Before export, look at the document or output preview as a recipient would. The review list is a guide; the final output still needs human inspection.
Check before you continue: The final preview matches the decision you made for each important item.
Completion Check
- Each high-risk item has an intentional decision.
- Missed values and false positives have been routed to the right playbook.
- The preview or output check matches the review state.
Safe Examples
- Fake customer email and phone values.
- Synthetic internal ID shapes such as CUST-12345.
If You Need Support
Contact support when:
- A review action does not change the document state.
- The same item keeps returning after you resolve it.
Include only support-safe context:
- Article slug and selected workflow step.
- Screen or action name, such as Canvas review, Vault resume, or Share package.
- Browser, viewport, file type category, and error category when relevant.
- Synthetic sample shape or redacted sample only after review.
Still stuck?
Copy a safe article handoff.
Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.
- Article slug
- Selected issue
- Screen name
- Action name
Redactorr support case Source: Article playbook: review-detections-conflicts Route: /knowledge-base/review-detections-conflicts Selected issue: A review action does not change the document state. Safe context: - Article slug and selected workflow step. - Screen or action name, such as Canvas review, Vault resume, or Share package. - Browser, viewport, file type category, and error category when relevant. - Synthetic sample shape or redacted sample only after review. - Article slug - Selected issue - Screen name or article section - Action name Only include with explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture - Hidden diagnostic uploads User note: - Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.
Support case builder
One case format, wherever you start.
This is the same support case shape used by diagnostics and article handoffs.
- Article slug and selected workflow step.
- Screen or action name, such as Canvas review, Vault resume, or Share package.
- Browser, viewport, file type category, and error category when relevant.
- Synthetic sample shape or redacted sample only after review.
- Article slug
- Selected issue
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions