Each area supervisor should only see the alarms of their own area

[LogicAutomation]

Our plant has three areas (raw material, production, utilities) and about 250 alarms in one Omnivex SCADA project. The area supervisors complain that the alarm list on their client is full of alarms that are not their responsibility, so they start ignoring it.
I already restricted pages per user, which works well. Now I want the same for alarms: the utilities supervisor should only see compressor, boiler and chiller alarms, for example. Is this possible, and does it also affect which alarms are sent by email or SMS?

[Technical Support]

Yes. Alongside page authorization, the User Editor has Alarm Authorization.
Assigning alarms to a user
1. Open the User Editor and select the user (for example the utilities supervisor).
2. Go to the Alarms tab, choose the alarms that belong to this user's area and click Add.
3. They appear under Subscribed Alarms. Use Delete to remove an alarm from the list.
This works the same way as page authorization with Subscribed Pages.
Making it manageable with 250 alarms
- Use clear Name and Description values with an area prefix (for example "UTL – Compressor 2 pressure low"). This makes selection much easier.
- Use Level (high, medium, low) and Color consistently, so the most important alarms stand out even inside an area.
- Users can additionally filter the list in the Client Alarm Panel.
- If you maintain alarms in Excel, export them with File > Import/Export Alarms to review names and levels in one place.
Email and SMS
Notifications are configured per alarm in the Alarm Editor with E-mail Active and SMS Active, and the recipients come from the E-Mail Editor and SMS Editor settings. Alarm authorization is a user setting and should not be relied on for notification routing. If each area needs its own recipients, describe your setup to us and we will check the best option for your version.
Test
Sign in on a client with the supervisor's user and trigger a test alarm from another area. It should not appear in that user's list.
Documentation: https://greensoft.ai/documentation/o...tem-interface/