Emails the platform sends

Oclavex sends a fixed set of transactional emails on your behalf. Use this table to answer “did the customer get a mail for that?” — there is nothing to configure per message; the platform sends them when the trigger fires. Every email sent for a tenant names the organization it concerns, with the tenant’s endpoint name and address, so a recipient who administers more than one tenant can tell them apart; the account and usage-limit subjects carry the organization name too.

Trigger	Recipient	Purpose
Account confirmation — a user registers, requests a resend, or changes their email	The account address	Confirm the address belongs to them
Account activated — an administrator approves a pending account	The account address	The account is ready to sign in
Password reset	The account address	Reset link; an administrator’s invite arrives as this same email
Sign-in methods changed — a passkey or authenticator app is added or removed, recovery codes are replaced, or an administrator resets them	The account address	What changed, so a change the user didn’t make doesn’t go unnoticed
Signup verification — onboarding sign-up	The sign-up address	Verify the address before the account is created
Tenant created — onboarding completes	The account address	Your environment is ready — the email includes its URL
Tenant renamed — a change of your tenant’s address is committed	The tenant administrator	Your address has changed — the old and new address, the new portal links, and what to update in applications that call the API or sign in through Oclavex
Endpoint name approved — a reviewer approves a change of your endpoint name	The tenant administrator	The approved name and your portal address, with the reviewer’s note if there is one
Endpoint name change declined — a reviewer declines a requested change	The tenant administrator	The name you asked for, the reason, and that your address is unchanged
Endpoint name reverted — a reviewer changes your endpoint name back to the one you signed up with	The tenant administrator	The reason, your address now, and that you need to sign in again there
Subscription activated — a new tenant’s Oclavex subscription is set up	The tenant administrator	Your subscription is live — the email opens its Subscription page in your admin portal
Subscription started — a paid Oclavex plan is bought	The tenant administrator	The plan is active; receipts and invoices come from Stripe
Plan changed — a paid plan is switched to another paid plan	The tenant administrator	The old and new plan; on a downgrade, that anything beyond the new limits is blocked and nothing is deleted
Payment past due — the first failed payment of a renewal	The tenant administrator	The plan stays while payment is retried, and how long there is to update the payment method before changes to the account are locked — once per failed-payment episode, not per retry
Subscription ended — the subscription was cancelled, or payment was not received within the retry window	The tenant administrator	Why it ended, and that the account is lapsed: licences and API traffic keep working, changes are locked until the tenant subscribes again
Entitlement activated	The customer contact	The grant is live
Entitlement expiring	The customer contact	Warning before expiry — weekly from 30 days before, daily in the final week
Trial expiring	The customer contact	Warning before a trial ends
Activation identity verification — an activation requires it	The activating user	The verification link that completes activation
Activation code ready	The customer contact	The code to redeem
Plan change received	The requester	The request was captured and is awaiting review
Plan change decision	The requester	Approved or rejected, with the reviewer’s note
Usage-limit notification — a quota threshold is reached	The customer contact	Usage crossed a plan threshold
Feedback reviewed — an administrator decides on in-app feedback, and the tenant has switched on Email the sender when you review their feedback on the Feedback page (off until switched on)	The person who sent the feedback	The decision on their report

Recipients fall into three groups: the customer contact on the entitlement’s organization, the requester of a specific action — which includes the end user who sent feedback — and the account address of the user themselves.