Email Alerts

Every email the platform sends, who it goes to, and its wording. Obtempera's System Administrators only.

For: System AdminLast checked: 2026-11-13Open this page in Obtempera ↗

Email Alerts is in the top bar, and has a tile on Platform Admin. Three tabs: Alert Rules, Email Templates and Email Log. Opened from that tile, the page has a Back link above the title, which returns you to Platform Admin as you left it (or opens Platform Admin if there is no page to go back to, for example in a new tab). Opened from the top bar, it has no Back link.

Who sets the emails

Email Alerts is open to Obtempera's System Administrators only. Customer and Contractor administrators, reviewers and Workers do not see this page and cannot reword, re-route or switch off an email. An email addressed to System Administrator (Obtempera) goes to one shared address, info@obtempera.com, and not to each System Administrator's own mailbox; you see every such email in the delivery history here. Rules and wording apply to the whole platform: Where does this apply? offers Entire platform only. A rule or wording made earlier for one Customer, Country, Contractor or Project is kept for the record but no longer used; such a rule is switched off and cannot be switched back on.

Alert Rules

+ New alert opens Create Email Alert: What triggers the email? (an Event or a Date), When should it send? (minutes, hours or days, before or after), Who gets the email? (one or more recipients; Specific person takes email addresses, separated by commas, semicolons, spaces or new lines), Which email is sent?, then Save alert. Each rule in the list shows its trigger, timing, recipients and wording, with Turn off or Turn on. With no rules of your own, the tab reads System defaults are active: the standard emails go out without any rule.

If something is missing or refused when you save in Create Email Alert or a template editor (for example Specific person with no address), the reason shows in red just above its Save button, and the editor stays open. Closing an editor, or changing tab, clears it.

  • Turning a reminder off stops it, and its emails already queued are not sent. A reminder whose moment had already passed when it was turned on is recorded as missed, not sent late.
  • Every event has a standard email with standard recipients. A rule on an event can add recipients, but never takes the standard ones away: turning that rule off leaves the standard email going as before. Each person gets one email per event, however many rules cover it: the standard recipients get the standard wording, and a rule sends its own wording only to the people it adds who are not already emailed.
  • The same alert cannot be added twice: a new rule with the same trigger, timing, wording and recipients as an active one is refused (This alert already exists), so nobody gets two copies. If the identical rule is turned off, saving it turns that one back on instead.
  • Creating, turning on or off, rewording and deleting wording, and re-sending an email are each recorded in the audit trail (Platform Admin, Audit Events) with who did it and when.

Locked emails. Some events are locked: every email with a personal link (invitations, password resets, the Customer sign-up form, toolkit invitations, audit and Communications survey links), the two-step sign-in emails and signing in paused, and a few more, such as a new whistleblowing report and the weekly AI agents digest. They go straight away to the person they name, cannot be given an alert of their own, and are not offered under Event.

