SMTP is the standard protocol for sending emails via mail servers. Many systems use SMTP with a username, password, and TLS. In Central Command, SMTP can serve as the transport for notifications and scheduled PDF or invoice emails — configurable globally or per instance.
The alternative is delivery via Gmail APIs with OAuth. Which variant fits depends on IT policies and sender domains. What matters are correct sender addresses, secure credentials, and traceable error logs when delivery fails.
SMTP is invisible when it works — and blocks workflows when it does not. Schedules and alerts depend on it. Central Command treats SMTP as an infrastructure building block of its automation: configure, test, monitor. This keeps command center processes reliable in their communication as well.
