Gmail OAuth allows applications to send emails on behalf of a Google account without permanently storing the actual account password. Instead, tokens are obtained through a consent process. Central Command can use this route as its mail transport when Google Workspace or Gmail is intended.
The advantage lies in controlled permissions and revocable access. Redirect URIs, client IDs, and secrets must be set correctly. After the connect flow, the app stores the refresh information securely. If problems occur, signing in again or rotating the token helps.
Compared to SMTP, OAuth is modern and often more policy-friendly, but dependent on the Google configuration. Teams choose the transport that fits their IT landscape. For schedules and notifications, what matters most is that the delivery channel is stable and documented — Gmail OAuth is a solid option in the Central Command backend.
