Notifications

Mirox tells you what happens on your plants, in your tickets and in your organization. Out of the box your organization role decides what reaches you — you only change what you want to be different.

Where notifications arrive

Mirox has three ways to reach you, and you choose them per category:

• App — the notification center behind the bell in the header, the unread badge and, if you use the Mirox iOS app with a registered device, mobile push. App notifications are always delivered immediately.
• Email — to your verified account address, immediately or as a digest (see Email).
• Webhook — signed HTTPS requests to Slack, Microsoft Teams, Discord or your own endpoint, for the plant categories only (see Webhooks).

Everything you receive on any channel also lands in the notification center. Clicking an entry marks it read and takes you to the plant, event or ticket it is about; View all opens the full notification center. When the condition behind an alarm ends, you receive a resolution notice and the original notification is marked resolved.

What notifies me

The What Notifies Me card lists one row per category, grouped into Sites, Alarm system, Alert Manager, Organization and Personal (system administrators also see Admin). Only categories that can actually notify you are shown. Each row has:

• the category name with an ⓘ that explains what it covers;
• a Preset or Custom badge — Custom means you changed the row; the revert arrow returns it to your role's preset;
• a switch per channel: App, Email and — on plant categories, once you have set up a webhook — Webhook;
• the minimum level from which the category notifies you.

Alert Manager carries the alerts of your organization's own alert rules; each rule sets the level of its alerts, so the minimum level you pick here decides which rules reach you.

Wind turbines, battery storage, solar trackers, park controllers and solar components do not have rows of their own: a turbine or a battery unit that stops is reported in Production exactly like an inverter, and a data source of any kind that goes silent is reported in Availability. One set of rows covers every plant type. The alarms a device reports itself — the manufacturer's own alarm and warning list of an inverter, a wind turbine or a battery — are filed under the Vendor alarms category in the event list. They never notify, so that category has no row here.

Reset to defaults at the top of the card removes all your changes after a confirmation, and the defaults of your organization role apply again. The card names the role your defaults come from.

Choosing a minimum level

Every event has a fixed level — Critical, Very high, High, Normal, Low or Very low — defined by the platform, the same on every plant. You decide from which level upwards a category notifies you: an event reaches you if its level is at or above the row's minimum and at least one channel is switched on.

• Critical — physical danger: fire, thermal runaway, an arc in a wind turbine or a battery storage system, an intrusion alarm. Choose it if you only want to be woken for danger.
• High — a site situation: units down, a data source or the VPN lost. The recommended minimum for whoever answers for a plant's operation.
• Normal — additionally each single solar unit's own outage and other single-unit states. The lowest minimum you can select.

What each level means, why it is set the way it is, how fast each event is detected and real examples from the platform are listed in the list of alarm levels and examples.

Levels are fixed, not per plant. You cannot raise or lower an event's level for yourself or for one plant: every event is tagged the same way everywhere, so that responses and escalation can be automated. If a level does not suit you, use Suggest a different level on the category or the event — it reaches our support, and we adjust the level for everyone. The reasons, and the planned alerts on thresholds of your own metrics, are in Why levels are fixed.

Role defaults

Your organization role sets which rows start switched on and at which level. In short:

• Asset Manager (Technical) starts with the plant categories on from High, the alarm system on from Very high (so only signals at Very high or Critical notify — among the fixed contacts, the intrusion alarm itself), and the monitoring agent armed at Critical.
• Moderator starts with Availability on from Very high; Member with Production and Availability on from Very high.
• Admin, Asset Manager (Commercial) and External start with the plant categories off; switching one on starts it at the role's level.
• Plant categories notify through the App by default; email is off for them until you switch it on per row.

The full table is in Alarm Levels — Defaults for your role.

Always delivered

Some notifications reach you whatever your settings:

• Authentication — suspicious logins, failed login attempts, password resets and two-factor changes.
• Invitations — organization and cooperation invitations.
• Mentions, assignments and replies addressed to you personally.

The first two appear as locked rows at the bottom of the card. Notifications at Critical level and those addressed to you personally also skip email batching and working hours.

Alarms and your sign-in

Alarms do not depend on your sign-in or on 2FA. The alarm notifications you have switched on are delivered on the channels you set up, within your level and mute settings.

• They also arrive on a phone whose sign-in has ended and is waiting for a new sign-in. If you sign out in the app yourself, push to that phone stops; your other channels keep delivering.
• They also arrive for plants that are hidden from you because the organization that owns them requires 2FA and your account has none.

To open the plant itself you have to be signed in, and for a hidden plant you enable 2FA first.

Email batching & working hours

The Email Notifications card sets how emails are delivered; which topics email you is chosen per row under What Notifies Me.

• Delivery — Immediately (one email per notification), Hourly digest or Daily digest.
• Working hours — pick weekdays and a time range in your local time zone. Outside the window emails are held and sent when it next opens; off means any time. App notifications and mobile push are never held.
• Push first — while the mobile app is registered for push, non-security emails wait a few minutes and are only sent if you have not already acknowledged the notification in the app. Email stays the fallback.

Webhooks

The Third-Party Notifications card sends notifications to other systems — a team chat or your own automation. Webhook deliveries are sent immediately, even while you are online, and are never held back because you have already read the notification in the app: every matching event is delivered, which makes them reliable automation triggers. They are limited to the plant categories (Production, Availability, Sensors, Control signals, Alarm system, Monitoring agent).

• Add webhook — up to five endpoints, each with a name, a URL and a format: Generic JSON, Slack, Microsoft Teams or Discord.
• Generic JSON endpoints receive signed HTTPS POST requests (X-Mirox-Signature, an HMAC-SHA256 of the body with a per-endpoint secret shown once). You can add Basic or Bearer authentication and custom headers; their values are write-only.
• For chat formats, the webhook URL itself is the credential — treat it like a password. For Teams, create the URL with the Workflows app; see Connect Microsoft Teams.
• Each endpoint offers Test, Rotate secret, edit and Delete. An endpoint that keeps failing is disabled; fix it and use Test or Re-enable.

Once a webhook exists, the plant rows of What Notifies Me show a Webhook switch so you can choose per category what it receives.

Test a channel

The last row of What Notifies Me — Send a test notification — runs the real delivery pipeline for one channel: in-app, mobile push, email or a webhook. Add an optional message, click the channel's icon and the row shows per target whether the test was sent, skipped or failed.

Mute a plant / watch a ticket

• Mute a plant — the bell in a plant's page header mutes your notifications for that plant. Mentions and assignments still reach you, and so do notifications about tickets you created or are assigned to. Click it again to unmute.
• Mute or watch a ticket — the Notifications box on a ticket offers Default (you are notified as a participant: tickets you created, are assigned to or commented on), Watching (every change) and Muted (nothing — mentions still reach you).

Support requests

When support has answered your support request and nothing more happens on it for 7 days — no message, reaction or status change from either side — the request is closed automatically. One day before, you receive a reminder, delivered like a support reply (app, push and email). Write a message or reopen the request and the 7 days start again. The automatic close itself sends no notification.

• A request support has not answered yet is never closed automatically.
• A request in status Waiting is never closed automatically, however long it stays quiet.
• You can close your request yourself at any time and reopen it later.
• Writing a message into a closed request reopens it.

Related

• Alarm Levels — every event that can notify, its level, timing and examples
• Connect Microsoft Teams — post Mirox notifications into a Teams channel
• Events — the plant events behind the notifications
• Tickets — the workflow behind mentions and assignments