The Email settings page lets a Company Admin verify that outgoing email is wired up and send a test of each template without leaving the app. The sender address, API key, and non-prod override are configured at the environment level (not per tenant), so this page is primarily a diagnostic surface.
Navigate via Settings > Email.
What ships the emails
Vuoro sends transactional email (invitations, password resets, notifications, roster-published summaries, shift-swap updates) via Brevo. Two environment variables control the sender identity for all tenants:
| Variable | Purpose |
|---|---|
BREVO_SENDER_EMAIL | From-address. Defaults to noreply@vuoron.fi. |
BREVO_SENDER_NAME | Display name shown in the recipient's inbox. |
There is no per-tenant sender configuration — every tenant uses the same From-address. If you need a tenant-branded sender, that is an infrastructure change and is not configurable from this page.
Checking configuration status
The Configuration card shows:
- API key configured — a green checkmark confirms
BREVO_API_KEYis set in the environment. A warning icon means outgoing email will fail. - Override recipient — the value of
EMAIL_OVERRIDE_RECIPIENT, if set, shown partially masked. When this is populated you are in a non-production environment (see below).
Sending a test email
The Test Send section lets you fire each of the five templates Vuoro ships:
| Template | When Vuoro sends it in normal use |
|---|---|
invite | New user invitation. |
password_reset | User-initiated password reset. |
roster_published | Rich template — summary of an employee's shifts for a newly published roster window. |
swap_requested | Rich template — sent to the target employee of a shift swap. |
notification | Generic template used by the notifications system. |
Pick a locale (Suomi / English), click the template button, and Vuoro queues the message. The response shows the destination it was sent to (masked). In non-prod the destination is the override address; in prod the configured recipient is test@example.com — so production test sends are of limited value and primarily exist to confirm the API key works.
Non-production test override
In any environment where EMAIL_OVERRIDE_RECIPIENT is set, every outgoing message is rerouted to that address. The original recipient's email address is preserved in the subject line, prepended in brackets:
[TO: user@customer.fi] Tervetuloa! Hyväksy kutsu
This lets you exercise password-reset and invitation flows on staging without mailing real users. To disable the override in production, leave EMAIL_OVERRIDE_RECIPIENT unset in the environment file. The override is enforced inside the email processor — there is no way to bypass it from the UI.