Workflow ▸ Notifications

The Workflow ▸ Notifications sub-tab inside a matter is where you configure who Athenty notifies — and what it says — when something happens on that matter. It has two sections:

Configured for this matter

This section lists the notifications that are unique to this matter. Each row is a template that fires only on events tied to this file — for example, a custom heads-up when a particular participant is added, or a bespoke retainer-low message worded for a sensitive client.

Use Add Notification in the top right to create a new one. Each template specifies:

• Trigger — the event that fires the notification (matter created, status changed, participant added, retainer below minimum, …)
• Send to — Matter staff, Matter participants, or both
• Subject + Message — supports the merge tokens {{matter_name}}, {{date_label}}, {{client_name}}, {{org_name}}, {{retainer_balance}}, {{retainer_minimum}}
• Channel — Email, In-app, or both
• Active — uncheck to keep the template but stop it from firing

Inherited from organization

These are the firm-wide and division-wide notification templates that also apply to this matter by default — including the system-default Retainer below minimum notice that emails the primary client when the trust retainer falls beneath the configured minimum.

Each inherited row carries a state badge:

• Active — the inherited template fires on this matter as-is
• Overridden — you’ve configured a matter-specific override; the org template is suppressed and yours fires instead
• Muted — you’ve explicitly disabled the inherited template for this matter; nothing fires on this trigger

Override

Click Override on an inherited row to open the Add/Edit drawer pre-filled from the organization template. Edit the copy, audience, or channel however the matter requires and save — the new matter row takes precedence at fire time, and the inherited row shows the Overridden badge. Click Remove override to delete the matter row and revert to the inherited default.

Disable for this matter

Click Disable on an inherited row to suppress the notification for this matter only. The organization template stays exactly as it is for every other matter; this matter just won’t fire on the trigger. Click Un-mute to clear the suppression and let the inherited default apply again.

Precedence

When a trigger event fires (e.g., a retainer dips below the configured minimum), Athenty looks for templates in this order and uses the FIRST match:

1. The matter’s own row for that trigger
2. The matter’s division’s row (if the matter has a division)
3. The organization’s row

A row at any level with Active unchecked is treated as an explicit mute — the notification is suppressed at that scope. The Inherited section above lets you do the per-matter version of this with one click.

What you do here vs. in Settings → Notifications

Where	What	Who
This tab (matter Notifications)	Per-matter override + per-matter mute	Anyone with edit access to the matter
Settings → Notifications	Organization-wide and division-wide defaults	Owners, Admins

The system-default templates (e.g., the retainer-low client email) are shipped per organization and editable from Settings → Notifications. Changes there apply firm-wide unless a specific matter has overridden or muted them here.