Teammates
People who work in the dashboard: they open the inbox, triage reports, comment, and configure projects. Each one occupies a seat on your plan, and you bring them in by email invitation: they set their own password.
uMarker onboards two different kinds of people, and the two never mix.
Teammates
People who work in the dashboard: they open the inbox, triage reports, comment, and configure projects. Each one occupies a seat on your plan, and you bring them in by email invitation: they set their own password.
Extension testers
Testers, QA and clients who capture through the Chrome extension. They never sign into the dashboard. You issue each one a connection code, assign them to projects, and revoke or delete them at any time.
A person can be both, but the two credentials are separate records. Creating one never creates the other.
Team management lives at Manage team → Members, opened from the profile menu. It is account-level: everyone you invite gets one role for the whole account, and there is no separate per-space members page. That account role is a baseline rather than the last word — a project can give someone a different role inside itself, which then decides for and against within that project. See Roles & access.
Open Manage team → Members. You see active members, pending invitations, and anyone the account has suspended, each on its own tab.
Enter the email and choose what they join as: the Admin seat, the Member seat, or one of the custom roles you have written (writing a new custom role needs Professional or above; roles you already have stay editable and assignable on any plan).
Send. uMarker emails a unique, single-use link that expires in 7 days. Its credential is a 48-character random token stored only as a hash, so an edited or guessed link matches nothing. The message names your account, the role, and who invited them. The link is also shown in the dashboard so you can pass it along any other way.
Two things can refuse the invitation before it goes out:
They open the link, which confirms the account name they were invited to.
They enter their name and a password twice. The policy is at least 8 characters, containing letters and numbers.
On submit uMarker claims the invitation atomically, creates the user in the invited role, and marks the address verified: accepting the link already proved they control it. They land signed in.
Used, expired, revoked or tampered links are all refused the same way and send the person to sign-in with a note to ask for a fresh invitation. The link also opens while someone is signed into another account: nothing is dropped when it opens, and accepting it swaps that browser over to the new user. The invitation is claimed by the token in the URL and never by whoever happens to be signed in, so it cannot land on the wrong account.
From the same tab:
Acceptance attempts carry their own per-IP limit, so an invitation link cannot be brute-forced. Sending and resending have no separate limit of their own — they sit under the dashboard-wide ceiling of 300 requests a minute. All four events (sent, accepted, resent, revoked) are written to the audit trail.
Three different things, and the difference matters.
| Action | What it does | Reversible |
|---|---|---|
| Suspend | Freezes the person account-wide: sign-in is refused and their live sessions are dropped on the spot. The record, their comments and their history all stay. | Yes, while a seat is free |
| Reactivate | Lifts the suspension. Nothing about them was changed while they were suspended, so the role, the project access and the history all come back untouched. | Not applicable |
| Remove | Deletes the membership, drops their sessions, and revokes every API key they minted. | No |
A suspended member does not occupy a seat, so reactivating one takes a seat back. If the account is full, uMarker says so and names the two ways to make room (withdraw a pending invitation, or remove a member) rather than only telling you to upgrade.
Removing someone tells you how many API keys were revoked with them, because a revoked key is an integration that stops working tonight, and an admin who was not told will spend that outage looking anywhere but here.
Extension testers are managed inside the project: open the project, then Widget → Extension. The list is the people allowed to capture on that project.
Choose Add tester and give a name, an email, and the projects they may capture on.
Save. uMarker shows a connection code (mdc_…) exactly once, the way an API key is shown once. Copy it and send it to the tester.
The tester pastes the code into the extension. That exchanges it for a session. The code is the only thing they have to set up: there is no account for them to create, and the extension already points at uMarker.
Extension testers are capped per plan: 2 on Free, 10 on Starter, 50 on Professional, 200 on Agency.
A teammate recovers their own access from the sign-in page without involving you. The response is deliberately identical whether or not the address is registered, so the form can never be used to discover who has an account. Completing a reset invalidates that person’s other sessions and any other outstanding reset link, and reset emails are rate-limited per address.
If a tester loses their connection code, issue a new one. The old code stops resolving the moment the new one is minted, and their live extension sessions end with it.
The connection code is the only way a tester signs in, so a new one is enough to cut off a code that leaked: whoever held the old one is out. To cut off the tester themselves — whatever code they hold next — use Revoke or Delete.