Add Tech Ringer AI to your Google Workspace. Spaces, DMs, slash commands — all with capability gating, PII redaction, and a Workspace-admin-friendly audit log.
Four steps. Defaults are conservative — you can broaden later.
A Workspace admin installs Tech Ringer AI from the Marketplace and approves the OAuth scope set (listed in the consent flow).
Users add the Tech Ringer AI app to spaces or start a DM with it. Per-space configuration is set by the Workspace admin.
Read access to connected Google services (Gmail, Drive, Calendar) is the default. Write actions stay off until explicitly enabled per user.
Type `@Tech Ringer AI` in any space the app is added to, or DM the app directly.
@Tech Ringer AI draft a reply to the last email in #project-channelThe agent reads the referenced email (capability gating permitting), drafts a response, and posts the draft back to the space for review — never sends without explicit approval.
Google Chat sits inside the Google Workspace trust boundary, where most customers already have strong identity and access controls in place. Our Google Chat integration uses Workspace-scoped OAuth, so the same admin who controls Gmail and Drive controls the AI agent's reach — no separate identity layer to manage.
The integration plays especially well when the agent needs Google Workspace tools (Gmail, Drive, Calendar, Docs). Because the Workspace admin has already vetted the OAuth scopes, the AI's tool catalog mirrors what users already have access to — capability gating is just a finer-grained filter on top.
We also kept the Chat scope set narrow: the bot reads space messages only when invoked, never proactively polls, and never requests cross-space access. If your Workspace policy requires least-privilege bots, this configuration is what we ship by default.
Yes — Google Chat itself requires Workspace. Personal Google accounts can't host third-party Chat apps. If you're using Tech Ringer AI personally with a Gmail account, the dashboard chat or Telegram/Discord might be a better fit.
Yes. Per-user capability gating works alongside Google Workspace's OU-based admin policies. You can set 'engineering org can use write tools, sales org can only read' via the Tech Ringer AI dashboard, and it composes with Workspace's existing scope controls.
No. We don't train models on customer conversations — across every plan, every audience, every chat platform. PII is also redacted before any third-party LLM provider sees a tool result.
Yes. Input guardrails, URL safety scanning, PII redaction, capability gating, and audit logs run identically here as in the dashboard and on every other integration. Adding a chat platform doesn't expand your security surface area meaningfully.
Disconnect the integration from the dashboard at any time. That revokes the OAuth grant (or removes the bot from the platform, for non-OAuth platforms), all in-flight agent sessions stop, and any future invocations from that platform fail closed. The audit log of past activity stays accessible.
Free to start. $5 in credits on us. No credit card required.