SnagRelayDocs
Getting Started

Core Concepts

The vocabulary used throughout the dashboard and these docs.

Project

A Project is the unit everything else hangs off: one widget install, one API key, one connected tracker. It's named automatically from whatever you connect (a Jira project, a Linear team, a Trello board, a GitHub/GitLab repo, or an Azure DevOps project) rather than a name you type yourself.

No environments — use separate Projects

There's no staging/production toggle inside a Project. If you want to keep staging reports out of your production tracker queue, create a second Project with its own API key and point your staging site's script tag at that key instead.

Your account can have multiple Projects, up to what your plan allows (see Plans & Limits).

Issue

An Issue is one widget-originated bug report. It tracks:

  • The captured payload (screenshot, console/network data, session replay reference)
  • Its submission status — pending, success, or failed
  • Its linked tracker entity — the real Jira/Linear/Trello/GitHub/GitLab/Azure item it created
  • Duplicate-detection results

Integration

The connection between a Project and an issue tracker. SnagRelay supports six: Jira, Linear, Trello, GitHub Issues, GitLab, and Azure DevOps Boards. Most use an OAuth popup; Azure DevOps also supports a Personal Access Token. See Integrations for details on each.

Installation channel

Each Project picks one capture channel on the Installation tab: Web Code, WordPress, or Chrome Extension. Extension replaces the embed for that Project. See Installation.

Team

A tracker person on the project Team list, invited by email. They can file bugs and (on an MCP plan) open the editor — they never get a dashboard account. Owners sign in as themselves. See Team and Your access.

Plans

PlanPriceHighlights
Free$01 project, watermark on reports, screenshot + AI title
Studio$29/moInvite Team seats, video recording, console/network capture, reproduction steps, widget routing, AI duplicate detection
Agency$79/moUnlimited projects, no watermark, session replay, AI triage rules, MCP agent

New accounts get a 14-day trial with Studio-level features. See Plans & Limits for the full feature matrix.

Credentials

Easily confused — full matrix in API Keys & Tokens:

  • Project API key — one per Project; Web / WordPress / SDK. Installation tab.
  • Chrome extension — owners Sign in as owner; invited people Authenticate Chrome from the access email.
  • Editor / MCP — project MCP tab for mcp.json; owners Sign in, teammates Authenticate from the access email. CI tokens on Account → API tokens.

On this page