Skip to content

What are the alerts, and when do they arrive?

In two lines #

Your tools are read every day or every week, depending on the tool; an alert as soon as a tracked event is read; a dated snapshot every week to decide. The alert types: new feature in place, activation announced by the vendor, new AI application connected, usage-based billing enabled, vendor terms or features changed, new model behind a feature, new data access.

The steps #

  1. In “The register”, the banner “Since the snapshot: … alerts”; “Handle all” opens “To handle”.
  2. In “Your feed”, the “Today's alerts” block: each alert carries “Noted on …” and its pace, “read every day” or “read every week”.
  3. A “Usage billing turned on” alert also states the cap: “spending cap read: €…”, or “no known spending cap”.
  4. By email: “A daily alert in your workspace”, with counts and the link “See them in your workspace”; the email carries neither a tool name nor a figure from your company.
  5. The pace of each tool is published at /en/watch/alerts and at /en/trust. An event that a vendor only lets us read once a week is shown as such, tool by tool. “New feature in place” and “Activation announced by the vendor” follow the pace of “Vendor terms or features changed” there.
  6. When the list of users' consents to applications could not be read, it is marked “not read”: Ojja does not compare it with the previous reading, and raises neither “new AI application connected” nor “new data access”. The first reading that contains it is the starting point.

On the Arvenne example #

On the Arvenne example, the meeting recaps enabled by default in Teams are in “To handle”, waiting for a decision.

What Ojja does not do #

Ojja turns off and blocks nothing: an alert is a dated fact, with its source.

The method #

The cadence.

Updated on

Open in Ojja