Glossary
One sentence per term, linked to the page that covers it properly. Machine data (field
names, keys, status values) is in monospace and is exact.
Account: The tenant boundary, one customer organisation and everything under it. Every
tenant-owned record carries an account_id. Most models filter on it automatically through a
global scope; the rest — the team roster, extension testers, transactions, the audit log — are
filtered by each endpoint instead. See Account isolation.
AI assist: Optional model-written help during triage, with a drafted title and summary, suggested priority and labels, possible duplicates. Every output is advisory until a person accepts it. It stays off until three separate switches say yes: your account turns AI on (off by default), your plan includes it (Professional and above), and a model provider is configured — either uMarker’s own chain (Groq and Google Gemini today) or your own key. See AI assist.
Announcement: A message published to a project and shown to that site’s visitors in the widget. Available from Starter. See Announcements & changelog.
API key: A REST credential shown once as md_live_… and stored only as a hash; it can be
account-wide or scoped to one project. Minting one is a paid capability. See
API keys.
Assignment: The teammate a report belongs to, so one person owns it through triage. See Labels, priority & assignment.
Breadcrumb: One entry in the time-stamped trail of the reporter’s last actions (clicks, inputs, route changes), captured alongside the console on Technical-mode reports only. Field identifiers only; never what was typed. See Technical context.
Bulk action: One operation applied to many selected reports at once, setting status, labels or assignment. See Saved views & bulk actions.
Capture mode: A per-project setting under Widget → Setup that decides what a report carries, on the snippet and the extension alike. Normal (what new projects start on): the screenshot, marks, notes, page and device. Technical: all of that plus console, network requests, errors, performance, breadcrumbs and environment. A report keeps the mode it was filed in. See Technical context.
Capability: A feature a plan either includes or does not, among them surveys, custom roles, API access and multi-space. Different axis from a permission: a permission says what a person may do, a capability says what the account has. See Roles & access.
Changelog: The hosted public page listing what you shipped; the same entries appear inside the widget as What’s new. Available from Starter. See Announcements & changelog.
Channel: A shared destination uMarker delivers events to, one of Slack, Telegram, Microsoft Teams, or a signed outbound webhook. Email is not a channel: it is a per-person preference. See Channels.
Close the loop: Telling the person who reported something that it was fixed, through a changelog entry — plus an optional email when the reporter was a signed-in extension tester. Snippet reports are anonymous, so there is no verified address to write to and no email option appears. See Close the loop.
Connection code: The mdc_… credential an extension tester exchanges for a session. uMarker
shows it once when you create it and stores only a hash; it stays usable until you rotate or
revoke it, and it is the only thing the extension asks for. Treat it like a password — anyone
holding it can connect as that tester. See Invitations & onboarding.
Console logs: The browser console output captured with a Technical-mode report and shown in monospace on the report page. See What gets captured.
CES: Customer Effort Score, an agreement-scale survey; results show the average and the distribution. See Surveys.
CSAT: Customer Satisfaction, a 1–5 satisfaction scale; results show the average and the distribution. Stars and emoji are question types inside a form survey, not the CSAT type. See Surveys.
Custom field: An extra field you define for reports in a space, so triage can record something uMarker does not ship. A paid capability, from Professional. See Labels, priority & assignment.
Custom role: A role you write yourself from the permission catalogue, when neither built-in seat says what you mean. A paid capability. See Roles & access.
Digest: The daily email option that groups a person’s notifications into one message instead of sending each immediately. The hour is uMarker’s, not yours — 08:00, delivered in each person’s own timezone. It is email, so it needs Starter or above. See Email & notifications.
Distribution route: The per-project rule that sends chosen events from one connected integration to one destination. The credential is entered once per account; the route decides which project uses it and for what. See Issue trackers.
Domain: A site host mapped to a project, so uMarker knows which project applies on a given page. Domains are the plan’s headline pricing unit; projects, seats, spaces, testers, integrations and storage are counted too. See Install the widget.
Duplicate: A report linked to another as the same issue, from the report page; the link is visible from both. See The report page.
Element inspection: The DevTools-style capture mode. Hovering highlights the deepest element with its box model, arrow keys walk up the tree, and the comment is anchored to that element and its CSS selector. See Capture overview.
Extension: uMarker’s Chrome extension, a capture surface for named testers, who sign in with a connection code. Published on the Chrome Web Store; Firefox and Safari not yet. See Install the extension.
Extension tester: A person you authorise to capture through the extension, assigned to specific projects and revocable at any time. They never sign into the dashboard. See Invitations & onboarding.
Feedback / report: The core record, holding a screenshot, the reporter’s notes on it, the element each note points at, page and device context and — in Technical capture mode — console logs, network requests, errors and breadcrumbs, and moving through the status lifecycle. See The inbox.
Frequency cap: A targeting control limiting how often the widget re-appears to the same visitor, tracked in that visitor’s own browser. See Targeting rules.
Insights: The read-only rollup across reports and surveys for a space or a project. Available from Professional. See Insights.
Invitation: A single-use, 7-day email link carrying a 48-character random token (stored only as a hash) that lets someone join your account in a role and set their own password. Resending rotates the token; revoking kills it. See Invitations & onboarding.
Issue tracker: A connected GitHub, Linear or Jira destination a report can be pushed to as an issue, with the link stored on the report. See Issue trackers.
Label: A tag applied to reports and survey responses from the same taxonomy, defined per space. Four starter labels (Bug, Idea, Question, Improvement) are seeded in Arabic and English into every new account’s first space; a space you create later starts with none. See Labels, priority & assignment.
Margin bar: The orange strip drawn around an inspected element’s margin; it is clickable, so a reporter can comment on the empty space itself rather than the nearest thing in it. See Capture overview.
MCP server: The interface that lets a coding agent read your inbox and act on reports. It authenticates with an API key, so it needs a paid plan. See MCP server.
Mute: A personal, per-project silence. It stops notifications reaching you and changes nothing about what your team receives. See Email & notifications.
NPS: Net Promoter Score, a 0–10 survey scored as the percentage of promoters (9–10) minus detractors (0–6). See Surveys.
Pin: One numbered note on a capture. Each pin carries its own comment, its own discussion thread on the report page, and its own resolve toggle. See The report page.
Priority: The urgency set on a report during triage. On the board it sorts after the manual drag order, so it arranges a column nobody has dragged and moves nothing in one that has been reordered by hand; in the list it is an opt-in sort, not the default. See Labels, priority & assignment.
Project: What a widget, its domains, its reports, surveys and settings attach to. Belongs to one account and one space. See Core concepts.
Public key: The non-secret key in a project’s snippet that tells v1.js which project to load
its configuration for. See Install the widget.
Redaction: Masking that happens on the reporter’s own device, before the screenshot is taken. Query-string values whose names look like a secret are blanked on every project; masking typed field values and any region you mark with a CSS selector is a per-project switch, off until you turn it on. See Redaction.
Role: What a person may do. Two built-in seats (Admin and Member) plus any custom role you write (Professional and above). See Roles & access.
Saved view: A named inbox filter, shared with the space. Saving one is available from Starter. See Saved views & bulk actions.
Seat: One dashboard person on your plan. Seats are bundled, not priced per head, and a pending invitation already occupies one. See Invitations & onboarding.
Sensitive selector: A CSS selector you mark so its element is blurred before capture, whatever it contains. It is read only while that project’s redaction switch is on, so the list does nothing on its own. See Redaction.
Snippet: The <script> tag you paste on your site. It loads v1.js from the uMarker API host
and needs nothing installed by the visitor. See Install the widget.
Space: The wrapper projects live in (Account → Space → Project). Every account starts with
one called General; any space can be deleted, including that one, and deleting it deletes the
projects inside it — uMarker mints General again the next time you sign in with none left. The
spaces overview is the first screen after sign-in. See Spaces.
Status: A report’s position in its lifecycle. One of new, in_progress, waiting,
resolved or archived. See Status lifecycle.
Survey: A microsurvey (NPS, CSAT, CES, or a short form with stars, emoji and choice questions) rendered by the widget on a project. Available from Starter. See Surveys.
Targeting rule: A per-project condition (URL, device, audience, frequency) deciding whether the widget appears. The snippet applies it to everything; the extension applies it to surveys, announcements and What’s new, while its feedback button always shows for a tester. Available from Professional. See Targeting rules.
Two-factor authentication: A second sign-in step, by authenticator app or emailed code, with recovery codes. Available from Starter. See Your account & security.
Webhook: A signed outbound HTTP callback uMarker POSTs on subscribed events, carrying an
X-uMarker-Signature header the receiver verifies. See Outbound webhooks.
What’s new: The in-widget list of recent changelog entries shown to a project’s visitors. Available from Starter. See Announcements & changelog.
Widget: uMarker’s in-page capture UI, isolated in a shadow DOM, so your page’s CSS cannot reach into it and its own styles cannot leak out. The one deliberate exception is the capture tool, which hides the page cursor while it is open and restores it when you finish. Delivered by the snippet or by the extension. See Capture overview.