An Alerting Profile controls who Monitor contacts when an alert reaches a certain Risk Level for a group of users. You can create as many Alerting Profiles as your organisation needs with their own suitable setups.
Tip
You don't need a profile for every group of users. Most organisations need only a few.
Before you begin
You must be a Safeguarding Contact.
Your user groups are set up. Alerting Profiles apply to user groups, so plan your groups first. See Create user groups.
You know which staff are Safeguarding Contacts and which are Limited Safeguarding Contacts. See Safeguarding Contact roles.
How Monitor sends notifications
When an Alert occurs, Monitor:
Checks whether any custom Alerting Profiles exists. If none exist, the default Alerting Profile applies.
Compares the risk level against every Alerting Profile that covers the student's user group.
Sends an email for each match. Monitor calls your Phone contacts only for specific Risk Levels and Risk Categories.
Three results affect how you plan:
No match, no notification: If an alert occurs at Level 2 and every profile notifies from Level 3 and above, Monitor contacts nobody.
Overlapping groups, one notification: If a user belongs to user groups in two profiles, Monitor sends one notification. It copies in the Contacts from every profile that applies.
Users outside every profile: The default Alerting Profile covers any user that no custom Alerting Profile includes. Its settings decide what happens. You can turn off its email notifications, but Monitor still calls its Phone contacts.
Tip
Keep the user groups you use in Alerting Profiles mutually exclusive. This stops Contacts being copied into notifications for users outside their own groups.
Alerting Profiles don't affect monitoring. Monitor logs all alerts, at every level and category, and Safeguarding Contacts can see them in the portal. Alerting Profiles control only who Monitor contacts.
What each Contact type can see
Alerting Profiles control notifications. They don’t control who can open an Alert in the Alert dashboard.
Safeguarding Contacts: Can view and action every Alert, including Alerts for users they aren’t assigned to in a custom Alerting Profile. An Alerting Profile can stop their notifications, but it can’t limit this access.
Limited Safeguarding Contacts: Can receive and view Alerts only for the users in the groups they’re assigned to.
Plan your Alerting Profiles
Create the minimum number you need: Each profile is another item to update when your staff or year groups change.
Use the default profile on its own: This suits you if one person receives all notifications, or if all your Safeguarding Contacts need all notifications.
Appoint few Safeguarding Contacts: Every Safeguarding Contact can view and action all users’ Alerts and devices, whatever your Alerting Profiles say.
Use Limited Safeguarding Contacts to restrict access: Appointing a Limited Safeguarding Contact and assigning them to a profile is the only way to limit which users a Contact can see.
Check your plan against data access: Confirm that no Contact has more access to sensitive user data than the role requires.
Adjust risk levels before you add profiles: Customise your risk levels if the default profile sends too many or too few notifications.
Exclude a Contact from phone calls: Don't add that Contact as a Phone contact on any Alerting Profile. Monitor calls Phone contacts only for specific risk levels and risk categories, so some Contacts never receive calls anyway. They still receive email notifications and can see alerts in the portal.
Choose a scenario
Scenario |
User groups to create |
Alerting Profiles to create |
|---|---|---|
Give each set of users its own Contacts |
One for each school, campus, year or grade |
One for each user group |
Alert some users at a different level |
Vulnerable students, all other users |
One customised, one default |
Set up each scenario
Give each set of users its own Contacts
Use this scenario when different Contacts are responsible for different users. Divide your users in the way that suits your organisation. For example, give each school or campus its own Contacts, or give each year or grade its own Head of Year.
Create a user group for each school, campus, year or grade.
Create an Alerting Profile for each user group.
Assign separate Limited Safeguarding Contacts to each profile.
Note
The user group on the profile decides which users a Limited Safeguarding Contact can see. The notification settings on the profile don't restrict this.
Alert some users at a different level
Use this scenario to receive fewer notifications for older students, or more notifications for vulnerable users at lower risk levels than their age group's default.
Create a user group for vulnerable students.
Create a user group for all other users.
Create an Alerting Profile for the vulnerable students group. Set a lower Age range.
(Optional) Customise the phone and email notifications for lower risk levels.
Create an Alerting Profile for all other students. Keep their default age group and risk levels.
Assign Safeguarding Contacts or Limited Safeguarding Contacts to each profile.
Review your Alerting Profiles
Review your setup when your staff or user groups change, and at least once each school year:
Confirm that your user groups still cover every user in the organisation.
Confirm that the user groups you use in Alerting Profiles are still mutually exclusive.
Confirm that each Contact still needs the access their profiles give them.
-
Confirm that your risk levels produce a useful number of notifications.