Whistleblowing. Eleven events cover a disclosure: a new report, the acknowledgement and feedback deadlines, a reply to the reporter, the reporter adding something, a report with nobody to handle it, a case with no progress, a closed case, Obtempera appointing a Disclosure Administrator, Obtempera appointing a Disclosure Handler (to the Customer's Disclosure Administrators and the handler), and a case due while its channel is switched off (to Obtempera, instead of the Disclosure Administrator, who cannot act while it is off). None carries what a report says or who made it; those about a case give its reference and a link. They keep going while a Customer, Project or Contractor is suspended or archived.

Date reminders

These are standard and on for everyone:

  • a document expiring: 30 days before, to the Worker and their Contractor Administrator (a Contractor's own declaration document: its Contractor Administrator). The Worker's email is in their own language; everyone else gets a copy in English that names the Worker, for example Aoife Byrne's Passport / ID expires on 05 Jan 2027;
  • a training certificate expiring: 30 days before, to the Worker, and again when it expires, saying it no longer counts and on which Projects that leaves them not compliant;
  • training still to be done: 7 days after it became required, to the Worker;
  • a licence expiring: 30 days before, and the day after it expires, to the Worker and their Contractor Administrator;
  • a Customer's contract with Obtempera expiring: 60 days before, to Obtempera's System Administrators.

A reminder about a date (a document, licence or form date) goes at 09:00 that day in the record's Country; for a Worker's licence, the earliest 09:00 of the Countries they are placed in. A Customer's contract has no Country, so its reminder goes at 09:00 server time.

Three chasers are ready but switched off until a System Administrator turns one on:

  • an invitation not accepted: 3 and 7 days after it was sent, to the Contractor Administrator (who can send it again);
  • a compliance form not submitted: 7 and 14 days after the Worker was invited, to the Worker;
  • a Worker waiting in HR review: 3 days after they submitted, to the Country's HR Administrators.

A queued chaser is withdrawn once its reason has gone (accepted, submitted or reviewed).

Form dates. Under Date, after the records' own dates (Records), you can choose any date question on the Worker compliance forms (Worker compliance form) or the Country Compliance Declaration (Country compliance declaration). A date question added to a form later can be chosen at once. Nothing is sent until you create the alert. Only submitted or approved answers count; a Worker whose placement has ended gets nothing, and a queued email is not sent if the date is changed or the answer withdrawn. A form date has no primary recipient, so choose the Worker or the roles to email. HR Administrator (Project, else Country) emails the Project's HR Administrators, or the Country's where the Project has none; the social security reminder (30 days after the Worker applied for their number) goes to them.

Document expiry for one question. Under Date there is also a group for single documents on the Worker compliance forms, such as Passport / ID or Work Permit Scan: any upload that asks for an expiry date. An alert on one of these is about that document only, not every certificate. As standard, the passport or ID, the work permit, and each country's residence permit, residence card or visa have a reminder 60 days before they expire, to the Worker, their Contractor Administrator and HR, in the document expiry wording (the copy to staff names the Worker). Right-to-work evidence and the Estonian ID card have it too. This is on top of the 30-day reminder every document gets. It goes at 09:00 in the Worker's Project Country and is never sent twice. It reads the expiry date of the Worker's current upload, so a renewed document starts its own count and the old reminder is not sent. Nothing is sent for a document with no expiry date, a question the Worker was never shown, or a placement that has ended.

Email Templates

Every email's wording, System default or custom. Edit template opens the subject and body, with tags you insert that are filled in when the email is sent; Save new version keeps the earlier ones. Create template makes a custom wording, which then appears under Which email is sent?. Delete removes a custom one, with its saved versions, after a confirmation; alerts that used it go back to the standard wording of their trigger.

Emails to Workers go in the Worker's language. Wording you change goes out in English until it is translated again, never as a translation of the old words.

Email Log

When an administrator gets a copy of an email written to a Worker, its link opens that Worker's record (the Licences section for a licence email), not the Worker Portal, which administrators cannot open.

Email history lists the newest 100 emails: Date, Email (its subject and event), Recipient, Contractor and Status. Older emails under the list shows the next 100. To find one email, choose a Status (for example Failed), or type words from its subject or a recipient's address and press Search.

  • Pending: waiting to go, including emails held while email is switched off.
  • Sent.
  • Failed: the mail server did not take it. It is tried again, five attempts in all; one that still fails is reported to the System Administrators by email, once per failed email, with the last error.
  • Will not be sent: deliberately not sent. For example: missed, nobody to send it to, the Customer, Project or Contractor suspended or archived, or its rule turned off. (Email switched off for the whole system holds emails as Pending instead.)

Under a Failed or Will not be sent status, the reason recorded with it is shown: the mail server's answer, or why it was held back.

Resend sends an email again exactly as it was; Latest sends it again in the current wording. Each resend is a new row, linked to the original. A resent invitation or password reset whose link has expired is not sent.

While email is switched off

While email is switched off for the whole system (System configuration), nothing is sent and emails that fall due are held. A red line at the top of every tab says so, with a link to System configuration, and a Resend or Latest says the new row is held as Pending. When email is switched back on, those still useful go out; an invitation or reset link that has expired, or a warning about a date that has passed, is marked missed.