...
Go to JEMH Cloud → Messaging → Message Outbounds → Click the Create button.
In the Create Message Source screen enter a Name and select the Type SMTP GMAIL OAuth
Click on the Authorize link. This will take you to the Google confirmation screen.
Select the email account that you want JEMHC to be able to access.
Once accepted, close the tab and go back to JEMH Cloud.
The Message Outbound should appear authorised. The Username should be automatically filled. If not, enter the same email address as the selected account.
Submit the configuration. Once the configuration is tested, the connection will be created.
Troubleshooting
Why re-authorization is required
See Refresh token expiry for more reasons:
The user has revoked your app's access.
The refresh token has not been used for six months.
The user changed passwords and the refresh token contains Gmail scopes.
The user account has exceeded a maximum number of granted (live) refresh tokens.
If an admin set any of the services requested in your app's scopes to Restricted (the error is
admin_policy_enforced).For Google Cloud Platform APIs - the session length set by the admin could have been exceeded.
Denied authorization
During OAuth ‘authorization' its possible to get denied (below) typically this means that the account used is not a GSuite account (app not going through Verification for public use are disabled for ‘free’ accounts). To resolve this, create an ‘incognito’ browser session, login only to Jira, then follow the authorization flow.
...