Skip to content
Sign inRequest access

Notification preferences & digest

uMarker tells you when feedback that concerns you changes. You get two independent delivery channels and a set of dials to keep the signal trusted: which events reach you, on which channel, at what times, and how often.

These preferences are per user. You set your own; they never affect a teammate. Every send of the events below checks them, so what you choose here is exactly what reaches you. Account-level messages are a separate matter: a support reply, a billing notice or a platform announcement from us reaches the bell whatever these switches say.

In-app: the bell

The bell in the header and the notification centre at /notifications. Never gated by plan: you must always be able to see what happened to your own reports.

Email

Leaves the product and reaches an inbox, a phone, someone who isn’t looking at the dashboard. Part of the Starter plan (99 ⃁) and above.

Each channel has its own master switch. Under them, the eight report, discussion and integration events each carry their own Email and In-app toggle, so you can (for example) let everything ring the bell while only mentions reach your email. The two Content events are bell-only — see the table.

Ten event types, grouped the way the settings page groups them. Each row carries an Email and an In-app switch — except the two Content rows, which are in-app only: surveys, announcements and changelog entries ring the bell and never send email, whatever their Email switch is set to.

Group Event Fires when
Reports new_feedback New feedback arrives on a project you can see
Reports assigned A report is assigned to you
Reports status_change A report’s status changes
Reports priority A report’s priority changes
Discussion mentioned Someone @mentions you in a comment
Discussion comment A comment is added to a report
Discussion resolved A report is resolved
Content survey_response Someone answers one of your surveys — bell only
Content publish A survey, announcement, or changelog entry is published — bell only
Integrations issue_linked A report is linked to a tracker issue

Your preferences live in Manage account → Notifications, reachable from your profile menu. Any member can reach their own; there is no admin gate.

  1. Set the channel master switches at the top (in-app and email). Either one off overrides every per-event toggle in the table below it. The bell still carries a few account-level messages regardless — support replies, billing notices and platform announcements.

  2. Work down the event table, ticking the Email and In-app columns per row.

  3. Optionally turn on quiet hours and pick a from/to time. Immediate email is skipped inside that window — not delayed and sent afterwards, simply not sent; the bell has already recorded it, so nothing disappears, as long as you left that event’s In-app switch on. The bell itself is untouched by quiet hours, because a do-not-disturb window is about your phone, not about your own dashboard. The daily digest ignores quiet hours entirely: it goes out at your digest hour.

  4. Under Cadence, choose Immediate (email as things happen) or Daily digest (one summary email a day).

  5. Save. The change takes effect on the next event.

There’s also a sound switch for the bell, with a preview button, if a chime helps or bothers you.

Quiet hours and the digest hour are read in your own timezone, the one set in your profile, not the server’s. A window that wraps midnight (say 22:00 → 07:00) is understood as such.

With immediate cadence, each qualifying event queues its own email right away, with no delay built in: it leaves as soon as a worker picks the job up. How long that takes is whatever the queue’s backlog is, not a fixed figure — the platform’s own health check still calls the queue healthy while its oldest waiting job is under five minutes old.

Every immediate email identifies the account and project, quotes a short summary of the report, and carries a button that deep-links straight to it; the digest below is shorter. Mail is sent in your own language: the locale on your profile decides, not the sender’s.

Choose Daily digest and uMarker stops sending individual emails. Instead, every qualifying event is set aside through the day and rolled into a single email:

  1. As events qualify for you, each is recorded as a pending digest item rather than sent immediately.

  2. The notifications:send-digests job runs hourly and picks out whoever’s digest hour has arrived in their own timezone (08:00 by default). It sends their pending items as one email and marks them delivered.

  3. The email lists each item under a plain label with a short quote, and links back to the dashboard.

Some projects you simply don’t need to hear about. At the bottom of the preferences page you can mute a project for yourself: pick it from the list, and it stops notifying you on both channels from that moment on, with no Save needed. It applies to what happens next: on daily cadence, a digest item already set aside before you muted still goes out in that day’s email.

A few behaviours are built in and hold no matter how you set your preferences:

  • No self-notifications. You are never told about your own actions. If you change a status or post the comment, that event won’t notify you.
  • One notification per event. If a single event reaches you for two reasons at once (say you’re both assigned and @mentioned), you get one, not two.
  • Preferences win at send time. The switches and cadence in effect when the event is processed are what apply. Switch to immediate and future events send at once; switch email off entirely and even queued digest items are cleared without sending.
  • Strict tenant scoping. You are only ever notified about accounts you belong to. Losing access to a project stops its new-feedback notifications, and you can no longer be assigned or mentioned in it — but a thread you are already on keeps reaching you: if you are the assignee, or have ever commented, that report’s status, priority, resolved, comment and linked-issue events still notify you. The per-event toggles above are how you turn those off.
  • A frozen member hears nothing. If a teammate is suspended or banned, both the instant mail and the digest stop for them on the spot.
  • Nothing is dropped. The bell is written on the request itself, so no backlog can delay it — except on a bulk action, where it is queued so one click doesn’t block on hundreds. Immediate email goes through a retrying queue: a rejected send is retried and, only after the retry ceiling, recorded as a persistent failure rather than silently discarded. A digest that fails to send keeps its items unstamped and tries again on the next hourly run, with the failure logged for the operator.