This article is for Safeguarding Contacts and Cloud Admin/Technical Admins.
Alerting Profiles control who receives Alerts for a Group of users based on the Risk Level for each type of Event. Your Safeguarding Contact should create the minimum number of custom Alerting Profiles needed to protect your users.
How many Alerting Profiles do I need?
If your Organisation has only one person receiving Monitor alerts, or if all of your Safeguarding Contacts need to receive all alerts, you only need one Alerting Profile. Safeguarding Contacts can customise your Alert Levels if the default Alerting Profile is sending too many or too few alerts.
Organisations with multiple Safeguarding Contacts often need multiple custom Alerting Profiles to manage their Groups of users. Use these scenarios to plan and create the minimum number of Alerting Profiles. Identify how you can create Alerting Profiles to reduce the potential for a Contact to have too much access to your users’ sensitive data. You should also review your plan to ensure your Groups and custom Alerting Profiles are easy to update.
Warning
Limit the number of people who are Safeguarding Contacts in your organisation.
- Any Safeguarding Contact can see all users’ Events in the Monitor Portal.
- All Safeguarding Contacts will receive Alert calls and email notifications for any users not associated with an Alerting Profile.
- Only assign Limited Safeguarding Contacts to Alerting Profiles if you need to limit staff access to specific Groups of users.
Before you start
- Your Cloud Admin / Tech Admin and a Safeguarding Contact should identify and plan the Groups from your Google, Azure or Windows directory before syncing with Monitor.
- A Safeguarding Contact should add or edit the Limited Safeguarding Contacts before adding Groups and custom Alerting Profiles to Monitor.
Managing Alerting Profile Scenarios
Some Safeguarding users shouldn't see all Events
Some Organisations need authorised staff members to monitor staff members. Other Organisations may only need to monitor students and not their academic and administrative staff.
| Cloud Admin / Tech Admin | Safeguarding Contact |
|---|---|
Creates two Groups in Monitor:
|
Creates two custom Alerting Profiles to assign separate Limited Safeguarding Contacts for:
|
Heads of Year or separate faculty are responsible for year groups
Your faculty or Heads of Year only need to see the Events and receive Alerts for students in a year group.
| Cloud Admin / Tech Admin | Safeguarding Contact |
|---|---|
Creates multiple Groups in Monitor:
|
Creates multiple Alerting Profiles and assign separate Limited Safeguarding Contacts for:
|
Some users need a higher level of monitoring
You may wish to apply a less sensitive alerting profile to your older students. Or, you may want to be proactive and monitor vulnerable users for lower-risk Events than the recommended default monitoring for their age group.
| Cloud Admin / Tech Admin | Safeguarding Contact |
|---|---|
Creates multiple Groups in Monitor:
|
Creates multiple Alerting Profiles and assign separate Limited Safeguarding Contacts or Safeguarding Contacts for:
|
Some Safeguarding Contacts don’t want to receive notifications
You may have Safeguarding staff who need to view the Events in your Monitor Portal, but do not need the phone calls and email alerts. You can exclude a Safeguarding Contact from all of your Alerting Profiles, as long as all profiles cover all your users.
| Cloud Admin / Tech Admin | Safeguarding Contact |
|---|---|
Must verify
|
Must ensure all Groups have:
|
