Notifications
Mirox keeps you informed about what happens in your parks, tickets, and organization. The in-app notification feed is always on — the bell in the header shows your unread count, and clicking it opens your latest notifications. Everything beyond the app (email, Telegram, webhooks) is opt-in: nothing is sent externally until you turn it on.
Where It Lives
All settings below live on your Profile page, in the Notifications tab. Open in Mirox — Profile menu ▸ Profile ▸ Notifications.
The Notification Feed Is Always On
You do not need to configure anything to receive notifications inside the app:
- The bell in the header shows how many unread notifications you have.
- Clicking the bell shows your most recent notifications; clicking an entry marks it read and takes you straight to the park, ticket, or event it refers to.
- View all opens the full notification feed, where you can filter, catch up, and mark everything read.
- When the underlying condition is resolved — an alarm clears, a ticket is closed — the related notification is cleared for you automatically.
Your defaults come from your organization role: a technical manager starts with different notification defaults than a commercial manager. Zero configuration works out of the box — customize only if you want to.
Turn On External Notifications
By default, Mirox sends nothing outside the app. To change that:
- Open your Profile and select the Notifications tab.
- Turn on the master switch Send notifications outside the app.
- Enable and configure the channels you want below.
Turning the master switch off again silences all external channels at once without losing their configuration. The in-app feed is not affected — it stays on either way.
Security Emails Are Always Delivered
Security and account notifications (for example password or sign-in related messages) are always sent to your verified email address. They are transactional and not affected by the master switch or channel settings.
Channels
The Channels card lists every way Mirox can reach you. Each channel has its own switch.
Notifications go to your verified account email address. Choose how they arrive:
- Immediate — one email per notification.
- Hourly digest / Daily digest — notifications are collected and sent as one summary email.
Telegram
Get notifications as Telegram messages from the Mirox bot:
- Click Link Telegram. A Telegram chat with the Mirox bot opens.
- Press Start in Telegram. The link code expires after 15 minutes — if it does, simply start again.
- Back in Mirox, the row shows your linked Telegram username.
Use Unlink to disconnect at any time. If the bot is blocked or the chat is deleted, the row tells you why delivery stopped.
Webhooks
Webhooks push notifications to external systems as HTTP requests — for example into a Microsoft Teams channel or your own automation. You can add up to five webhooks, each with a name, a target URL, and a format (Generic JSON or Microsoft Teams). Each webhook row offers Test, Rotate secret, and Delete actions.
For the full Teams walkthrough, see Connect Microsoft Teams.
Web App
The in-app feed is always on; this switch only controls whether new notifications additionally pop up as toast messages while you are working in the app.
External Messages Are Minimal by Default
Telegram and webhook messages carry only minimal content (what happened and where) unless you enable Include details in Telegram/webhook messages. Keep this off if third parties could read those channels — details can include names and comment text from other users.
Choose What Notifies You
The What notifies me card groups all notification types into product areas — production and alarms, technical infrastructure, tickets, commercial, documents and reports, organization and members, security and account. For each group you control:
- On/off — whether this group notifies you at all.
- Minimum priority — only notifications at or above this priority get through.
- Channels — which channels this group uses (defaults to your global channel selection).
Your organization role provides sensible defaults for all of this. Anything you customized is marked, and Reset to role defaults takes you back to the standard configuration for your role after a confirmation.
Direct Messages Always Reach You
@-Mentions, ticket assignments, and replies addressed to you personally always notify you — they are not filtered by group settings or priority thresholds.
Mute a Park
If one park is generating more notifications than you need, mute it without touching your other settings:
- On the park page, use the bell toggle in the header to mute or unmute the park.
- Or add the park in the Park overrides card of your notification settings, where you can also see and remove all existing overrides. Besides muting, a park can be set to Watching all — every notification from that park reaches you regardless of your group settings.
Muting a park stops the broadcast stream from it — but @-mentions and ticket assignments in that park still reach you.
Mute or Watch a Ticket
Every ticket has its own notification control, directly on the ticket:
- Mute — stop notifications about comments and status changes in this ticket. @-Mentions and assignments still come through: when someone addresses you directly, you are always notified.
- Watch — get notified about all activity in a ticket even if you are not participating in it.
By default you are notified about tickets you participate in: tickets you created, tickets assigned to you, and tickets you commented on.
Working Hours
If you do not want external notifications around the clock, set a delivery window:
- In the Notifications tab, enable the working-hours option.
- Pick your weekdays and a time range. Times use your local time zone.
Outside the window, external notifications are held and delivered together as a single summary when the window next opens. Critical alarms and direct notifications (mentions, assignments) are delivered immediately regardless — working hours never delay what genuinely cannot wait. The in-app feed is unaffected.
Related Guides
- Connect Microsoft Teams — post Mirox notifications into a Teams channel
- Tickets — the ticketing workflow that drives mentions and assignments
- Events — the park events behind production and infrastructure notifications