Until the client allows the round’s domains
Mobile, tablet or desktop, on every comment
A revoked token disconnects on its own
In the popup, the bar and the guide
Connect, allow the sites, pick an element and send a comment. The panel under the window shows what the CRM receives. Everything runs in this page and nothing is sent anywhere.
Made-up data. Nothing on this page reaches a CRM.
The task each comment becomes, in the project. Pick one in the list to see its fields.
What the extension would send, as you use it.
Nothing sent yet.
Clients do not need an account for this. The team issues a token in the CRM for each round of feedback, tied to one project, one contact and the domains under review.
A round in the CRM
The team picks the project, the contact and the domains (production, staging, dev or local), the day comments close and the day access ends.
Pasted once
The client pastes the token into the extension. The CRM keeps only its hash, and checks it on every call.
Allowed on those sites
Chrome asks the client to allow the extension. The comment bar then runs on the round’s domains, and nowhere else.
Revoked in a click
A revoked or expired token disconnects the extension within a minute. A closed round stays readable, and the next one copies its project, contact and domains.
What the client does takes seconds. What the team receives is everything needed to reproduce it.
Comment mode highlights whatever is under the pointer and a click selects it. The site’s own links stay quiet until the comment is sent.
Each comment carries a capture of the screen with a marker and a crop of the element, plus up to five files of the client’s own.
Every comment is a task in the CRM project, named after the round, tagged with it and the screen size, and assigned to whoever the round says.
The team’s replies show in the extension. The client marks a comment solved or reopens it, and the task moves with it.
The list the Web Store review read, with the reason for each. At install the extension runs on no website at all.
| Permission | Why it is there |
|---|---|
storage | Keeps the token, the round’s details and the chosen language on the device. Disconnecting removes them. |
scripting | Adds the comment bar to the round’s domains, and to no other site. |
alarms | Checks the token once a minute, so a revoked or expired round disconnects on its own. |
activeTab | When the popup is opened, tells it which site the tab is on, so it can say whether comments are active there. |
optional_host_permissions | Asked for when the client connects, in Chrome’s own dialog. The bar runs only on the round’s domains; Chrome words the access more widely because a screenshot of the visible tab needs it. |
The extension is the part the client sees. The rounds, the rules and the tasks live in the CRM.
What it reads, what it keeps, where and for how long: the policy its store listing points to.
The module issues a token per round, keeps it hashed and checks every write against the round’s domains. Revoking or regenerating a token is one click.
Comments are ordinary tasks of the project, visible to the client, with the captures attached, so the team works them on the same board as everything else.
In the CRM’s client area, the contact sees every round, every comment and its conversation, and can read the token again if their permissions allow it.
Forty comments every ten minutes per token, files checked by type and size, and answers only to the extension, not to the open web.
Time on CRM tasks from the toolbar: search by client or project, press play, and the timer that runs is the CRM’s own.
Manifest V3 extensions for the Chrome Web Store, built together with the API they talk to. People sign in with an account they already have, and what they do in the browser lands in your CRM or your app.