Notifications

Stay current with in-app and email notifications across your projects, and tune your preferences.

Notifications keep you current on the records and reviews that involve you, across every project, without having to watch each item. Choose what reaches you in-app and by email, and tune your preferences so the signal stays useful.

This section covers in-app notifications and email delivery with preferences.

Why notifications matter in a controlled system

In a regulated ALM, work moves through defined states, reviews, and approval gates — and the people accountable for each step need to know the moment their attention is required. Notifications are how TraceUnified closes that loop without anyone having to poll the system. When a requirement you own is changed, a review names you as a participant, an approval gate reaches your signature, or a linked item goes suspect, a notification reaches you through the channel you’ve chosen.

The design goal is signal, not noise. Because every module — requirements, tests, risk, architecture, SBOM, reviews, approvals, and releases — feeds the same notification stream, you get one consistent inbox across your whole program instead of a different alerting model per tool. That single stream is also what makes it safe to tune aggressively: you can quiet categories that don’t concern you knowing you won’t miss the ones that carry accountability, because the ones tied to sign-off and suspect propagation are always surfaced.

In-app versus email

Two delivery channels serve different rhythms of work. The in-app Notification Center is the running record you triage while you’re in the tool — grouped, filterable, and cleared as you act. Email delivery reaches you when you’re not looking at TraceUnified, and its preferences let you decide which categories are worth an interruption and which can wait for a digest. Most teams keep approval requests and suspect alerts on email and leave lower-urgency activity to the in-app center.

What’s in this section

Was this helpful?