White label
White label is a dynamic pro_white_labeling category inside the level-0 /all-settings shell. The Settings sidebar separately excludes read-only sessions, and the Pro tree depends on Pro or Enterprise plan state. Returned category IDs and values are project/runtime data and must not be copied between projects.
The pinned API catalogue places email identity and SMTP transport configs under this category. Other branding fields may be returned by a project, but fixed source does not prove a universal inventory or deployed effect. No address, domain, credential, asset, mail job, or provider was accessed.
Email identity and SMTP
The pinned API catalogue defines the following reference controls; returned presence, values, enablement, and dependencies remain runtime state:
| Control | Effect |
|---|---|
| Sender Email Name | Display name recipients see as the sender. |
| Reply-To Email Name | Display name used for replies. |
| Reply-To Email Address | Destination address for recipient replies. |
| Use Default SMTP Account | Selects the project/platform default delivery account instead of custom SMTP. |
| SMTP Host | Custom SMTP server host when the default account is not used. |
| SMTP Username | Custom SMTP account identifier when the default account is not used. |
The same catalogue also defines sender/reply addresses, SMTP password, port, and encryption, with custom SMTP fields dependent on the default-account setting. These are source contracts, not deployed-field or provider-validation proof.
The shared settings editor renders returned text, option, image, color, and password types. Generic text/options are staged until Save and saved sequentially; earlier updates can be accepted before a later failure. Password fields remain credentials even when masked. If a returned image-type config exists, crop confirmation calls saveConfig immediately and can upload without the generic Save sequence. No such action ran.
Sender/reply addresses, customer domains, SMTP hostnames/usernames/passwords, keys, certificates, tokens, and unpublished assets are sensitive and excluded. Mail helpers and jobs consume SMTP settings downstream, but no delivery result is claimed. Re-entry requires immutable serving receipts, placeholder non-routable addresses, credential-free synthetic configs/assets, deny-all provider egress, and every config/upload/mail/plugin effect blocked.
Related guides: Pro settings · Dashboard customization