Mobile Guardian’s AI Content Analysis automatically reviews web browsing activity, search queries, and app usage across managed devices to identify potentially harmful or concerning content. When the AI detects content that matches your configured risk categories, it generates a flag in the Safeguarding section of the dashboard, allowing administrators to review incidents and escalate them to the appropriate staff.
This article explains how to enable AI Content Analysis, configure the risk categories and sensitivity levels, set up escalation workflows, and manage flagged incidents.
What You Will Learn
- How to enable AI Content Analysis for your school
- How to configure risk categories and detection sensitivity
- How to set up escalation workflows for flagged incidents
- How to review and manage flagged content in the dashboard
- How to customise notification preferences for different severity levels
Prerequisites
- Administrator access to the Mobile Guardian Dashboard
- At least one active Baseline or Conditional profile with web filtering enabled
- Devices enrolled and checking in to Mobile Guardian
Enabling AI Content Analysis
- Log in to your Mobile Guardian Dashboard.
- Navigate to Safeguarding on the left-hand menu.
- Select AI Content Analysis.
- Toggle Enable AI Content Analysis to on.
- Click Save.
Once enabled, Mobile Guardian will begin analysing browsing activity, search queries, and app usage data from all managed devices. Analysis results appear in the Safeguarding section as flagged incidents.
Configuring Risk Categories
AI Content Analysis evaluates content against a set of risk categories. You can enable or disable individual categories and adjust their severity classification to match your school’s safeguarding policies.
- In the Safeguarding section, select AI Content Analysis.
- Open the Risk Categories tab.
- Enable or disable categories as needed.
The following risk categories are available:
Category | Description |
Self-Harm | Content related to self-injury, suicidal ideation, or eating disorders |
Cyberbullying | Harassment, threats, or intimidation directed at others |
Violence | Graphic violence, threats of physical harm, or glorification of violent acts |
Explicit/Sexual Content | Pornographic material, sexually explicit language, or age-inappropriate sexual content |
Weapons | Content related to acquiring, building, or using weapons |
Substance Abuse | Content promoting or instructing on drug or alcohol use |
Adjusting Severity Levels
Each risk category can be assigned a severity level that determines how flagged incidents are prioritised and routed through your escalation workflow.
- In the Risk Categories tab, click the severity dropdown next to the category you want to adjust.
- Select a severity level:
- Critical - Requires immediate attention. Triggers instant notification to designated safeguarding leads.
- High - Flagged for priority review. Included in daily safeguarding summary.
- Medium - Logged for review. Included in weekly safeguarding reports.
- Low - Recorded for reference. Available in the dashboard but no active notification sent.
- Click Save.
Setting Up Escalation Workflows
When the AI flags content, Mobile Guardian can route incidents to different staff members based on severity, category, or whether a student has repeated flags.
Configuring Escalation Rules
- In the Safeguarding section, select AI Content Analysis.
- Open the Escalation tab.
- Click Add Escalation Rule.
- Configure the rule:
- Trigger - Select the condition (severity level, specific category, or repeat offense threshold).
- Assign To - Choose the staff member or role (e.g. Designated Safeguarding Lead, class teacher, year-level advisor).
- Notification Method - Select how the assignee is notified (dashboard alert, email, or both).
- Click Save.
Repeat Offense Thresholds
You can configure escalation rules that activate when a student accumulates multiple flags within a defined period.
- In the Escalation tab, click Add Escalation Rule.
- Set the Trigger to Repeat Offenses.
- Define the threshold:
- Number of flags - The count of flags required to trigger escalation (e.g. 3).
- Time period - The window within which flags are counted (e.g. 7 days, 30 days).
- Assign the escalation recipient and notification method.
- Click Save.
When a student crosses the threshold, the system automatically escalates the matter to the designated staff member, regardless of the individual severity levels of the flags.
Reviewing Flagged Incidents
All flagged incidents appear in the Safeguarding section of the dashboard.
Viewing the Incidents List
- Navigate to Safeguarding on the left-hand menu.
- Select AI Content Analysis.
- Open the Incidents tab.
The incidents list displays:
- Date and time of the flagged activity
- Student name and device
- Category that triggered the flag
- Severity level assigned to the incident
- Content summary showing the flagged browsing activity, search term, or app usage
- Status (New, Under Review, Escalated, Resolved)
Filtering Incidents
Use the filter options at the top of the incidents list to narrow your view:
- Date range - View incidents from a specific period.
- Severity - Filter by Critical, High, Medium, or Low.
- Category - View only incidents from a specific risk category.
- Status - Filter by incident status.
- Student - Search for incidents related to a specific student.
Taking Action on an Incident
- Click on an incident to open the detail view.
- Review the content summary and context information.
- Select an action:
- Acknowledge - Mark the incident as reviewed. No further action required.
- Escalate - Forward the incident to another staff member (e.g. teacher, advisor, safeguarding lead) with an optional note.
- Resolve - Close the incident with a resolution note for record-keeping.
- Click Confirm.
All actions taken on incidents are logged in the audit trail for compliance and accountability.
Configuring Notification Preferences
Administrators can control how and when they receive notifications about flagged content.
- In the AI Content Analysis settings, open the Notifications tab.
- Configure your preferences:
- Dashboard alerts - Enabled by default. A badge appears on the Safeguarding menu item when new incidents are detected.
- Email digest - Choose the frequency (immediate for Critical, daily summary, or weekly summary).
- Quiet hours - Set hours during which only Critical-severity notifications are sent.
- Click Save.
Verification
After configuring AI Content Analysis, confirm the setup is working correctly:
- ☐ The AI Content Analysis toggle is enabled in the Safeguarding section.
- ☐ All required risk categories are enabled with appropriate severity levels.
- ☐ At least one escalation rule is configured for Critical-severity incidents.
- ☐ Notification preferences are set for the relevant administrators and safeguarding leads.
- ☐ After a period of normal device usage, flagged incidents begin appearing in the Incidents tab.
Troubleshooting
Issue | Possible Cause | Resolution |
No incidents appearing after enabling AI Content Analysis | Devices have not synced since the feature was enabled | Allow time for devices to check in and sync. Check individual device status in the Devices section to confirm connectivity. |
Incidents flagged under the wrong category | AI categorisation may not match your expectations for borderline content | Review the flagged content in the incident detail view. If misclassified, resolve the incident and consider adjusting the sensitivity for that category. |
Escalation notifications not being received | Email notifications may be disabled or the recipient is not configured | Check the Escalation tab to confirm the assigned recipient has a valid email address. Verify the Notification preferences include email delivery. |
Too many low-severity flags creating noise | Sensitivity may be set too high or low-severity categories are enabled unnecessarily | Disable categories that are not relevant to your safeguarding policy, or adjust their severity levels. Consider setting low-severity categories to log-only without notifications. |
Repeat offense escalation not triggering | The threshold count or time period may not yet be met | Check the escalation rule configuration. Verify the student’s flag count and the time window in the Incidents tab. |
Flagged content not showing a content summary | The content may have been transient (e.g. a search query that was immediately cleared) | The AI captures metadata at the time of detection. If a content summary is unavailable, review the category and timestamp for context. |
Staff member not appearing in the escalation assignee list | The staff member may not have a Mobile Guardian dashboard account | Ensure the staff member has been added as a user in the Mobile Guardian Dashboard with appropriate permissions. |
Related Articles
- Configuring Safe Content and Web Filtering
- Actions on Web Filter Report
- Bulk Upload Keywords to Your School Keyword Filter List
- How On-Device Synchronisation and Cloud Categorisation Work in Mobile Guardian
Please let us know if you found this helpful.
Thanks for reading! 🙂