Skip to content
HamstikHamstik Docs

Notifications

Hamstik gives each signed-in account a notification inbox for activity across all of its Organizations. In a private workspace, the bell in the application header shows a compact list of recent notifications. The unread badge is hidden when there are none, shows the exact count through 99, and shows 99+ above 99.

Recent and full views

Open the bell to see recent assignments, mentions, replies, and watched activity. Each row includes the event summary, actor when the actor is still visible, relative time, Organization and Project context, and Work Item context. Use View all notifications for the full center.

The full center provides All and Unread views, keyboard-accessible read/unread actions, and Mark all read. Opening an available notification marks it read and takes you to the relevant Work Item or Project inside your current Hamstik origin. New activity may arrive while you are paging; refresh or retry to load the authoritative server state if a page becomes stale.

The inbox combines activity from every Organization where your account is an active member. The Organization and Project labels on each row help distinguish otherwise similar Work Item keys.

Access and unavailable sources

Notification links are checked against your current membership and access to the Project, Work Item, and comment. A notification never grants access to a source that you can no longer read. If a source was deleted, archived, or is no longer available to your account, Hamstik shows a safe unavailable state and does not display protected titles, actors, comment text, or a protected deep link. Deleted comment content is removed from the notification as well.

Email and the native inbox

The native inbox is the durable in-app record. Email is a separate delivery channel: an email failure does not remove or change the inbox row, and reading an inbox notification does not depend on email delivery.

By default, Hamstik sends immediate email for:

  • Work Item assignment;
  • a mention in a comment; and
  • a reply to your comment.

Watched-comment and watched-status activity is recorded in the inbox but is email-off by default. Notification email contains the current authorized Organization, Project, Work Item, status, and a short comment excerpt when available. Links return to Hamstik and require you to sign in with current access.

Notification email preferences

Open Account settings to configure five account-wide email event families. The setting applies to your account across every Organization:

  • Work-item assignment — when a work item is assigned to you (default: Immediate).
  • Comment mention — when someone mentions you (default: Immediate).
  • Comment reply — when someone replies to your comment (default: Immediate).
  • Watched comment — when a comment is added to a work item you watch (default: Off).
  • Watched status change — when a watched work item changes status (default: Off).

Each choice is Off, Immediate, or Daily digest. These choices only control email. Native inbox notifications continue to be projected when email is Off, including assignment, mention, and reply notifications. A per-work-item mute from the Watch controls takes precedence over watched-comment and watched-status email choices.

When at least one family uses Daily digest, choose an IANA timezone and a preferred local delivery time. The default is 08:00 UTC when no setting exists. There is one digest opportunity per recipient and local calendar date. A digest groups entries by Organization and then Project, and orders them by event occurrence time. A recipient with no eligible entries receives no email.

Preference changes use a clear delivery cutoff. Turning a choice Off cancels a matching pending email or digest entry before it is claimed. A change to Immediate or Daily digest applies to future events immediately; already queued unclaimed events are not moved between channels. Historical inbox events are never emailed retroactively. A worker claim is the transaction boundary: a provider request already claimed may finish, so an extremely narrow race with Amazon SES is possible.

An expected event may be absent from a digest when its source was deleted or archived, access was revoked, the work item was muted, the event was already delivered immediately or included in a completed digest, or the event became ineligible at the final authorization check. Worker downtime does not discard eligible content: the next due run catches up pending eligible entries. A late worker can therefore deliver a digest after its preferred local time.