Screenshot redaction

Screenshots make support faster, but they can leak sensitive data.

Default source

Use staging for all documentation screenshots unless a workflow only exists in production. Prefer synthetic tenants and test users.

If production is unavoidable, crop tightly and redact aggressively before the image leaves the browser.

Always redact

• API tokens.
• Passwords or secret fields.
• Customer employee lists.
• Unrelated customer names.
• Personal email addresses unless needed for the issue.
• Authentication metadata that is not already public documentation.

Usually safe to show

• Page title.
• Non-sensitive button labels.
• Error messages.
• Empty form field labels.
• Organization name when the ticket is for that organization.

Good screenshot pattern

1. Capture only the relevant browser area.
2. Crop unrelated navigation or rows.
3. Redact sensitive values.
4. Add one sentence explaining what the screenshot proves.