Notifications How to decide which events notify your team, who they reach, on which channel, and what people are allowed to mute.

Settings, Notifications, Notifications. The event catalogue and its routing rules. You need weight 90 plus the capability to view settings.

This surface sets policy for everyone. What an individual receives is filtered further by their own preferences - see Your Account.

The Model

Three layers, in order:

1. An event happens - a deal is won, leave is requested, an invoice goes overdue.
2. A rule routes it - to a pattern of people, on chosen channels, at a priority.
3. The person's preferences filter it - they may have muted email, if the event allows muting.

An event with no rule notifies nobody. An event whose rule includes only in-app will never send email, no matter what the recipient has switched on.

Finding An Event

The catalogue is grouped by area, collapsed by default, with counts of events and active rules on each header.

• Search by event name or key.
• Filter by area to see one department's events.
• Filter by routing pattern to audit everything routed one way - useful for finding every broadcast.
• Show inactive reveals rules that are switched off.

Events with no rule at all appear as unconfigured, so gaps are visible rather than silent.

The Eight Routing Patterns

Who a rule reaches:

Pattern	Reaches	Configure
Manager Chain	Walks up the actor's manager chain	Chain depth, 1 to 5
Role in Department	Everyone in a department above a weight	Minimum weight
Department Head	The head of the actor's department	-
Direct	A specific user carried in the event	-
Broadcast	Every non-client user in the organisation	-
HQ Module	People with access to a chosen area	Target area and minimum tier
Entity Owner	A person named inside the event, such as a deal owner	The payload field
Role-based	Matches role names. Legacy	-

Manager Chain is the workhorse for anything needing sign-off. Depth 1 is the direct manager only; depth 3 walks three levels up.

HQ Module is right for area-wide news - everyone in Finance at manager tier and above. You pick the area and the minimum tier: Dept Head (80), Manager (60), Senior (40) or Staff (25).

Broadcast reaches everybody. Use it sparingly. It is the single fastest way to train a team to ignore notifications.

Editing A Rule

1. Find the event and expand it.
2. Choose the routing pattern. The configuration fields underneath change to match; some patterns have none.
3. Set the pattern's target - depth, weight, area, or payload field.
4. Choose the channels - in-app, email, Slack, WhatsApp. More than one is allowed.
5. Set the priority - low, normal, high or urgent.
6. Optionally set escalation - after how many hours, and to whom, plus a fallback recipient.
7. Edit the templates - the title, the body, and the link the notification opens.
8. Save.

An event can carry more than one rule, which is how a single event notifies two different groups differently - the owner in-app immediately, the department head by email after four hours.

Mandatory And Optional

Beside each event is a control with two positions:

• Mandatory - recipients cannot mute it.
• Optional - recipients may mute it in their own settings.

Anything about security, compliance or sign-in is locked Mandatory and the control is disabled. Nobody can opt out of being told their account was accessed.

For everything else, the default is a judgement call. A useful line: if not receiving it could cause a business failure, it is mandatory. If it is useful but not critical, make it optional and let people manage their own attention.

Setting Up From Scratch

1. Start with the unconfigured events. Filter to them and decide, for each, whether it should notify anyone at all. Most should not.
2. Route the approvals first. Anything needing sign-off, on Manager Chain, in-app plus email, with escalation.
3. Route the exceptions second. Overdue, failed, rejected - these are what people actually need to know.
4. Route the good news last, and prefer optional. A won deal is worth announcing; nobody needs to be unable to mute it.
5. Leave routine progress unrouted. Every event you route makes every other one less visible.

WhatsApp

Settings, Notifications, WhatsApp is the separate surface for staff numbers, PIN status and command access - who can act on the platform over WhatsApp, and whose PIN is locked.

Common Questions

Nobody received a notification. Check in order: the event has a rule, the rule is active, the routing pattern resolves to actual people, and the org graph has the managers or heads that pattern needs.

Somebody received it who should not have. Look at the pattern. Broadcast reaches everyone; HQ Module reaches by area access, which is wider than most people expect.

Someone wants to mute an alert and cannot. It is either set Mandatory, or it is a security, compliance or sign-in event, which is locked.

Can I change the wording? Yes, the title, body and link templates are editable per rule.