Team Review

Last updated: November 6, 2026

Team Review lets you capture and review issues on any live URL straight from the OverlayQA dashboard. Nothing to install: the page loads inside a review canvas where you place pins, write issues, and track findings with your team. It's the fastest way to review a publicly reachable site. For localhost, staging behind a VPN, or login-gated pages, use the Chrome extension instead.

Start a Team Review

Team Review starts from a project in the dashboard:

The review opens straight away on the page the project already knows: the page of its newest issue, else its scan URL, else the URL in its Project Settings. It asks for a Page URL only when the project has none on file, or when that URL is a local or private address the server cannot reach. To start somewhere else, use Capture a different page.

Tip: Localhost, private-network, and file:// URLs can't be reached by the review proxy. Open those pages with the extension, which captures them in place. From its Issues tab, Open in team review takes a snapshot of the page you are on, including localhost, staging, and pages behind a login, and opens it as a team review.

Live and Snapshot Modes

Every review runs in one of two modes, shown in the header:

Almost every site reviews fine in live mode, including pages built in Webflow and Framer. Two hosts are the exception: figma.site and notion.site pages start in snapshot mode automatically, because their client bundles don't render inside the review proxy. Everything else starts live, and you can switch modes yourself at any time: click the mode indicator in the header and choose Switch to Snapshot or Switch to Live.

Note: Live mode opens pages logged out. If a page needs sign-in and never finishes rendering, a hint appears explaining why, with a shortcut to open that page with the extension instead.

Capture Issues

Capture starts with the review. Use Create on the capture toolbar at the bottom of the page (or press C) to pick an element, and Screenshot (or S) to drag a region. Pause capture makes the page clickable again without ending the session, and Done capturing ends it. OverlayQA captures a screenshot automatically for both pin types.

AI Suggestions

AI drafting is opt-in. Write at least 10 characters and click Rewrite & fill in details, and the AI suggests a title, type, severity, and expanded description. Click Apply All to accept the suggestions, or Dismiss to keep your own wording. The one exception is your first capture during onboarding, where a description of 10 characters or more starts a draft on its own.

Preview Breakpoints

Use the width dropdown in the header to view the page at a preset breakpoint: Responsive, Desktop 1440, Laptop 1024, Tablet 768, Mobile L 414, Mobile 390, or Mobile S 360.

Issues remember the breakpoint they were captured at. The expanded issue detail shows a "Captured at" line (for example, "Mobile 390"), so developers know exactly which viewport reproduced the bug.

The Issue Drawer

Captured issues appear in the drawer on the right, grouped by page, with the current page expanded. The drawer stays in sync with the canvas: click a pin to jump to its row, and a just-created issue floats to the top of its group.

Expanding an issue shows its screenshot, the captured breakpoint, and a comment thread where teammates can discuss the issue with @mentions.

Select issues with the checkboxes to open the Actions menu: export to Jira, Linear, Notion, Asana, Trello, ClickUp, GitHub Issues, Basecamp, or monday.com, share issues via a public link, set status, type, or severity in bulk, or delete.

Measure Spacing and Record the Bug

The ruler on the capture toolbar turns spacing inspection on or off. While it is on, hover an element to see its padding and the gaps to the nearest visible elements, in pixels; hover a container to see the gaps between its children. The measurements are temporary and are not saved with the issue.

Record (Chrome and Edge on a computer) records the page for up to 30 seconds and 9 MB, with no sound. Choose Share when the browser asks, drag to pick an area or keep the whole page, and start recording. Stop recording opens the issue editor with the clip listed as a file.

Where Issues Go

Team Review issues save into the same project issue list as extension captures and get the same sequential issue IDs (like OQ-127), so integrations, exports, and reporting treat them like any other issue. Open the project in the dashboard to see review captures alongside extension captures.

Team Review vs. Client Links

Team Review is the signed-in version of the review canvas, built for your own team. To collect feedback from clients or stakeholders who don't have OverlayQA accounts, create a client link instead. Guests can pin comments that become linked issues automatically, record a short clip, and reply in a pin's thread, while workflows, exports, mode switching, and spacing inspection are reserved for signed-in team members. Guests get width previews only on links whose owner allows responsive views.

Workflows in Team Review

Five workflows run inside the review canvas with no extension installed: Visual Comparison, which overlays a design on the page so you can align it with the live layout; AI Visual Comparison, which compares the page against a Figma frame or an uploaded design image, then lists the visual differences; the Accessibility Audit, which finds WCAG 2.2 AA issues on the page you are reviewing; Auto Review, which scans the page for UI-quality issues like design inconsistencies, missing interactive states, form problems, and leftover placeholder content; and Design Tokens, which checks the page's CSS against a Figma frame or a design tokens JSON you choose and flags hard-coded colors, spacing, type, and radius that should be tokens.

When You Still Need the Extension

See Getting Started to install the extension, or Creating an Issue for the extension capture flow.