Google connections
Your business. Your account. Your permission.
Shoyu Solutions is preparing a shared authorization service for business websites. New shared-platform connections are not yet open. Existing client Google connections keep working in their current application.
How connection will work
- A business administrator selects a specific feature in its private website workspace.
- The workspace explains the Google permissions that feature needs and identifies the business and expected account.
- Google displays its consent screen. The account holder chooses the account and permissions.
- The server checks that the authorized account matches the intended business connection and stores credentials in that business’s isolated server-side record.
- The workspace shows the connected account, granted features, and a disconnect control.
Permissions by feature
| Feature | Permission | Use |
|---|---|---|
| Account identity | OpenID and email | Identify the account authorizing the connection. |
| Send a message | gmail.send | Send only messages the business chooses to send. |
| Search reporting | webmasters.readonly | Read authorized Search Console property performance. |
| Mailbox correspondence | gmail.readonly | Only after a separately enabled workflow, scope review, and any required assessment. |
Google Ads access is not requested for future features. Connecting an account does not launch advertising or grant permission to send an email.
Control and support
You can revoke an app’s access from Google Account permissions. Read our privacy policy for data use, retention, and deletion requests. Contact franklinreitzas@gmail.com for help. Do not send a token or password.