Notifications
ExaVault sends activity notifications through Automation rules. A rule selects a path, user, or group to monitor; selects the events that trigger it; and names the users or groups that receive the email.
Outbound email must be configured before a notification can be delivered. See Sending Email.
Create a Notification Rule
Open Automation, create a Notification rule, and choose the target to monitor. Select the triggering events and add a Notify (Email) action with one or more user or group recipients.
By default, the notification task is scheduled when a matching event occurs. You can add a delay in days, hours, and minutes. Events that match during that delay are grouped into one email rather than sent as separate messages.
Path Notifications
Path notification rules generate emails for activity on one path or on any path. A rule can trigger when a file or folder is created, a file is overwritten, a file is read, or an item is moved, copied, or removed. A rule for a specific path can also include its subfolders.
Emails are only sent to users for activity within their home directory.
User Notifications
User notification rules monitor what one user or any user does and what changes are made to user accounts.
The activities that can trigger the notification are any combination of authentication activity (logging in or logging out), changes to a user account (new user created, user updated, user deleted), and file activities (creating a new file, overwriting a file, reading a file, moving a file, copying a file, or deleting a file).
When you create a notification for any user, it is triggered by all users logging in or logging out, and by any changes made to any user accounts. The notification email includes file activities only when the paths are accessible to the user who receives the notification.
Group Notifications
Group notification rules monitor what a group member does and what changes are made to one group or any group.
The activities that can trigger the notification are any combination of changes to a user group (new group created, group edited, group deleted), and file activities by a group member (creating a new file, overwriting a file, reading a file, moving a file, copying a file, or deleting a file).
When you create a notification for any group, it is triggered by any changes made to any user groups. The notification email includes file activities only when the paths are accessible to the user who receives the notification.
One use for group notifications is to monitor exchange flows with external parties. Create a group that represents the external users who connect to your site, then create a group rule triggered when a member downloads or uploads. Add the internal users responsible for monitoring the flow as recipients.
Access Filtering
A notification email includes path activity only when the recipient can list that path and it is within the recipient's Home Directory. This prevents a broad notification rule from disclosing inaccessible path activity to its recipients.
Lifecycle and Troubleshooting
Rules can be enabled, disabled, edited, or deleted from Automation. If a target user, group, file, or folder is deleted, review rules that refer to it. A rule whose target no longer exists can become invalid instead of silently changing to another target.
When a notification does not arrive:
Confirm that the rule is enabled and valid and that the event type, target, and subfolder setting match the Activity record.
Confirm that the recipient has an email address and can list the affected path within their Home Directory.
If a delay is configured, wait for the delay period; matching events are grouped until it ends.
Use Logging > Activity Search to confirm that the triggering event was recorded.
Follow Troubleshooting Emails to check the Celery service logs, SMTP provider, bounces, and recipient filtering.
Share Link visits are not a target type in current ExaVault Automation notification rules. Do not rely on a notification email as proof that an external recipient opened a Link.
Last updated