Email alerts
Fixed Dashboard source can render the special Email alerts view for level 0 when plan state requests the Pro tree and a returned email_configs category is selected. This does not prove runtime availability.
Source-defined recipient groups
The special email_configs renderer recognizes Administrator, Business, and Customer config records. It displays options returned for the selected record; fixed client source does not establish that every project returns the same statuses or values.
The exact status list is configured by the project. A status visible in one project is not guaranteed to be available in another.
Status selection is source-traced to operational email eligibility, but it does not prove a recipient address, template, SMTP route, job dispatch, provider delivery, or inbox result. None was accessed or executed here.
Saving and errors
The Dashboard stages edits and, after Save, updates each changed configuration separately. A later failure can follow an earlier accepted update. Accepted config updates can add audit-log records, refresh global config state, and invoke plugin hooks; no request or effect ran here.
This page renders recipient/status configuration. SMTP credentials, sender/reply addresses, templates, actors, customers, orders, and mail-provider state are sensitive and excluded.
If the category is missing
Route level, read-only state, plan state, returned Pro tree, email_configs category enablement, and configs are separate gates. A missing category does not prove a specific entitlement or mail-delivery failure. Re-entry requires immutable receipts and synthetic statuses with all config, job, provider, and delivery effects intercepted.
Related guides: Settings overview · Settings logs