Who Receives Alerts?

Overview

When a goal triggers an alert in ARMOR, the system needs to know who should be notified. Alert recipients can be customized per goal, allowing you to route notifications to the right people based on responsibility, role, or location.

This guide explains how alert notifications are delivered, who receives them by default, and how to configure custom recipient lists for your goals.

Default Notification Behavior

Who Gets Alerts Automatically

Unless you customize recipients, alerts are sent to:

1. The goal creator - The user who created the goal
2. Account Admins - Users with Account Admin role for the account associated with the goal
3. Super Admins - If configured to receive all alerts (optional setting)

Role-Based Alert Access

Who Can See Alerts in the Platform

User Role	Alert Visibility	Notification Delivery
Super Admin	All alerts across all accounts	Configurable - can opt in/out
Account Admin	All alerts for their account(s)	Automatically receives emails
Site Manager	Alerts for their assigned sites	Only if explicitly added to recipient list
Basic User	Alerts for assets they can view	Only if explicitly added to recipient list

Customizing Alert Recipients

Adding Custom Recipients to a Goal

During goal creation:

1. Navigate to Administration → Goal Management
2. Click "+ Create New Goal"
3. Fill in goal details (name, data field, threshold, etc.)
4. Scroll to "Notification Settings"
5. Click "Add Recipient"
6. Select users from the list or enter email addresses
7. Save the goal

Editing existing goals:

1. Open the goal in edit mode
2. Locate "Notification Settings"
3. Add or remove recipients
4. Click "Save Goal"

Recipient Options

Recipient Type	How to Add	Use Case
Existing Users	Select from dropdown list of users in your account	Notify specific team members who already have ARMOR accounts
External Email	Enter email address manually	Notify stakeholders who don't have ARMOR accounts (managers, executives)
Distribution Lists	Enter group email (e.g., fleet-team@company.com)	Notify entire teams without listing individuals

Removing Recipients

1. Edit the goal
2. In the "Notification Settings" section, find the recipient to remove
3. Click the X or Remove button next to their name/email
4. Save the goal

Common Notification Strategies

Strategy 1: Role-Based Routing

Scenario: Different roles handle different types of goals.

Configuration:

• Utilization goals → Fleet managers + operations supervisors
• Efficiency goals → Maintenance team + energy managers
• Safety goals → Safety officers + site managers

Benefit: Alerts reach the people best equipped to act on them.

Strategy 2: Location-Based Routing

Scenario: Goals apply to specific sites or regions.

Configuration:

• Site A goals → Site A manager + Site A supervisors
• Site B goals → Site B manager + Site B supervisors
• Regional goals → Regional manager + all site managers in region

Benefit: Local teams get relevant alerts without being overwhelmed by fleet-wide notifications.

Strategy 3: Escalation Hierarchy

Scenario: Start with frontline staff, escalate if unresolved.

Configuration:

• Level 1 (Initial alert) → Shift supervisors
• Level 2 (If goal remains unmet for 3 days) → Site managers
• Level 3 (If goal remains unmet for 7 days) → Regional director

Note: ARMOR does not currently support automatic escalation. This requires manual monitoring or integration with external ticketing systems.

Strategy 4: Executive Summary

Scenario: Executives want high-level awareness without detailed notifications.

Configuration:

• Daily/Weekly goals → Operations team only
• Monthly goals → Add executives to recipient list for strategic KPIs

Benefit: Executives receive summaries without being flooded with daily operational alerts.

Managing Notification Volume

For Individual Users

To reduce alert emails:

• Ask goal creators to remove you from non-essential goals
• Use email filtering rules to prioritize critical vs. informational alerts
• Review goals quarterly and adjust recipient lists

To increase alert visibility:

• Request to be added to specific goal recipient lists
• Create custom dashboards with alert widgets
• Set up browser notifications for in-app alerts

For Administrators

To prevent alert fatigue:

• Use distribution lists instead of individual addresses
• Route alerts to shared inboxes (e.g., fleet-alerts@company.com)
• Consolidate overlapping goals to reduce duplicate notifications
• Adjust goal frequencies (switch from daily to weekly for less urgent metrics)

Notification Delivery Methods

Email Notifications

What recipients receive:

• Subject line: Goal name + asset identifier (e.g., "Daily Runtime Goal - Forklift #234")
• Body: Alert message (set or clear text), asset details, goal threshold, link to view in ARMOR
• Frequency: Immediate when alert is set, again when alert clears

Customization: Alert messages are configured in the goal settings. Email templates cannot be customized per recipient.

In-App Notifications

Where they appear:

• Alerts page (main navigation)
• Asset detail pages (Alerts tab)
• Dashboard alert widgets
• Notification bell icon (if enabled)

Who sees them: All users with permission to view the affected assets, regardless of recipient list configuration.

Webhook Notifications (Advanced)

For integration with external systems:

• Connect ARMOR to ticketing systems (Jira, ServiceNow)
• Send alerts to Slack, Microsoft Teams, or other collaboration tools
• Trigger automated workflows or scripts

Configuration: Requires API integration setup. Contact ARMOR Support for details.

Troubleshooting Notifications

Not Receiving Expected Alerts

Possible causes:

• Not added to goal's recipient list
• Email address incorrect or unverified in user profile
• Emails filtered to spam/junk folder
• Goal is Inactive or Archived

Solutions:

1. Check goal's Notification Settings to confirm you're listed
2. Verify email address in your user profile
3. Check spam folder and whitelist ARMOR sender address
4. Confirm goal is Active in Goal Management

Receiving Unwanted Alerts

Possible causes:

• Added to recipient list for too many goals
• Account Admin role automatically receiving all alerts
• Distribution list includes your email

Solutions:

1. Review goals you're subscribed to and request removal from non-essential ones
2. If Account Admin, adjust notification preferences or create filters
3. Check distribution list membership and adjust as needed

Duplicate Notifications

Possible causes:

• Listed multiple times in recipient list (e.g., individual + distribution list)
• Multiple similar goals with overlapping scope

Solutions:

1. Edit goal to remove duplicate recipient entries
2. Consolidate overlapping goals to reduce redundancy

Best Practices

• Keep recipient lists focused - Only notify people who can act on the alert
• Use distribution lists - Easier to manage than individual emails
• Document recipient logic - Add notes in goal description explaining who receives alerts and why
• Review quarterly - Update recipient lists as team members change roles
• Test new goals first - Send test alerts to yourself before adding others
• Respect roles - Don't send operational alerts to executives unless strategic
• Enable clear notifications - Recipients should know when issues are resolved, not just when they occur

Advanced: API-Based Notification Management

For organizations with complex notification requirements, ARMOR's API allows programmatic management of alert recipients:

• Dynamically add/remove recipients based on shift schedules
• Route alerts based on on-call rotations
• Integrate with HR systems to auto-update recipient lists

Documentation: See the ARMOR API documentation for details on alert subscription endpoints.

Related Topics

• Goal Alerts & Notifications - Understanding the alert system
• Configuring Daily/Weekly Goal Checks - Setting up check schedules
• Permissions & Roles for Goals - Who can create and manage goals

Getting Help

If you need assistance configuring alert recipients or troubleshooting notifications, contact the ARMOR Support Team.