Report a Canvas issue safely
Give support enough context to help without sending raw private document content by default.
Outcome
You can describe a Canvas issue with safe context, screenshots only when masked, and synthetic reproduction examples.
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
Safe Canvas support report storyboard
Synthetic support report only. It shows the exact boundary between safe context, consent-only context, and material that is not collected by default.
Synthetic frame
Safe issue summary
Enough context to route the issue.
Report a Canvas issue safely 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.
Name the screen and action
Start with where you were and what you clicked: upload, scan, review, export, Vault, Share, Open Package, or AI Assistant.
Add safe details
Include file type category, browser, viewport, error category, selected article, and whether the issue repeats. Keep private values out.
Use a synthetic reproduction
If support needs an example, create a fake value with the same shape. Replace real names, emails, account numbers, IDs, and file names.
Branch questions
Can you see the screen or control described in Report a Canvas issue safely?
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/report-canvas-issue-safely Selected issue: A safe diagnostic path does not route to the right article. 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
Report a Canvas issue safely
Give support enough context to help without sending raw private document content by default.
Outcome
You can describe a Canvas issue with safe context, screenshots only when masked, and synthetic reproduction examples.
Before You Start
- Know the screen, action, and symptom you saw.
- Do not attach raw files or unmasked screenshots by default.
- Use synthetic examples when support needs a reproduction shape.
1. Name the screen and action
Start with where you were and what you clicked: upload, scan, review, export, Vault, Share, Open Package, or AI Assistant.
Check before you continue: The issue can be routed without seeing document contents.
2. Add safe details
Include file type category, browser, viewport, error category, selected article, and whether the issue repeats. Keep private values out.
Check before you continue: The report contains action context, not raw private material.
3. Use a synthetic reproduction
If support needs an example, create a fake value with the same shape. Replace real names, emails, account numbers, IDs, and file names.
Check before you continue: The example shows the problem without exposing the original value.
Completion Check
- The report identifies screen, action, symptom, and browser context.
- No raw original document text is included by default.
- Any screenshot is masked or replaced by a synthetic reproduction.
Safe Examples
- Use CUST-12345 instead of a real customer ID.
- Use [email protected] instead of a real email.
If You Need Support
Contact support when:
- A safe diagnostic path does not route to the right article.
- A Canvas, Vault, Share, or export issue repeats after following the matching playbook.
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: report-canvas-issue-safely Route: /knowledge-base/report-canvas-issue-safely Selected issue: A safe diagnostic path does not route to the right article. 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