What is Team Review in OverlayQA?

Team Review is a dashboard-native way to capture UI bugs on any public URL without installing a browser extension. A reviewer opens the page inside OverlayQA, pins issues on elements or regions, and each pin becomes a tracked issue with a screenshot and element context that exports to Jira, Linear, Notion, Asana, or Trello.

Do I need to install a browser extension for Team Review?

No. Team Review runs in the OverlayQA dashboard, so reviewers open a URL and start pinning issues with no install step. The OverlayQA browser extension is still available and is required for localhost, staging, and login-gated pages that a hosted proxy cannot reach.

What is the difference between live-proxy mode and snapshot mode?

Live-proxy mode loads the live page inside OverlayQA so reviewers see the current site in session. Snapshot mode reviews a frozen capture of the page instead. OverlayQA switches SPA builder domains like Webflow, Framer, and figma.site to snapshot automatically because their heavy client-side rendering does not proxy reliably.

Can my team review Webflow, Framer, or Figma Sites pages?

Yes. Pages on Webflow, Framer, and figma.site are reviewed in snapshot mode, which OverlayQA selects automatically for those domains. Reviewers pin elements and regions on the snapshot the same way they would on any other page, and each pin becomes a tracked issue.

When should I use Team Review versus the browser extension?

Use Team Review for public URLs where you want reviewers to start without installing anything. Use the OverlayQA browser extension for localhost, staging, and login-gated pages, since those require running in your own browser session. Both paths share the same projects and issue tracker.

Workflow Guide

Team Review Workflow

Team Review is OverlayQA's dashboard-native way to capture UI bugs on any public URL without installing a browser extension. A reviewer opens the page inside OverlayQA in live-proxy or snapshot mode, pins issues on elements or regions, and each pin becomes a tracked issue that exports to Jira, Linear, Notion, Asana, or Trello.

Last updated: July 2026

What is Team Review?

Team Review lets your whole team capture visual bugs on a live website with nothing to install. Designers, PMs, and QA sign in to the OverlayQA dashboard, open the URL, and pin issues directly on the page. Each pin is captured with a screenshot and the element's CSS selector, so feedback lands with the context developers need to reproduce and fix it. To collect feedback from clients who don't have OverlayQA accounts, use a client review link instead.

Team Review vs. the browser extension

Dimension	Team Review	Browser Extension
Install step	None — runs in the dashboard	Install the OverlayQA extension in Chrome
Best for	Public URLs and client/stakeholder reviews	Localhost, staging, and login-gated pages
How the page loads	Live-proxy in session, or snapshot for builder sites	Runs in your own browser session on the page
Who reviews	Your team, signed in to the dashboard — nothing to install	Team members with the extension installed
Capture	Element and region pins with screenshot + selector	Element capture with screenshot + selector
Export	Jira, Linear, Notion, Asana, Trello	Jira, Linear, Notion, Asana, Trello

Common team review challenges

Extension install friction — Cross-functional reviewers will not install a browser extension just to leave a round of feedback, so reviews stall before a single issue is captured.
Feedback without context — Bugs arrive over Slack and email as "the header looks off on mobile" with no element, page, or screenshot attached.
Builder sites break capture — Webflow, Framer, and Figma Sites pages use heavy client-side rendering that ordinary screenshot tools capture blank or half-loaded.
Manual triage — Scattered feedback has to be copied, screenshotted, and re-entered as tickets by hand before developers can act.
No shared canvas — Reviewers and the team look at different screenshots, so nobody is sure which pin maps to which issue.

How Team Review works

Live-proxy mode loads the live page inside OverlayQA so reviewers work against the current site in session. For SPA builder domains — Webflow, Framer, and figma.site — OverlayQA switches to a frozen snapshot automatically, because their heavy client-side rendering does not proxy reliably. Either way, reviewers pin issues the same way and every pin is captured with full context.

Each pin becomes a tracked issue in a drawer that stays synced with the on-page canvas: selecting an issue highlights its pin, and every reviewer sees the same board. When the review is done, issues export to your tracker with screenshots and element details attached, so there is no copy-paste triage.

Team Review workflow steps

Open the URL in OverlayQA — From the dashboard, enter any public URL. It opens inside OverlayQA with no extension to install.
Choose live-proxy or snapshot — Review the live page in session with live-proxy mode. Webflow, Framer, and Figma Sites pages switch to a frozen snapshot automatically.
Pin the issues — Click an element or drag a region to drop a pin. Each pin captures a screenshot, the element selector, and the page context.
Work the issue drawer — Every pin becomes a tracked issue in the synced drawer. Set severity, add comments, and triage without leaving the page.
Export to your tracker — Send issues to Jira, Linear, Notion, Asana, or Trello with screenshots and element context attached.

Frequently asked questions about Team Review

What is Team Review in OverlayQA?: Team Review is a dashboard-native way to capture UI bugs on any public URL without installing a browser extension. A reviewer opens the page inside OverlayQA, pins issues on elements or regions, and each pin becomes a tracked issue with a screenshot and element context that exports to Jira, Linear, Notion, Asana, or Trello.
Do I need to install a browser extension for Team Review?: No. Team Review runs in the OverlayQA dashboard, so reviewers open a URL and start pinning issues with no install step. The OverlayQA browser extension is still available and is required for localhost, staging, and login-gated pages that a hosted proxy cannot reach.
What is the difference between live-proxy mode and snapshot mode?: Live-proxy mode loads the live page inside OverlayQA so reviewers see the current site in session. Snapshot mode reviews a frozen capture of the page instead. OverlayQA switches SPA builder domains like Webflow, Framer, and figma.site to snapshot automatically because their heavy client-side rendering does not proxy reliably.
Can my team review Webflow, Framer, or Figma Sites pages?: Yes. Pages on Webflow, Framer, and figma.site are reviewed in snapshot mode, which OverlayQA selects automatically for those domains. Reviewers pin elements and regions on the snapshot the same way they would on any other page, and each pin becomes a tracked issue.
When should I use Team Review versus the browser extension?: Use Team Review for public URLs where you want reviewers to start without installing anything. Use the OverlayQA browser extension for localhost, staging, and login-gated pages, since those require running in your own browser session. Both paths share the same projects and issue tracker.