TattvaDocs
Trust & administration

Notifications

Where Tattva tells you something changed — the in-app bell, each tracker's Delivery tab, and the subscription settings.

Tattva can tell you when something needs attention in three places. Knowing which does what saves you from setting up the wrong one.

WhereWhat it does
The bell (top right of each page)Shows project notifications, such as a tracker run that came back Critical or Needs attention, and personal ones, such as a new comment on an answer for the analytics team, or the outcome of a comment you left.
A tracker's Delivery tabSends that tracker's runs to email, Slack or Teams. This is how you get alerts outside the app.
Settings › NotificationsSaves your subscription preferences per project. Tattva stores them but sends nothing based on them. Use a tracker's Delivery tab for alerts.

The bell

Click the bell to open Notifications. Each item shows a title, a line of context and how long ago it happened. Unread items are highlighted.

  • Click an item to open what it's about (for example the tracker or the answer). That marks it read.
  • Click the tick to mark one item read, or Mark all read. Mark all read only marks the notifications you can see.

Most notifications are for the whole project and everyone in it sees them. Some are addressed to one person, and only that person sees them.

You'll see a notification when:

  • a tracker run is classified Critical or Needs attention (everyone in the project);
  • a workspace definition changes that your project overrides, so you can decide whether to keep your override (everyone in the project);
  • someone leaves Not satisfied feedback on an answer in a project where you are an owner, admin or ontology admin: "New feedback: Not satisfied", with the reasons and what they said (each of you gets your own notice; the author does not). Click it to open the comment in Ontology › Maintain › Feedback. If the project has a Slack webhook under Settings › Project › Answer feedback, the comment is also posted to that Slack channel;
  • the team settles a comment you left with Not satisfied: "Your correction was applied", "Your correction is already covered" or "Your correction was not applied" (only you). Click it to open the answer, where the status line says what was changed or why not. The team's internal note is never included.

Getting tracker runs by email, Slack or Teams

  1. Open the tracker and switch to the Delivery tab.
  2. Click Add destination.
  3. Pick Email, Slack or Teams and enter the target. Slack and Teams take an incoming-webhook URL; email takes an address.
  4. Choose the detail level, Summarised or Full, and click Save.
  5. Click Test send to run the tracker and deliver once, so you can check it arrives.

Destinations are set per question. See Trackers.

Settings › Notifications

The page is titled Signal subscriptions and applies to the current project. You can save rules with:

  • Signal types: All signal types, or pick from Anomalies, Invalidated hypotheses, Policy / constraint violations, Forecast misses, Opportunities, Next-best-action proposals, Data-quality alerts.
  • Minimum severity: Info, Watch, Warn or Critical and above.
  • Channels: In-app, Email, Slack or Teams, each with a target and its own severity floor. Add more with + Add channel.
  • Framing: Terse, Standard or With actions.
  • Cadence: Realtime, Hourly digest, Daily digest, Weekly digest or Off.

Click Add subscription. Saved rules appear under Your subscriptions, where you can switch them On or Off or delete them.

These rules are stored but not used to send anything. For alerts you can rely on, use the tracker's Delivery tab and the bell.

Tips

  • Use Test send after adding a destination, so you know it arrives before a real alert depends on it.
  • Deliver to a shared channel only from questions whose rule trips on real problems. Noisy alerts train people to mute the channel.
Notifications — Tattva Docs