Google Workspace uses a Personal connection. Each Stackyapper user connects
their own Google Workspace account and chooses the Google capabilities that
Stackyapper may use. Connecting one account does not authorize an entire Google
Workspace tenant or any other Google account.
Google Workspace is currently a Beta app. Start with the smallest read-only
permission needed for a real workflow, then confirm the first call in
Audit.
Connect an account
In the Stackyapper portal, open Apps.
Find Google Workspace and choose Connect account. If you already have
a connection, choose Manage accounts instead.
Choose Add Google account.
Select the Calendar, Drive metadata, Gmail, Chat, or Workspace Directory
access needed for this account.
Review the Google-data notice, choose Continue with Google, and select
the intended Google Workspace account at Google.
Review Google's consent screen and approve the requested access.
Stackyapper stores the resulting OAuth grant encrypted. It never asks you to
paste a Google password or token into the portal. Consumer Gmail accounts are
not supported in this release.
Use more than one Google account
Choose Add Google account again for each additional Workspace account. Give
each connection a name that makes its purpose clear. If more than one connected
account can run a requested tool, the request must identify the intended
connection; Stackyapper does not silently choose a different account.
Change permissions
Choose Reconnect beside an account to add an available permission. Existing
permissions remain selected during reconnect so a stale browser cannot silently
reduce or replace the stored permission boundary. To remove access, disconnect
the account and connect it again with the smaller set.
Disconnect and delete connected-account data
Open Apps and select Google Workspace.
Choose Manage accounts.
Find the exact account and choose Disconnect.
Confirm the account shown in the dialog.
Disconnecting removes the selected Stackyapper account connection and its
encrypted local grant, and removes access to that connection's Google tools.
Stackyapper asks Google to revoke the underlying authorization after the last
Stackyapper connection using that Google account is removed. If you want to
revoke Stackyapper immediately across every connection using that Google
account, remove Stackyapper from your Google Account's third-party access page;
those remaining connections will stop working. Disconnecting does not delete
email, events, files, Chat messages, or Directory records in Google. It also
cannot delete copies already returned to an AI client or workflow you selected;
that destination controls its own retention and deletion.
Stackyapper keeps bounded operational audit metadata for the period described in
the Privacy Policy. Standard tool-call logs do
not retain Google message, event, file, Chat, or Directory content. Contract,
security, and audit records may remain when legally or operationally required.
To request access to or deletion of personal data that remains in Stackyapper,
email legal@stackyapper.dev. Include the
Stackyapper workspace and connected-account label, but never send a password,
authorization code, token, message content, or provider response.
If the account needs attention
Reconnect when Google has revoked the grant, the grant has expired, or a needed
permission is missing. If the account or Workspace domain shown in the portal is
not the one you intended, disconnect it instead of reconnecting it.
Google Workspace administrator permissions should be connected only by an
owner or admin using an account authorized for the intended Workspace domain.