You're connected
Disconnected, you never see the launcher anywhere. The extension fails closed: if it can’t confirm you’re authorized, it shows nothing rather than guessing.
The uMarker extension is what your team gives named testers so they can file reports from inside the browser — including on staging, and on sites whose HTML you can’t add a snippet to, as long as your team has registered that site’s domain on a project. It puts a feedback launcher on the pages you’re allowed to review: click it, point at what’s wrong, send. Nothing appears on sites you aren’t authorized for, and nothing is sent until you press submit.
Two things:
mdc_…, issued by your admin. It identifies you
as a widget user and links the extension to your team’s uMarker account. You normally paste it
once, but the code stays valid after that: it connects you again after a reinstall, and on a second
machine, without anyone issuing you a new one. So treat it like a password. An admin ends it by
issuing you a replacement, which signs out every session the old code opened.You don’t need a server address: the store build talks to uMarker’s servers directly, and has no field to change that.
Open the uMarker page on the Chrome Web Store in Chrome, Edge, Brave, Opera or Vivaldi.
Click Add to Chrome (or your browser’s equivalent — Edge, for example, asks you once to allow extensions from other stores) and accept the permissions. Updates then arrive from the store on their own.
Pin uMarker so its mark stays in your toolbar: click the puzzle-piece icon and pin it. You’ll click that mark to connect and to report.
Click the uMarker icon in your toolbar. Before you connect, it shows Offline.
Read the disclosure. It says plainly what a report sends: a screenshot, your marks and comments, the page address, your name, and your browser, system, language and screen size — and that your team sets each project to Normal (only that) or Technical, which adds the page’s console messages, errors with their stack traces, every request the page made, page-speed figures and, in Chrome, the browser’s own warnings. Never cookies, headers, what was sent or what you typed. Tick I understand and agree. You can’t connect without it.
Paste your connection code (mdc_…) into the Connection code field and click Connect.
The popup switches to your connected view with your name, your team’s account name, and the line Connected — the widget shows on sites you’re authorized for.
Access control is the whole point of the extension. The launcher appears only when all of these are true at once:
You're connected
Disconnected, you never see the launcher anywhere. The extension fails closed: if it can’t confirm you’re authorized, it shows nothing rather than guessing.
This site belongs to a project you're on
A page’s host is matched against the projects’ allowed domains. You see the launcher only if you’re assigned to the project that owns that host — and your code assigns you to the project it was issued from. The Extension tab adds you to the project it’s on, and nothing else in the dashboard adds an existing tester to a second one.
The project is published, with the extension on
An admin can put a project back to Draft, or switch the extension surface off for it specifically, and connected testers then see nothing there.
One more thing takes the launcher away without anyone changing a setting. If your team’s plan is downgraded past what it covers, uMarker pauses the excess — a project, a registered domain, or a tester’s own seat — and any one of those being paused hides the launcher exactly as a Draft project does. Nothing is deleted, and an upgrade brings it all back as it was.
On a site you’re not authorized for, the launcher simply doesn’t appear. That’s expected, not a bug. Your browser doesn’t even ask uMarker about it: the extension keeps the list of hosts you’re registered for and checks locally first, so the origin of every page you open is never sent anywhere.
And because uMarker re-checks your authorization on the server every time you submit, a report can’t slip through from a project you’ve lost access to. Once your access ends, the launcher is gone on the next page load and any submission is refused.
What a report carries is decided by your team, per project, not by you: they set each project to Normal or Technical under Widget → Setup, in the card What a report captures. The popup shows the mode of the project the current tab belongs to — This project captures: Normal or Technical — with a line on what that sends. There is no switch in the extension.
net::ERR_…), and while the capture tool is open Chrome shows a “started debugging
this browser” bar — that’s how those warnings are read, and it goes away when you send or cancel.Neither mode ever sends cookies, headers, what a request sent or received, or what you typed. See What gets captured for the full list.
The extension runs the same widget as the website snippet, so on the sites you’re authorized for you also see your team’s surveys, announcements and What’s new feed, with the same targeting the snippet uses. A survey you answer from the extension is filed under your name rather than as an anonymous visitor. If a page also has the snippet installed, you see one widget — the extension’s.
“Could not connect. Check the code your admin sent you.” The code wasn’t accepted. Confirm you pasted it exactly (codes are case-sensitive). If it’s right, the usual reason is that a newer code has been issued for you — issuing one retires the old one — so ask your admin for the current one.
“Couldn’t reach uMarker.” This one is about the network, not your code. Check your
connection and that nothing is blocking api.umarker.com, then try again.
“This uMarker account is suspended.” A new code won’t help. Ask your admin.
You connected, but no launcher appears on a site. Most likely the site’s host isn’t on any project you’re assigned to, or the project is in Draft, or its extension surface is off — or a plan downgrade has paused the project, the domain, or your own tester seat. Try a site you know you’re assigned to; if it’s still missing, ask your admin to confirm.
You were connected and got dropped back to Offline. Your session ended. Sessions are forgotten after a long stretch with no use, and issuing you a new code ends every session the old one opened. Paste your code again; if that’s refused too, ask your admin for the current code.
Open the popup and click Disconnect. Every page you open from then on comes up without the launcher, until you connect again. A tab you already had open keeps the launcher it drew when it loaded — reload it, or just leave it alone: anything sent from a disconnected session is refused, and the tool says so. Disconnect on any shared or public computer when you’re done.