Skip to content
Sign inRequest access

Roles & access

Access in uMarker answers two separate questions, and keeping them apart is what makes the rest of this page readable:

What may this person DO?

Their role: one of the two built-in seats, or a custom role you wrote. A role is a set of permissions and nothing else.

What may this person SEE?

Their project access: which projects they are attached to. Set per project, in the project’s Access tab.

By default the two axes stay out of each other’s way: the permissions in a role do not decide which projects appear, and attaching someone to a project hands them no permission. Someone can hold a role that allows deleting a report and still be attached to a single project, in which case that is the only place the permission ever applies.

Two crossings exist, both deliberate, and both named where they live. A role can carry “open every project in the space without being attached to it”, which lifts the attachment requirement for whoever holds it. And a project’s Access tab can hand someone a role in that project only, which then decides permissions inside that project instead of their account role. Unless one of those two is in play, the rest of this page reads exactly as written.

Every account starts with two seats. They are not roles you created and they cannot be edited.

Admin Member
Open the inbox, the board and a report Yes Yes
Triage: status, priority, assignment, labels, merge, bulk actions, resolve a pin Yes Yes
Comment and @mention Yes Yes
Save and delete queue filters Yes Yes
Push a report to the tracker this project routes to Yes Yes
Open a support request to uMarker Yes Yes
See the plan and its usage Yes Yes
Create and configure projects, domains and the widget Yes No
Manage labels, custom fields, surveys, announcements and the changelog Yes No
Connect integrations, mint API keys, set delivery routes Yes No
Manage spaces, the team, roles and billing Yes No

The line has not moved: a Member triages, an Admin configures. Applying an existing label is a Member action; creating or deleting the label is not.

Two rows there are true about the seat and still have a condition outside it. Saving a queue filter needs a plan that includes saved views, which starts at Starter; deleting one is never plan-gated. And pushing a report needs this project to route to a tracker: a tracker connected on the account but not routed here has nothing to push to, and a tracker the current plan no longer covers refuses the push in words rather than silently.

Professional and above

Write a role when the seat does not say what you mean: “reads the inbox and never deletes a report”, “manages the widget on client projects and touches nothing else”, “billing only”.

A role is a name plus a selection from more than 130 individual permissions in 15 groups: the feedback inbox, comments, triage setup, projects, the widget, delivery routes, account connections and API keys, the browser extension, surveys, announcements and changelog, spaces, team and roles, account and billing, support, and AI.

Two properties of that list matter more than its size:

  • No permission exists that guards nothing. Every key in the editor is checked somewhere in the product. A checkbox that grants nothing is a checkbox that lies to whoever ticks it.
  • Destructive actions are split out from the reads they would otherwise ride along with. “View the inbox” and “delete a report” are different permissions. Where a single action genuinely both edits and destroys — writing or clearing a custom-field value, replacing a tracker’s credential, editing an announcement and replacing its image — that one key is labelled destructive, and the editor marks every destructive key so you can see what you are handing over.

Manage roles from Manage team → Roles. Opening a role shows what it grants on one side and who holds it on the other, so you never have to guess before deleting one.

Project access is the second axis: it decides which projects someone can open at all.

  1. Open the project and go to its Access tab.

  2. Attach a person. Attaching them is the grant: it is what lets them open the project and its reports at all. Its settings are a second question — reaching those needs a role that carries them, which the Member seat does not.

  3. Optionally give them a role in this project only. That override wins over their account role wherever a permission is asked about this specific project, in both directions: it can grant something their account role withholds, and it can withhold something their account role grants. Account-wide questions are never asked about a project, so the override has no say in them — moving the project into another space, inviting a colleague, or anything in billing is still decided by their account role.

An account admin, and anyone whose role carries “open every project in this space”, reaches every project without being attached to anything. Everyone else reaches exactly the projects they are attached to, and an empty list means no projects at all.

When uMarker asks “may this person do X?”, it answers in this order and stops at the first one that applies:

  1. Account owner (the Admin seat) or a uMarker operator → yes, always.

  2. A per-project role, when the question is being asked inside a project they hold one in → that role decides, for and against.

  3. A role granted inside the active space, if they hold one → that role decides.

  4. Their account-wide custom role, if they have one → that role decides.

  5. The built-in seat. This is the floor for someone whose access is not described anywhere narrower.

Actions about people are the deliberate exception. Inviting somebody, resending or cancelling an invitation, changing a colleague’s role, suspending, reactivating or deleting them are all account-wide, so they skip steps 2 and 3 and answer from the account-wide role and the seat alone. A role granted inside one space decides plenty, but never who may invite or remove someone from the whole account.

Every one of these is re-read on the server on every request. Client state is never trusted, and the posture throughout is fail closed: when a check cannot be satisfied, the answer is no.

An account is the hard boundary. Almost every record carries an account_id and is filtered by a global scope resolved from whoever is authenticated, so one account’s data is invisible to another.

Asking for a record that belongs to another account returns 404, not 403, deliberately. A 403 would confirm the identifier exists, which turns an error message into a way of enumerating other customers’ data. The developer API’s project endpoints are the one place that answers 403 instead — and there the refusal is worded identically whether the project belongs to somebody else or does not exist at all, so it reveals no more than the 404 does.

A project you are not attached to answers the same way, on every route that names it: 404, rather than an error that reveals it exists. Spaces are looser on purpose — everyone in the account reaches every space unless they have been explicitly confined to particular ones. The Spaces page and the space switcher then list exactly the spaces that person reaches, but the confinement stops at those listings: a space named directly still answers for anyone holding the “see spaces” permission, granted or not. Project attachment, not space membership, is the boundary to hand a client reviewer.

A tester’s access is not a role. The extension appears for them only when all of these hold at once, and the server checks every one of them:

  1. They hold a valid connection code and it has not been revoked.

  2. The page they are on maps to a project in their account, through that project’s domains.

  3. They are assigned to that project.

  4. That project’s widget is live.

  5. That project’s extension surface is switched on — its own toggle on the project page, separate from the widget’s.

  6. The account is not suspended, and the plan is not paused for being over its limits.

Every one is re-checked on the server on every request, and the extension fails closed when it cannot reach uMarker: no capture UI rather than an unverified one. Revoking a tester flags the identity and deletes its live sessions on the spot, so a client that already knows the answer cannot keep using it.