Alert detail

Selecting an alert in the Tracker opens its page. A strip at the top shows the alert's illustration when one has been generated; when attribution is available, the information icon on the image shows it. Below it, the content column is divided into Cases, Activity, and Unlinked, with a contents list for jumping between them. The panel on the right holds the alert's actions and settings; on small screens it opens with the Alert settings button.

Actions

Owners and authorized administrators see three actions at the top of the panel:

• Edit alert — opens the conversation-based editor. See Create and edit alerts.
• Pause / Resume — stops or restarts the recording of new events. Existing events stay available.
• Delete alert — asks for confirmation, then permanently deletes the alert's monitoring configuration and saved matches. This cannot be undone.

Other viewers see Shared alert · read-only or System-managed alert · read-only instead.

Definition and details

Below the actions, the panel shows the alert's name and description and, for alerts with a rule contract, the rules it runs. Each rule is summarised in a sentence, with chips for its conditions and tiles for the sources it checks; when there are several rules, the panel notes that Each rule runs independently. A material only needs to match one of them.

Details lists:

• Status — Enabled, Paused, or Setting up;
• Definition ready — when the monitoring definition was last prepared;
• Created — when the alert was created.

Access

The Access section sets who can open the alert: Only me or Selected groups. After choosing groups, select Update to save the change, or Cancel to return to the saved audience. Switching a shared alert to Only me first shows how many groups will lose access. Members of the selected groups can open the alert and receive notifications according to their own settings.

Viewers who cannot manage the alert see a summary instead, such as Owner only or Shared via followed by the group names.

Match sensitivity

Matching sensitivity controls how widely the alert accepts matches:

• Precise — only matches directly about the alert's topic; the least noise.
• Balanced — direct and strong matches; weaker matches are held back near the threshold.
• Broad — also weak matches, clearly marked and without email notifications.

Only viewers who can manage the alert can change the level, and the change is saved immediately. When Persate's calibration suggests a different level, a note above the control reads This alert may be too broad. Consider the “…” sensitivity. Select Set “…” to apply the suggestion or Dismiss to hide it.

Cases

Cases lists the matters the alert follows — for example legislative matters, parliamentary questions, people, or organizations — that were discovered by the alert or attached to it. The number of tracked cases appears next to the heading. Select a case to see its summary, type, origin, and latest activity date, and Open source to go to the source. No tracked cases yet means nothing has been discovered or attached so far.

When RCL projects are attached to the alert, an RCL watchlist appears below the cases with each project's latest stage, latest document, and identifiers. To change the list, search by topic, title, or RCL id and add the matching projects, or remove a project with ×. Changes are marked Unsaved until Save RCL watchlist is selected.

Events

Recorded matches appear in two sections:

• Activity — events linked to a tracked case.
• Unlinked — matches that are not linked to a case.

Each row shows the source type, the time of detection, the speaker for Sejm speeches, an identifier (such as a paragraph or a print number) or a confidence label for the speaker (verified, probable, or unidentified), and a headline. When several observations belong to the same event, the row shows how many observations and sources it combines. Load more loads further events.

Select a row to expand it. Depending on the source, the expanded event contains:

• a link to the source — for example Open act, Open print, Open project, Open on X, Play from a timestamp in the recording, Open file (opens the file in the Repository viewer), or Open source;
• Why this alert? — a short explanation of why the material was accepted;
• Quote or Quotes — passages from the source quoted as evidence for the match;
• Excerpt or Matched fragments — the relevant parts of the text. Fragments are ordered by how well they match, not by their position in the document; a button below them reveals any remaining fragments. When an excerpt is past its retention period, a note asks you to open the source instead;
• labels showing whether the event is linked to a case (Case-linked or Unlinked signal) and whether it starts an event or updates an existing one (Event root or Grouped update);
• Continue tracking with Track full project — when a match covers only newly introduced text in a project, this sets up a separate alert for the whole project;
• Event observations — the individual observations grouped into the event;
• Email delivery — whether an email was sent, queued, or failed, or why it was withheld, for example because email notifications were off, no recipient has alert emails enabled, or the organization's privacy setting prevented it.

Match feedback

Each expanded event ends with Match assessment, which shows the strength of the match (for example Direct) and asks whether it is relevant. Select Relevant or Not relevant. For Not relevant, a reason can be added — Wrong topic, Duplicate, Too minor, Wrong source, or Opposite direction — together with an optional comment sent with Send detail. Persate records the assessment with the event.

Setting up

Right after saving, an alert can show This alert is being set up with the note that tracking starts automatically when setup is complete. No action is needed.

Empty and error states

• No trigger events yet — the alert has not recorded any match yet. Matches appear here as they are found.
• No activity matches this filter. — the alert has events, but none in this section. Check the other section.
• Alert not found — the alert could not be loaded: it may have been deleted or the link may be outdated. Return to the Tracker list.