Email notifications: send selected audit events to the right inbox

VaultPilot can email selected audit events through an SMTP server that the Owner sets up. Each event has its own delivery rule, and one recipient list receives the mail. Every event stays in audit history whether or not it is emailed.

Set up by: Owner
Delivery rules: Immediate, cooldown or threshold
Test sends: To a separate test recipient

Illustration of an audit event moving through an email outbox to a mail server

Connection and recipients on two screens

Server settings › SMTP holds the host, port, sender, TLS or STARTTLS choice and authentication. The Notifications screen holds the recipient list and the event rules. Owner, Admin and Auditor can open Notifications, but only the Owner can change or save it.

Three delivery rules

Selecting an event does not mean one email for every occurrence. Each row states its own rule, and, depending on the event, grouping looks at the actor or at the actor and target together.

What a test send tells you

Send test uses the current form values, even unsaved ones, and needs a separate test recipient. A success notice means the SMTP server accepted that address. It says nothing about the inbox, quarantine or the reader, so check those with your mail team.

When SMTP is off

Turning SMTP off stops email but keeps the connection details, audit records and in-app notifications. Email candidates created while it is off are deleted from the outbox and are not sent when you turn it back on. The outbox retries temporary failures a set number of times.

Share packages by SMTP

The Sharing screen can use the same SMTP server to send one recipient an external package, the decrypter ZIP and short instructions. The share passphrase is never attached, so send it through another channel. On its way the package passes through the VaultPilot server and the SMTP service, and its content is capped at 12 MiB.