Gmail or Google Workspace can be connected so supported Ellich operational messages use the business mailbox your team already manages. This is a shared business-email feature for authorized organizations and locations. Availability follows the current service configuration and the organization's email access. The connection uses Google's secure sign-in page; Ellich does not ask for or store the mailbox's normal password.
Choose the company or location scope
Open Admin / Communications / Email. Under Connect Business Email, choose the scope before selecting Connect Google:
- Company default supplies the sender for every location that does not have its own override.
- This location supplies the sender only for the current location and takes priority over the company default there.
Confirm the company and current location shown at the top of the page. If the Google option is disabled, Ellich's Google connection has not been enabled in that environment. Do not replace a working sender or share account details with support while the option is unavailable.
Authorize the mailbox safely
Select Connect Google, sign in on Google's page, and choose the mailbox that should send business messages. Review the requested permission to send mail before approving. This provider sign-in is sometimes called OAuth; it does not require an app password.
Ellich requests OpenID and email permissions to identify the selected account. It receives the account identity, granted permissions and authorization credentials, and stores the credentials encrypted to send the business's transactional email. The Gmail permission is gmail.send; this connection does not request access to read or search your inbox, manage contacts or delete mailbox messages. See the Privacy Notice before authorizing.
If Google displays Google hasn't verified this app, the developer's Google application review is incomplete. Do not treat that warning as a problem with your mailbox or repeatedly reconnect. Ellich must complete the applicable verification for wider release. A Workspace administrator's separate connected-app policy can also restrict access.
Use a mailbox that the business controls and expects to keep active. A Google Workspace administrator may need to allow the Ellich application under the organization's connected-app policy. Do not work around an administrator block by connecting a personal Gmail account.
After returning to Ellich, review the sender and reply-to address. The reply-to address should be a monitored business inbox because customer replies go there. Connecting Google does not change MX records or nameservers. Keep the domain's SPF, DKIM, and DMARC settings under the control of the Google Workspace or domain administrator.
Send the required test
Enter an approved Test recipient and select Send test. The connection is not ready until the test succeeds. Accepted means Google received the message from Ellich; it does not prove that the message reached the inbox. Check the destination inbox and spam folder, then review Recent email activity for later delivery evidence when available.
If sending is paused or the service displays an allowed-recipient restriction, resolve that stated condition before testing. Do not repeatedly send the same message after an ambiguous result. Connection testing does not activate or replace the company's or location's sending route; confirm the intended sender before explicitly activating it.
Disconnect or revoke access
Select Disconnect beside the connected sender when the mailbox should no longer be used. Disconnect removes this Ellich connection: it disables its sending routes and clears its active stored authorization credentials. It does not itself remove the Google Account's authorization. You can separately review or remove Ellich's access in Google Account or Workspace connected-app settings. Removing Google account access may affect other Ellich connections for the same Google account, so review that broader effect before proceeding. Confirm whether the location now inherits a company default or shows no sender.
Existing messages, recipient and delivery records, audit events and connection metadata are not all erased by Disconnect. Active credential removal does not delete every backup copy. For a privacy or deletion request, use the privacy contact in the Privacy Notice, identify the business and connected mailbox, and describe the records or connection concerned. We verify the requester's identity and authority before reviewing remaining records and any merchant instructions or retention requirements. Disconnect is not an automatic complete-deletion request. Do not send passwords or authorization tokens.
For legacy sender controls, domain details, and recipient blocks, see Configure and test outbound email. Never include sign-in codes, account recovery information, or authorization links in a support request.