Notifications
The bell in the top bar and Discord direct messages — what concerns you, when it happens, the way you chose.
The bell, at the top right (on desktop and phone alike), gathers what concerns you personally: a sanction, a summons, leave or a file to approve, an announcement, a call for your unit, a distress alert. A badge shows the number of unread notifications (“99+” beyond 99). If you chose it, the same notification also reaches you by Discord direct message.
notificationsThe panel
Section titled “The panel”A click on the bell opens the Notifications panel:
- notifications are sorted into Today, Yesterday and Earlier, newest first, each with its icon, its text and how long ago it arrived; unread ones are marked with a dot;
- a click on a notification opens what it’s about (the sanction, the call, the file, the operation…), switching to the right service if needed, and marks it as read;
- Mark all as read (shown while unread ones remain) clears the badge in one go;
- the settings icon (Set my notifications) leads to My profile › Notifications;
- the list is paginated by 15: Show more loads the next ones, and the panel says how many are shown.
With no notification, the panel reads “You’re all caught up”. Escape or a click outside closes it.
Dates follow the organization’s time zone. A read notification is deleted after 30 days.
What triggers a notification
Section titled “What triggers a notification”| Category | You’re notified when… |
|---|---|
| Distress (panic button) | an officer of your service triggers a distress alert, if you are on duty in that service |
| Dispatch (calls, game alerts) | someone else assigns your unit to a call; an important enough game alert (the service’s “Notify from” setting) arrives while you’re on duty |
| Announcements | an announcement for your service or the organization is published |
| Leave | leave awaits your approval; your leave is approved or rejected |
| Sanctions | a sanction is issued to you; a proposal awaits your approval; your proposal is approved or rejected; your sanction is lifted; your suspension ends |
| Summons | you are summoned; your summons changes (date, place, subject); it is cancelled |
| Justice (files, complaints) | a prosecutor or lawyer request you can accept; you’re assigned to a file; your request is accepted or expires; a complaint is handed to you |
| Offense files | a file awaits your approval (you hold an approver grade for its type, or you’re its prosecutor), including once fixed after a rejection; your file is approved or rejected |
| Operations | someone adds you to the officers present on an operation |
| Reports | a report of your service awaits your review (Reports › Review); your report is approved or rejected |
| Payroll (pay) | a period you’re paid on is approved; your salary is paid in game (automatic transfers) |
| Tracking (tags, plate reader) | a tag raises an alert; your reader reads a flagged plate (only a reason you’re allowed to see) |
| Getting started (guide) | owner only: Getting started isn’t finished, one day then one week after creation |
| System | the bot can no longer DM you (see below); this category can’t be set and doesn’t show in the preferences |
You never get a notification for your own action. A notification keeps names as they were when the event happened.
No permission is needed: everyone only sees their own notifications, in each organization separately.
Choosing what you get
Section titled “Choosing what you get”Open My profile › Notifications (the Notifications tab of My profile, or the panel’s settings icon). Your choices apply to this organization only.
notification-prefsMy notifications
Section titled “My notifications”The My notifications card lists the categories, each with its description and two switches: Bell and Discord (direct message). Each toggle is saved at once. The Getting started category only shows for the owner.
The defaults:
- everything lands in the bell;
- by direct message, what concerns you personally: leave, sanctions, summons, justice, payroll;
- the Distress bell can’t be turned off (a padlock and the “Always in the bell” tooltip say so): an officer on duty must see a colleague’s alert. You can also get it by direct message.
The Discord switch is greyed out when a direct message isn’t possible: the organization doesn’t send direct messages, no Discord server is linked, your Discord account isn’t linked, or the organization doesn’t allow that category (the row then says “Not allowed by the organization”).
As soon as you changed a choice, Restore defaults shows under the list and clears your settings. If you turn off both the bell and the direct message of a category, nothing is stored for you in that category.
The right column
Section titled “The right column”- Discord direct messages: the state of your direct messages. Depending on the case: the organization doesn’t send any; no Discord server is linked; your Discord account isn’t linked (sign in once with Discord); or your account is linked and the bot DMs you for the checked categories. If they’re closed, the date the bot will try again shows, along with a reminder of the sending limits.
- Good to know: the grouping, limit and deletion rules described below.
Repeats and limits
Section titled “Repeats and limits”- Repeats close together that are still unread are grouped into a single notification, marked “3 similar”: several requests of the same type to handle (leave, sanctions, files, reports, prosecutor or lawyer requests, game alerts), or the same record coming back (a tag still alerting). The most recent is shown; if they concern several records, the click opens the module’s list. Distress is never grouped.
- At most 20 new notifications per minute per member: beyond that, the next ones are grouped or dropped. Distress always gets through.
Discord direct messages
Section titled “Discord direct messages”The SuperMDT bot DMs you if:
- the organization linked a Discord server you’re on;
- your Discord account is linked (sign-in with Discord);
- the organization allows direct messages for that category (see below);
- you checked Discord for that category.
The message carries the notification’s text, in your language, with an Open in the MDT button. Several similar notifications waiting to be sent become a single message. The bot sends at most 6 direct messages per 10 minutes to each member, and respects Discord’s limits.
If your direct messages are closed (Discord refuses the message), the bot stops writing to you for 3 days and tells you once in the bell. Open them again in Discord (Server privacy › Direct messages), or turn direct messages off in your preferences. The My profile › Notifications page shows the state of your direct messages.
Organization setting
Section titled “Organization setting”In Settings › Notifications (admins, or the permission Delegated administration › Set up notifications), you decide whether the bot may DM members, and for which categories. You don’t choose what members get in the bell: each one sets it in their profile. Each change is saved at once.
notification-settingsAllowing direct messages
Section titled “Allowing direct messages”A switch for the whole organization (on by default). Off, no direct message goes out any more (those still waiting aren’t sent); the bell keeps working. If no Discord server is linked, a note says so: direct messages will go out as soon as a server is linked in Settings › Discord.
Categories allowed by direct message
Section titled “Categories allowed by direct message”The list of categories (all but System), each with its description and a checkbox. An unchecked category is never sent privately, whatever the member chose; in their profile, that category’s Discord switch is greyed out. By default, all are checked. The list is greyed out while the Discord direct messages switch is off.
This card can also be found with the settings search (“direct message”, “categories”…).
Each change is written to the audit log, with the categories added or removed.