User manual

Configure and read alerts

In Alerts, distinguish workspace events from threshold rules. Changes require management permissions; advanced thresholds and their deliveries remain subject to Enterprise rights and available channels.

Section 1

Read events before creating a rule

History shows the event type, time and read or unread status. Reading it before creating a rule shows you which events have already reached the workspace and which signals deserve a threshold.

Events may concern a ready collection, prepared report, regression or facts needing review. Marking them as read does not resolve the underlying issue.

  1. Open Alerts and load the selected brand’s history.
  2. Check the event and date; use the mark-as-read command when available.
  3. Refresh history to check the result and distinguish an empty list from a failed load.
Alert history: recorded events, such as a prepared report or a collection ready for review, with the time and whether they were read (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 2

Choose an authorised sample

A rule concerns a reviewed sample with an identifiable source, market and language. Starting from an authorised sample keeps the alert tied to observations you can open and check.

Rules do not monitor the entire web indiscriminately. Permissions are rechecked before delivery; a saved rule does not retain access that has been withdrawn.

  1. Open Threshold alerts and read the proposed samples.
  2. Select the relevant sample and check its stated coverage.
  3. If no authorised samples are available, return to data and reviews rather than inventing a threshold.
New alert rule: choosing the reviewed sample the rule measures, with its authorised market, language and assistant (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 3

Set the metric, window and interval

Choose negative share or observed mentions and define when the signal matters. Threshold, minimum sample, window and interval decide how often you receive an alert and how solid the signal behind it is.

A reached threshold is a signal to assess. Insufficient data, an oversized sample or missing access does not mean there are no problems.

  1. Choose the metric and enter a threshold within the form’s permitted limits.
  2. Set the minimum sample, window in hours and minimum interval between alerts.
  3. Select available channels, confirm and save the rule, then reread its status and configuration.
New alert rule: the measure, the threshold that triggers it, the minimum sample, the window in hours and the gap between two alerts (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 4

Enable a channel only when available

Email and device notifications have separate requirements and consent. A rule uses only the channels available in its form: enabling them first keeps you from saving an alert that cannot reach you.

A channel disabled in the form cannot be enabled by selecting another rule. Notifications do not contain customer data; the workspace link still requires authorised access.

  1. For email, check configuration and your delivery preference.
  2. For device notifications, use the offered activation and grant browser permission only if you want notifications.
  3. Reopen the rule and select the newly available channel before confirming the save.
Channels of an alert rule: the email link to the workspace and the alert on this device, which can be enabled only when they work (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 5

Review, disable and check outcomes

Read a rule together with its configuration and evidence, rather than just its status colour. That way you understand whether it found a signal worth assessing or needs changing or switching off.

Waiting for a check, staying below a threshold and having insufficient observations are different outcomes. Do not multiply requests to compensate for a missing confirmation.

  1. Open the reviewed sample to examine the observations behind the signal.
  2. Use edit or reactivate to change a rule and disable it when no longer needed.
  3. After an unconfirmed error or conflict, refresh the status and check its version before retrying.
Alert rules with their status: one with the threshold reached, one below the threshold and one disabled, each with its channels and last time, and below them the history of sent alerts (fictional brand, demo data)
Demo data · Ilmarde Audio

Related paths

Definitions, FAQs, guides and methodology: from here you reach the material you need to read the results and explain them to your team in the same words.

From question to action

Learn how to use TrustInsider: choose the brand and the questions, read the collected answers, update your content and compare the results.

Read

Find the right answer

Help with access, credits, collections, integrations and data: guides, FAQs, the site assistant and support requests from your workspace.

Read