FAQ

Is SnagRelay a developer tool?

It's installed by developers (one script tag) but built for the people who report bugs — QA engineers, testers, PMs, clients, and end users. The goal is for every report to arrive with enough context that developers never need to ask for more.

Do people who report bugs need technical knowledge?

No. They click the widget, annotate a screenshot, describe the issue, and send. SnagRelay automatically captures the technical context — page state, console errors, network data, and browser/device info.

Do I need to use a separate issue board?

No. Reports go directly into the tracker you already use — Jira, Linear, Trello, GitHub, GitLab, or Azure DevOps. The dashboard is for setup and configuration, not day-to-day bug triage.

Can I run separate staging and production setups?

Yes — create a separate Project for each. Each gets its own API key and its own tracker connection, so a bug filed on staging doesn't land in your production queue. There's no built-in environment switch within a single Project.

Will the widget slow down my site?

No. It loads asynchronously and only becomes active when a visitor opens it — it has no measurable impact on page speed or Core Web Vitals.

Can I remove the "Powered by SnagRelay" watermark?

The watermark only appears on the Free plan. It's removed automatically on Studio and Agency.

What's the difference between the widget and the Chrome extension?

Web Code installs an embed script with a project API key. Chrome Extension (SnagRelay - Intelligent Bug Capture) as an Installation channel injects the widget on Match URLs after each person connects — no script tag on the site. Owners click Sign in as owner. Invited people click Authenticate Chrome from their access email.

How do I invite people to report bugs?

Invite from Team on the project Overview — see Inviting from Team. They get an email, open the magic link, then Authenticate Chrome (or Unlock a web session on Your access). They never get a dashboard account.

Does SnagRelay support team seats or SSO?

Dashboard accounts are still single-owner — there is no extra dashboard login, roles, or SSO. Team seats are invited tracker people who can report (and, on an MCP plan, fix in the editor) without becoming dashboard users. Seat capacity is on your plan; see Team and Plans & Limits.