Skip to main content

Secure evidence

Attachments, Screenshots, and Sensitive Information

Attachments can make troubleshooting faster, but they should contain only the customer and system information needed for the specific ticket.

On this guide
  1. Before attaching a file
  2. Useful evidence
  3. Finish and verify the customer action
Browse all guides →
1

Before attaching a file

  1. Confirm the file belongs to the same customer, site, and ticket.
  2. Crop or redact unrelated people, customers, browser tabs, email addresses, IP details, account numbers, and desktop content.
  3. Never attach passwords, one-time codes, private keys, recovery codes, API secrets, enrollment tokens, or unredacted credential screens.
  4. Use the smallest useful file and a descriptive filename.
  5. The production portal maximum is 15 MB per file; email systems can impose a lower limit.
Back to top ↑
2

Useful evidence

  1. A screenshot with the complete error message and visible time.
  2. A device or panel photo that includes the relevant label or indicator without exposing credentials.
  3. An example event time, camera name, door, user, workstation, or transaction that DSE can reproduce.
  4. A short log excerpt around the failure after secrets and unrelated data are removed.
  5. A description of what was happening immediately before and after the evidence was captured.
Back to top ↑
3

Finish and verify the customer action

  1. Wait for the confirmation page, updated conversation, email, or account message before repeating the action.
  2. Confirm the customer, company, site, DSE-###### ticket, and visible status are the ones you intended.
  3. Save the confirmation or reply on the same ticket when more information is needed.
  4. Contact DSE immediately if account or ticket visibility includes unrelated customer information.
Back to top ↑

Visual references

Open any image to see it full size. Annotated images use numbered callouts to guide you.

Illustrated DSE secure attachment and screenshot checklist.Open full size ↗
Visual 1Illustrated customer-safe information handling example. All records are fictional.
Illustrated DSE ticket conversation and reply workflow.Open full size ↗
Visual 2Related workflow: Illustrated signed-in customer example. All names and ticket records are fictional.
Annotated DSE walkthrough for Attachments, Screenshots, and Sensitive Information with three numbered red callouts, boxes, and arrows.Open full size ↗
Visual 3Annotated walkthrough: follow red callouts 1 through 3 to confirm context, complete the action, and verify the result. The screenshot is a sanitized training view with fictional records.
Before you finish
  1. Confirm context. Recheck the DSE domain, signed-in account, company or site, ticket number, device, and request type shown on screen.
  2. Confirm the result. Perform one harmless verification and make sure the visible status matches what you expected.
  3. Keep the reference. Save the DSE-###### ticket number, confirmation, or other safe reference needed to continue the same conversation.
  4. Stop on a mismatch. Do not repeat a high-impact action. Preserve a safe screenshot, note the time and exact error, refresh once, and update or open the correct DSE ticket.

Content owner: DSE Service Operations. Reviewed July 16, 2026. Examples and visuals use fictional data.

Please Wait!

Please wait... it will take a second!