Drop the Tech Ringer AI app into your workspace. Run safe AI agents from slash commands, channel mentions, or DMs — with the audit log your security team will actually like.
Four steps. Defaults are conservative — you can broaden later.
Click 'Add to Slack' from your Tech Ringer AI workspace settings. The OAuth consent screen shows exactly the minimal scope set listed below.
A workspace admin approves once. The bot doesn't request `chat:write.public` by default — it only posts in channels it's been added to.
Pick which channels the bot can listen in and which user actions are allowed (read vs write per tool). Defaults are conservative.
Try `/techringer help` in any channel where the bot is present. Mentions and DMs also work.
OAuth scopes requested
chat:writechannels:readchannels:joinchannels:historygroups:readusers:readcommandsim:writeim:historyreactions:write/techringer summarize this threadPosts a sanitized summary of the active thread to the channel, with PII redacted in the summary and the original thread reference logged.
Slack workspaces install bots at the workspace level, which means a single approval governs everyone in that workspace. We treat that as a responsibility, not a shortcut: every tool action the agent takes gets logged with the requesting user's Slack ID, every PII redaction event flows into the parent audit log, and capability gating runs per-user even though the install is workspace-wide.
We've also kept the OAuth scope set deliberately minimal. The bot reads thread context only when it's invoked, never proactively polls channels, and never requests `chat:write.public` (the scope that lets bots post into channels they haven't been added to). If you need that, it's opt-in per workspace — and it's logged when toggled.
Slack is the platform where most teams pilot Tech Ringer AI first. The combination of fast time-to-value (under five minutes from install to first summary), genuinely-minimal scopes, and the audit log most security teams already want is what makes Slack the right starter integration.
Yes. Enterprise Grid workspaces install the bot at the workspace level (not org level), so each workspace gets its own configuration, audit log, and capability gates. If you want consolidated billing or shared workflows across Grid workspaces, contact us — we'll set that up.
The OAuth grant is revoked immediately. All in-flight agent sessions stop. Past audit log activity stays accessible from your Tech Ringer AI dashboard. Reinstalling restores access but doesn't replay past actions.
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.