Notifications
The bell in the top header collects your in-app notifications: things CompStack wants you personally to act on, like a policy you must attest to. A badge on the bell shows how many are unread, and clicking a notification takes you straight to the right page. Check it when the badge lights up; notifications are per user, so nobody else sees yours.
Before you start
- You must be signed in. The bell does not render for signed-out users.
- No special role is needed. Everyone has their own notification list.
- Some notification types depend on modules and roles: workflow-rule alerts go to org admins only, and attestation notices require the Attestations module (see Feature modules and industry presets).
Read your notifications
- Find the bell icon in the top header. It is present on both desktop and mobile layouts.
- Look at the badge. It shows your unread count, or "9+" when you have more than nine unread. No badge means nothing is unread.
- Click the bell. A dropdown opens under it titled "Notifications", listing your most recent notifications (up to 30).
- Each entry shows:
- A red dot and bold title when unread.
- The notification title and a one-line body.
- A relative time: "just now", "5m ago", "2h ago", "3d ago", "2w ago", or a plain date once it is about a month old.
- Click an entry. It is marked read, and if it carries a link you are taken to the related page (for example the Attestations page or My Tasks).
The list refreshes automatically about once a minute, and again every time you open the dropdown, so the badge stays current without reloading the page.
Mark everything read
- Click the bell.
- When you have unread notifications, a Mark all read action appears at the top right of the dropdown.
- Click it. The badge clears and every entry loses its red dot.
Marking read never deletes anything; read notifications stay in the list.
What creates a notification
Notifications are created by events in the system, not sent manually:
- Attestation campaigns: when an admin launches a policy attestation campaign, every targeted member gets a notification titled "Attestation required: [campaign title]", with the due date in the body when one is set. It links to the Attestations page.
- Workflow rules: when a rule with the "notify admins" action matches records (for example overdue CAPAs), each org admin gets a notification titled "Workflow rule: [rule name]" saying how many records matched. It links to My Tasks. The same rule notifies at most once per day, so re-runs do not pile up.
Deadlines in general (CAPA due dates, expiring evidence, certification visits) surface as entries in My Tasks rather than as bell notifications. If you expected a ping about a due date, check My Tasks first.
Try it
- Sign in and look at the top header. Expected: a bell icon on desktop and on mobile.
- Click the bell before anything has happened in a fresh org. Expected: a dropdown saying "No notifications".
- Have an admin launch an attestation campaign that targets you. Expected: within a minute the bell shows a badge, without a page reload.
- Open the dropdown. Expected: an unread entry "Attestation required: [campaign title]" with a red dot, bold title, and "just now" as its time.
- Click that entry. Expected: you land on the Attestations page and the entry loses its red dot.
- Accumulate more than nine unread notifications. Expected: the badge reads "9+".
- Click Mark all read in the dropdown header. Expected: the badge disappears and all red dots clear, but the entries remain listed.
- Reopen the dropdown after a few days. Expected: times display as "3d ago" style relative stamps, switching to a plain date after about a month.
If something goes wrong
- No bell at all: you are signed out, or the page has not finished loading your session. Sign in again.
- The badge will not clear: click the bell and use Mark all read. If a mark-read call fails (for example a brief network drop), the app ignores the error and the next automatic refresh shows the true state; wait a minute or reopen the dropdown.
- A notification did not take me anywhere: not every notification carries a link. Entries without one just mark themselves read when clicked.
- I never get workflow-rule notifications: they go to org admins only, the Workflow Rules module must be enabled, and the rule's action must include notifying admins. Also remember each rule notifies at most once per day.
- My teammate got a notification and I did not: attestation campaigns can target a single department. If the campaign was scoped to a department you are not in, you are not on the list.
- The count seems stale: the bell polls once a minute. Open the dropdown to force an immediate refresh.
- Old notifications disappeared from the dropdown: the dropdown shows the 30 most recent. Older ones are not shown there.
Related pages: Global search, Feature modules and industry presets, Getting started.
← Back to CompStack