Guidelines for Custom Alerting Profiles in Monitor

This article is for Safeguarding Contacts and Cloud Admin/Technical Admin.

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. You can also identify which Safeguarding or Limited Safeguarding Contacts receive phone calls. You can specify the order that the Moderator calls contacts until they reach a contact.

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 you need. Identify how you can create Alerting Profiles to reduce the chance 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 and Devices in the Monitor Portal.
  • All Safeguarding Contacts can 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 access to specific Groups of users.

Before you start

  1. Your Cloud Admin / Tech Admin and a Safeguarding Contact should identify and plan the Groups in your directory service before syncing with Monitor.
  2. 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:

  • Staff members
  • All other users or students

Creates two custom Alerting Profiles to assign separate Limited Safeguarding Contacts for:

  • The Group of staff members
  • For all other users or students

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:

  • One Group for each year or grade

Creates multiple Alerting Profiles and assign separate Limited Safeguarding Contacts for:

  • Each year group or grade group

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:

  • One Group for vulnerable students
  • One Group for all other users

Creates multiple Alerting Profiles and assign separate Limited Safeguarding Contacts or Safeguarding Contacts for:

  • The group of vulnerable students with a lower Target Age Range and optional custom phone or email alerts for lower-risk Events
  • The group of all other students with their default age group and default risk-levels

Some Safeguarding Contacts do not want to receive calls

You may have Safeguarding staff who do not want calls, but want to receive email alerts and need to log into Monitor to view Events.

Cloud Admin / Tech Admin Safeguarding Contact

Must verify:

  • All Groups in Monitor cover all users in the Organisation this Safeguarding Contact belongs to

Creates multiple Alerting Profiles:

  • Verify your Alerting Profiles cover all of the Groups your users belong to.

In one Alerting Profile:

  • Assign one other Safeguarding or Limited Safeguarding Contact as the Phone Call Contact (required).
  • Assign the Safeguarding Contact only as an Email Contact to allow them to see all Events in the Portal.

Only call if the other contacts did not pick up the call

One of your staff may be an emergency contact if Monitor Moderators are not able to reach the other Safeguarding or Limited Safeguarding Contact(s) by phone.

Cloud Admin / Tech Admin Safeguarding Contact

Identifies which Group in Monitor:

  • Includes the users this contact is responsible for

Creates or edits an Alerting Profile for this Target Group:

  • Adds up to ten Safeguarding or Limited Safeguarding Contacts to the Phone Call Contacts.
  • Drags the backup contact to the bottom of the list.
  • The Moderator will call the contacts at the top of the list in descending order until a contact picks up the call.

 

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.