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.
| 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 |
| 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 |
| 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 | 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.