--- title: Configure a Boss’nX role’s alarm emails by tag and severity description: Choose by tag and severity which alarms send an email to the accounts with a Boss’nX role, and troubleshoot an alarm email that does not arrive. canonical: https://wiki.can-nx.com/en/guides/boss-role-notifications/ language: en product: Boss’nX audience: - administrateur - installateur context: "Boss’nX: role editor, Notifications section of a supervision, role management rights" --- # Configure a Boss’nX role’s alarm emails by tag and severity Context: Boss’nX: role editor, Notifications section of a supervision, role management rights In the Boss’nX role editor, the **Notifications** section determines the alarms for which the role’s accounts receive an email: one rule per alarm tag, with the severities kept, and if needed a general rule for the other alarms. Without rules, the role’s accounts receive no alarm emails. Intended for the administrator or installer authorized to manage roles. To choose the recipient address or pause delivery for one person, follow [the account’s alarm emails](https://wiki.can-nx.com/en/guides/boss-user-notifications/). ## Before you start - Check the relevant supervision and the role assigned to the recipients. - The role’s **Notifications** section must be editable for your account. Some roles are only partially editable. A system role keeps its permissions read-only, but the administrator can edit the notifications of the administrator or owner role, and the owner those of their own role. A shared default role may also restrict editing to the notifications specific to the building. The banner and the eye and pencil icons indicate the sections concerned. If **Notifications** is read-only, involve the authorized person. ## Open the role’s notifications 1. In the relevant supervision, open **Menu → Users**, **Roles** tab. 2. Click **Edit** on the role’s row, then **Notifications**. You can also open [the role’s permissions panel](https://wiki.can-nx.com/en/guides/boss-roles-consult/) and click **Edit** in its **Alarm notifications** summary, when present. 3. Check the role label and the rules already displayed. **No notification rules** means that no alarm email rule is configured here for its accounts. ## Add tag rules 1. Click **Add tag rule**. 2. In **Search tags…**, search for the tag’s label or path. The search ignores case but not accents: try a fragment of the label if necessary. 3. Tick the tags you want. Those already present in the rules are no longer offered. 4. To tick several tags, use a category checkbox, which selects its displayed results, or **Select all**, which acts on the results of the current search. Checkboxes ticked before a change of search remain selected, even when they are no longer displayed. 5. Check the total on the **Add … rule(s)** button, then click it. The counter near **Select all** only counts the visible results; the add button counts the whole selection. 6. Check the new rows. An added rule enables all four severities by default: adjust them before saving. To abandon the checkboxes still ticked in the picker, use **Cancel**, click **Add tag rule** again or click outside. In the search field, Escape first clears a non-empty search; pressing it again with the field empty closes the picker and abandons its checkboxes. Clearing the search alone does not empty the selection. The picker may offer **In this project** for tags present on datapoints but absent from the catalog, as well as their parent paths. Tag and category names may remain in French when the interface is in English. ## Add a custom tag path If the installer gave you a precise path absent from the suggestions, type it in the search. **Use "…"** appears for a valid path: segments of unaccented Latin letters, digits or underscores, separated by a slash. For example, **alarme/eau** has two segments. Uppercase letters become lowercase and leading or trailing spaces are removed; internal spaces, hyphens, accents, double slashes and trailing slashes are not accepted. Explicitly tick **Use "…"**, then click **Add … rule(s)**: **Select all** does not include this suggestion. The action adds a rule to the role; it does not assign this tag to datapoints and does not create a catalog entry. Have someone check that the path matches the intended alarms. If rules on parent and child paths overlap and their expected effect is uncertain, contact support before saving. ## Choose the severities of each rule On each row, click **Critical**, **High**, **Medium** or **Low**. A colored button is selected; a pale button is deselected. You can keep several severities. If you deselect them all, the row shows **Muted**. To reactivate this rule, select the severities you want, then save. A **Muted** row remains a configured rule: the role’s rule counter includes it too. ## Cover the other alarms with the general rule **All other alarms** adds a general rule for alarms that match none of the tag rules. It appears last with **Default**, and its four severities are initially active. The add button disappears as long as this rule exists. Set its severities separately: each tag rule keeps its own. ## Remove a rule 1. On the relevant row, click the **Remove rule** trash icon. 2. In **Remove notification rule**, check the tag or **All other alarms**. 3. **Cancel** keeps the rule. **Remove** removes it from your pending changes. 4. Review the remaining rules, then save, or use **Discard** to return to the loaded state. Removing a rule and leaving it **Muted** are two different settings. To stop emails for certain alarms, also check the other rules and the general rule, which may still cover these alarms after the removal. Have an uncertain result validated by the administrator or support. ## Save the rules 1. After a change, **Unsaved changes** and the **You have unsaved changes** bar appear. 2. To keep the checked changes, click **Save**. This action saves all the role’s changes, not only the visible section. 3. Wait for **Role updated** and the return to the list, without making other settings while submitting. **Discard** returns the whole editor to its loaded state, including any changes made in the other sections, without leaving the page. **Back to roles** asks **Discard your unsaved changes?** if changes are still pending. Declining to leave keeps your input; confirming leaves the page without saving. Closing or reloading the tab may also trigger a browser warning. ## Check the result 1. Reopen the same role, then **Notifications**. 2. Check the tags, the severities and the general rule. Saving validates the displayed rules, not message delivery: delivery is confirmed when an email arrives for an alarm covered by a rule. ## Troubleshooting ### Saving does not complete - **Save** absent: check that you actually changed a value and that the section is not read-only. - **Save** disabled despite a change: another section of the role may contain an invalid configuration. Have its warnings checked before changing other rights. - Refused save: an error may be displayed while your input is kept. If the outcome of the submission is uncertain, check the reloaded state before trying again. ### An expected email does not arrive Check in turn the supervision, the role assigned to the account, the saved rules, the alarm’s tag and its severity. A **… accounts have no email** warning means the account addresses must be checked. Even without this warning, and whatever the reachable accounts counter shows, have the account’s own notification settings and the recipient mailbox checked. The [legacy recipients](https://wiki.can-nx.com/en/guides/boss-legacy-recipients/) page provides a historical reference; it does not replace these rules. If access to the section remains inconsistent or a notification is still missing, contact support@can-nx.com with the project, the role, the alarm concerned, its severity, its time and the checks performed. Do not send any password or access secret. French labels: **Notifications**, **Ajouter une règle de tag**, **Rechercher des tags…**, **Tout sélectionner**, **Ajouter … règle(s)**, **Toutes les autres alarmes**, **Critique**, **Haute**, **Moyenne**, **Basse**, **Muet**, **Supprimer la règle**, **Annuler les modifications**, **Enregistrer**, **Rôle mis à jour**, **Retour aux rôles**.