Skip to main content

​
Overview

Alert rules define the criteria that trigger notifications in Signal. When an incident is created that matches a rule’s criteria, alerts are sent to the configured recipients.
Only users with the Owner, Admin, DSL, or Deputy DSL role can create and edit alert rules.

​
Creating an Alert Rule

1

Navigate to Alert Rules

  1. Go to Settings in the main navigation
  2. Click Alert Rules
  3. Click Create Rule button
2

Name Your Rule

Give the rule a clear, descriptive name that explains what it monitors.Good examples:
  • “Self-Harm Incidents - All Students”
  • “Bullying - Year 7 Students”
  • “LAC Student Incidents”
3

Configure Criteria

Select the criteria that incidents must match to trigger this alert. You can combine multiple criteria.
4

Set Recipients

Choose who should receive alerts when the rule triggers.
5

Save

Click Save to activate the rule.

​
Rule Criteria

​
Available Criteria Types

Alert when incidents have specific categories.Example use: Alert DSL for any self-harm or child protection incidents.
Alert for incidents involving specific students.Example use: Monitor a student going through a difficult period.
Alert for incidents involving students in specific groups.Example use: Alert for any incidents involving Looked After Children.
Alert for incidents at specific locations.Example use: Monitor incidents in areas of concern.
Alert for incidents involving students in specific year groups.Example use: Monitor transition year students (Year 6, Year 11).
Alert for incidents involving students in specific classes.Example use: Monitor a class with known dynamics issues.
Alert for incidents involving students with SEN status.Example use: Ensure SEN students receive appropriate support.
Alert for incidents involving Pupil Premium students.Example use: Track safeguarding concerns among disadvantaged students.

​
How Criteria Combine

Rules use two types of logic:
  • Within each criteria type: OR logic (matches any selected value)
  • Across different criteria types: AND logic (must match all types)
Rule: “Bullying in Year 7”
  • Category: Bullying
  • Academic Year: Year 7
This rule will alert when an incident:
  • Has the “Bullying” category AND
  • Involves a Year 7 student
Rule: “Self-Harm or Bullying for Vulnerable Students”
  • Categories: Self-Harm, Bullying (OR)
  • Student Group: Vulnerable Students
This rule will alert when an incident:
  • Has “Self-Harm” OR “Bullying” category AND
  • Involves a student in the “Vulnerable Students” group

​
Alert Recipients

​
Recipient Options

Select individual staff members who should receive alerts.Best for: Dedicated safeguarding leads who should see all matching alerts.
Select user groups whose members should receive alerts.Best for: Teams that share responsibility for certain students or categories.
Alert all users who have permission to view the student.Best for: Ensuring everyone involved with a student is informed.

​
Managing Rules

​
Editing Rules

  1. Go to Settings > Alert Rules
  2. Click on the rule you want to edit
  3. Make your changes
  4. Click Save

​
Enabling/Disabling Rules

You can temporarily disable a rule without deleting it:
  1. Go to Settings > Alert Rules
  2. Toggle the Enabled switch off
  3. The rule will stop triggering until re-enabled

​
Deleting Rules

  1. Go to Settings > Alert Rules
  2. Click on the rule
  3. Click Delete
  4. Confirm deletion
Deleting a rule is permanent. Consider disabling instead if you might need it later.

​
Example Rules

​
High-Priority Category Alert

Name: “Child Protection Disclosures”
  • Criteria: Category = Child Protection
  • Recipients: DSL User Group
  • Purpose: Ensure immediate DSL awareness of any child protection disclosures

​
Vulnerable Student Monitoring

Name: “LAC Student Incidents”
  • Criteria: Student Group = Looked After Children
  • Recipients: Virtual School Head, DSL
  • Purpose: Track all incidents involving LAC students for reporting and support

​
Location-Based Alert

Name: “Playground Incidents”
  • Criteria: Location = Main Playground, Junior Playground
  • Recipients: Duty Staff User Group
  • Purpose: Monitor incidents in areas requiring supervision review

​
Best Practices

Start Simple

Begin with a few essential rules for your highest-priority categories

Be Specific

Combine criteria to avoid overwhelming staff with too many alerts

Review Regularly

Periodically review rules to ensure they’re still relevant

Use Clear Names

Name rules so staff immediately understand what triggered the alert

​
Troubleshooting

Check:
  • Is the rule enabled?
  • Do the criteria match the incidents being created?
  • Are recipients configured correctly?
  • Does the incident meet ALL criteria types (AND logic)?
The criteria may be too broad. Try:
  • Adding additional criteria to narrow the scope
  • Using student groups instead of “all students”
  • Focusing on specific high-priority categories
Review the recipients configuration:
  • Check if the correct users/groups are selected
  • Verify user group membership is up to date
  • Consider using specific users instead of “all visible users”