Notification rules

This page describes the rules system shared by Discord, Slack, and Telegram integrations. It controls which Akiles events and alerts get delivered to the channel.

Toggles

Every notification integration has four checkboxes on its configuration page:

• Notify gadget actions — Sends a message every time someone opens (or otherwise actions) a gadget. One message per opening.
• Notify admin actions — Sends a message for any other event in the audit log — admins editing members, creating sites, deleting groups, and so on. Anything that’s not a gadget opening.
• Notify alerts — Sends a message every time an alert fires (hardware offline, low battery, missing battery, no mains).
• Notify according to custom rules — Enables the Notification rules tab, where you can configure additional finer-grained rules.

The first three are independent toggles, not “either/or” — you can enable all of them, none of them, or any combination. A message is sent if any of the enabled conditions matches.

Custom rules

When Notify according to custom rules is enabled, the Notification rules tab appears on the integration. Each rule there matches additional events or alerts on top of whatever the toggles already cover.

A rule has three filter lists. An event matches a rule when it matches all filters that are set on the rule:

• Verbs — (Event rules only.) The kind of action (create, edit, delete, use, reveal, etc). Empty = match any verb.
• Object types — (Event rules only.) The kind of object (member, gadget, site, permission, etc). Empty = match any object type.
• Alert types — (Alert rules only.) hardware_down, hardware_low_battery, hardware_missing_battery, hardware_no_mains. Empty = match any alert type.
• Sites — Only match events/alerts that belong to one of the listed sites. Empty = match any site, including events that aren’t tied to a specific site.

A rule’s Kind field is either Event or Alert; that determines whether it filters events or alerts and which of the lists above are relevant.

Examples

• Only gadget openings on the front door of one site: Disable all three top-level toggles. Enable custom rules. Add an event rule with verb use, object type gadget_action, and the site you care about. Optionally also restrict by gadget if you only care about specific doors (no built-in filter for that — narrow further with object_types if needed).

• All admin changes to members and groups, anywhere: Disable the top-level toggles. Enable custom rules. Add an event rule with verbs create, edit, delete and object types member, member_group.

• Only hardware-down alerts on a specific site: Disable the Notify alerts toggle. Enable custom rules. Add an alert rule with alert type hardware_down and the site you care about.

• Everything: Enable Notify gadget actions, Notify admin actions, and Notify alerts. No custom rules needed.

Permissions

Custom rules can only filter on object types you have permission to read. For example, you can’t create a rule that filters on permission events unless your role has permission.get. If you leave object types empty (match any), the same check applies to every object type the integration could possibly receive — so admin-style roles will be required for unrestricted rules.

Disabled integrations

When the integration itself is disabled, no notifications are sent regardless of toggles or rules. A warning banner appears on the Notification rules tab in that case.