verityStart free
Documentation

Setup, workflow, and governance docs.

Installation, capture settings, inbox workflow, integrations, and security controls for teams using Verity in real environments.

Docs signal map
Documentation signal map
Evidence

Evidence overview

A report can include optional evidence attachments. Evidence is controlled by project settings, organization policy, and plan limits so teams can keep capture useful without drifting into surveillance.

Evidence types

  • Screenshot upload
  • Annotation overlay and annotated image variants
  • Session replay when opt-in is enabled
  • Technical telemetry such as console or network diagnostics
  • Capture bundles for server-side processing

What controls evidence

  • Organization policy defines the boundary for what a widget may capture.
  • Project settings choose the default evidence posture within that boundary.
  • Plan limits add the final storage and quota constraints.

Feedback flow

Feedback stays note-first. The reporter starts with the message and only adds more context when it helps. This is the calm default for production-facing feedback.

QA flow

QA is evidence-first. When capture bundles are allowed, the primary action is Generate screenshot. If capture is blocked on a page, the reporter can still upload or paste a screenshot and keep the rest of the evidence pack intact.

When limits are hit

If you exceed plan limits, Verity may still accept the report but drop evidence such as screenshots or replay to avoid runaway storage. That keeps intake moving without silently expanding the data surface.