Chrome Extension

Overview

The SeggWat Chrome extension lets you submit feedback with annotated screenshots directly from your browser, without leaving the page you're testing. It's built for product teams who triage across staging environments, customer dashboards, internal tools, and competitor sites — anywhere you can load a URL.

• One-click submission: Click the toolbar icon to send feedback for the current page
• Screenshot annotation: Capture and mark up screenshots with arrows, rectangles, text, and blackout tools
• Side panel mode: Keep the form pinned while you browse — perfect for QA sessions
• Right-click menu: Send feedback via the context menu without reaching for the toolbar
• Per-domain memory: Automatically remembers which project you last used on each domain

Installation

Requires Chrome 114 or later. Also works in Microsoft Edge, Brave, Arc, Vivaldi, and any Chromium-based browser that supports Manifest V3.

Configuration

The extension authenticates with your SeggWat account using an API key. You only need to do this once per browser profile.

1. Click the extension icon in the toolbar, then click the settings (gear) icon
2. Paste your SeggWat API key (find or create one under Settings → API Tokens in the SeggWat dashboard)
3. Click Test Connection to verify the key and see what it can do
4. Click Save Settings

API key format

SeggWat API keys are 47 characters long and always start with oat_:

oat_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Keys are stored in chrome.storage on your device only — they are never synced to Google's account sync and never shared with third parties.

Test Connection shows your token's scope

After clicking Test Connection, the extension renders a row of chips below the status message describing what the key is allowed to do. This is driven by the scopes the key was minted with — see Tester preset for the recommended scope set for external testers.

Chip	Meaning
Submit feedback	Key has the feedback:write scope — extension submission will work
List projects	Key has the project:list scope — the project picker will be populated
Read feedback	Key has feedback:read (not needed by the extension, but useful for shared keys)
Full org access	Legacy key minted before scoped tokens existed; has every permission in the org
Hint line	Spells out non-obvious consequences — e.g. project restriction, missing scope, or "this is a legacy unrestricted key"

If a tester reports the extension isn't working, ask them to open the options page and click Test Connection — the chips and hint line make it obvious whether the problem is the key (wrong scope, expired, project-restricted to a different project) or the network.

Tester preset

When you need to give the extension to a beta tester, contractor, or external QA partner, don't mint them a full-access API key. Use the Tester preset when creating an API key in Settings → API Tokens in the dashboard.

What the preset grants

The Tester preset is the minimum scope set required for the extension to function:

Scope	Why the extension needs it
project:list	Populate the project picker in the popup / side panel
feedback:write	Submit new feedback (with or without screenshot)

What the preset does not grant

A tester preset key cannot:

• Read existing feedback or ratings (feedback:read is not granted)
• Submit or vote on ideas (idea:write is not granted)
• Access any project other than the one the key is restricted to
• Modify feedback status, type, or message
• Delete anything
• Outlive its expiry — the preset defaults to 90 days

How to create one

1. Open the dashboard and go to Settings → API Tokens
2. Click Create API Key
3. Pick Tester preset in the create-key form
4. Choose the single project the key should be restricted to
5. Optionally adjust the expiry (default 90 days)
6. Add a label like "jane-doe@vendor.com — Acme staging" so you can audit later
7. Copy the key — it is shown once — and send it to the tester through a private channel

When the tester pastes the key into the extension and clicks Test Connection, they'll see exactly two scope chips (Submit feedback, List projects) and a hint line telling them the key is restricted to one project. There's no ambiguity about what the key can or can't do.

When to use a full-access key instead

The tester preset is intended for external people who only need to submit feedback. If you're an internal team member using the extension on your own org's projects, a full-access key (or your existing personal key) is fine — you already have read/write access through the dashboard anyway.

Sending feedback

There are three ways to open the feedback form:

• Toolbar icon: Click the SeggWat icon in your browser toolbar
• Right-click menu: Right-click anywhere on a page → Send feedback to SeggWat
• Side panel: Click the side panel icon next to the address bar (Chrome 114+)

In all three modes, the same form opens:

1. Pick a project from the dropdown (it remembers your last choice for the current domain)
2. Type your feedback (3–1000 characters)
3. Optionally attach a screenshot (see below)
4. Click Send Feedback

The current page URL and title are attached automatically — no manual copy-paste required.

Screenshot annotation

When you click Add Screenshot, the extension captures the visible viewport of the current tab and opens the annotation editor in a new tab.

Tools

Tool	Purpose
Select	Click an annotation to select and move it
Arrow	Draw arrows to point at elements
Rectangle	Highlight areas with rectangles
Pen	Freehand drawing
Text	Add multi-line text annotations
Blackout	Redact sensitive information
Pan	Navigate around zoomed screenshots

Keyboard shortcuts

Shortcut	Action
Space (hold)	Temporary pan mode
+ / =	Zoom in
-	Zoom out
0	Fit to screen
Ctrl+Z	Undo
Ctrl+Shift+Z / Ctrl+Y	Redo
Delete / Backspace	Delete selected annotation
?	Show / hide keyboard shortcuts
Esc	Close editor

When you're done, click Attach Screenshot to return to the feedback form with the annotated image attached, then submit.

Permissions

The extension requests only the minimum permissions needed:

Permission	Why
activeTab	Capture screenshots of the current tab
storage	Store your API key and per-domain project preferences locally
tabs	Read the current page URL and title
contextMenus	Add the right-click Send feedback menu item
sidePanel	Enable the always-visible side panel mode
Host: https://seggwat.com/*	Submit feedback to the SeggWat API

There are no broad host permissions, no analytics SDKs, no third-party trackers, and no requests to anywhere except seggwat.com.

Browser support

Chrome	114+
Edge	114+
Brave / Arc / Vivaldi	Any Chromium build supporting Manifest V3
Firefox	Not yet — on the roadmap once side_panel MV3 stabilizes
Safari	Not supported (use the iOS app for Apple devices)

Troubleshooting

"API key not configured"

Open extension settings (gear icon in the popup) and paste your API key. Make sure it starts with oat_ and is exactly 47 characters.

"Failed to capture screenshot"

Screenshots only work on regular web pages. They cannot capture:

• chrome:// internal pages (settings, extensions, etc.)
• The Chrome Web Store
• New Tab page

If you're on a normal site and capture still fails, refresh the page and try again.

Screenshots are too large

Captured screenshots are compressed to JPEG at 80% quality. The maximum upload size is 10 MB. For long pages, scroll to the area you care about before capturing — the visible viewport is what gets captured.

Project list is empty

Click Test Connection in settings and look at the scope chips:

• No "List projects" chip: the key is missing the project:list scope. Re-mint it with the Tester preset or a full-access key.
• "List projects" chip present, but no projects shown: the key is project-restricted to a project that has been deleted, or the org has no projects yet. Create one in the SeggWat dashboard and click Test Connection again.

Feedback submission fails with 401 / 403

Open settings, click Test Connection, and check the scope chips:

• No "Submit feedback" chip: the key lacks feedback:write — typical for a read-only key minted for analytics. Use the Tester preset instead.
• The key is project-restricted: the project you selected in the popup may not be in the allow-list. The "List projects" call will only return projects the key is allowed to operate on, so picking a project from the dropdown should normally succeed — but if the project was removed from the allow-list after the projects were cached, refresh the project list by clicking Test Connection again.