4 min read

Notifications

The bell, the events that fire, and how to mark them read or archive.

Notifications

The notification bell (top-right of the app shell) keeps you in the loop on team activity. It is enterprise-gated by default and powered by real events — no polling-only or fake counts.

How to open notifications

Click the bell icon in the top-right header. A side panel slides in showing your unread events first, then read events.

If the bell is hidden for your account, you are on a plan tier that does not include enterprise notifications. Contact your workspace Owner if you believe this is a mistake.

What triggers a notification

EvidAI emits a notification whenever one of these events affects you or a review you are assigned to:

  • Review created — a teammate created a review and assigned you.
  • You were assigned — a teammate added you to an existing review.
  • You were unassigned — a teammate removed you from a review.
  • New comment — a teammate commented on a review you are assigned to.
  • You were @-mentioned — a teammate mentioned you in a comment.
  • Phase locked / unlocked — a teammate froze or reopened a phase you participate in.
  • Bundle exported — a teammate exported the review's evidence bundle (audit-trail relevant).
  • Discovery vault hit — a saved Discovery Vault search returned new matching papers.
  • Living-review delta — a scheduled re-search found new studies for a Living Review you follow.

Acting on a notification

Each notification card has:

  • A small icon for the event type
  • The event title and a one-line description
  • The actor's name and a relative timestamp ("3 minutes ago")
  • A primary link that takes you straight to the relevant page (e.g. clicking a new comment notification opens the comment thread inside the review)
  • An ellipsis menu with Mark as read and Archive

Mark as read

Removes the unread badge but keeps the notification in your panel. Use this when you have seen something and don't need to act on it.

Archive

Removes the notification from the panel entirely. Use this for events you no longer want to see (e.g. closed phases, completed exports). Archived events are hidden from the panel but preserved server-side for audit purposes — they still appear in the per-review audit trail.

Mark all as read

A small link at the top of the panel clears every unread badge in one click.

Notification preferences

Some notifications can be muted on a per-user basis:

  1. Open Settings → Notifications (/settings/notifications).
  2. Toggle individual event types on/off (e.g. mute bundle exported but keep @-mention).

A few critical events cannot be muted: assignment changes and phase locks always emit, because they are part of the audit story.

Tips

  • Use @-mention sparingly. It is the only event type that overrides personal mute preferences. Reserve it for genuine "I need your input" moments.
  • Archive aggressively. The bell is most useful when it has zero or near-zero unread. If a notification is older than a few days and you have not acted, archive it.
  • Subscribe via assignment. The fastest way to get notifications about a review is to be assigned to it — see the Review Assignments article.
Did this article help?
Still stuck?