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
Support

Troubleshooting

If something doesn’t behave as expected, start with these quick checks before digging into logs.

Widget not seen

  • • Confirm the origin matches exactly in Project → Allowed origins.
  • • Ensure the publishable key matches the project.
  • • Check that `/v1/projects/config` responds with 200.

Evidence missing (screenshot/replay/telemetry)

  • • Check project toggles (screenshots/replay) and org Data & Privacy policy.
  • • If you hit plan limits, evidence may be dropped while reports still work.
  • • Verify storage provider is configured and healthy.
  • • If browser console shows a presigned upload CORS error, add the page origin to the R2 bucket CORS allowlist.

OTP not delivered

  • • Confirm email delivery is enabled for your workspace.
  • • Make sure the sender address or domain used for login emails is verified.
  • • If other users also stop receiving codes, ask an administrator to check the mail provider connection.

Magic link opens the wrong place or fails after click

  • • Open the admin app from its normal sign-in URL, not from a copied preview or internal host.
  • • If your team recently changed domains, ask an administrator to verify the sign-in redirect domain.
  • • Request a fresh magic link after any domain or login configuration change.

Access denied

Double-check that you are signed into the correct workspace, still have access to the organization, and are using the expected production host. If the problem started after a domain or SSO change, ask an administrator to review access and sign-in routing.