Notifications
Clear all
Topic starter
25/06/2026 1:06 am
TL;DR: Connecting AI agents to Slack through OAuth 2 gives them delegated access to send messages, read channels, and act on behalf of users, according to Frontegg. The real governance issue is not connectivity, but how identity teams constrain tool scopes, token lifecycle, and least privilege when agents operate inside user tools.
NHIMG editorial — based on content published by Frontegg: Learn how to integrate Slack into your AI agent using Frontegg's identity infrastructure
By the numbers:
- Only 5.7% of organisations have full visibility into their service accounts.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job.
Questions worth separating out
Q: How should security teams govern AI agents that connect to Slack through OAuth?
A: Security teams should govern Slack-connected AI agents as delegated identities, not as ordinary app integrations.
Q: Why do AI agents complicate least-privilege access in collaboration tools?
A: AI agents complicate least privilege because their permissions are defined by scopes that can be broader than a single task and may persist through refreshed tokens.
Q: When does Slack OAuth create more risk than it reduces for AI agents?
A: Slack OAuth creates more risk when the agent receives reusable or overly broad scopes for a workflow that does not need them.
Practitioner guidance
- Review every agent-tool OAuth scope set before deployment Approve only the minimum Slack scopes needed for the intended workflow.
- Separate token custody from agent execution Store and refresh delegated tokens in a controlled identity layer rather than inside the agent runtime.
- Treat AI agents as governed identities in access reviews Add agent-enabled Slack integrations to IAM and lifecycle review cycles.
What's in the full article
Frontegg's full guide covers the operational detail this post intentionally leaves for the source:
- Step-by-step Slack app registration and redirect URI setup for the OAuth flow.
- Exact tool configuration fields inside the Frontegg dashboard, including client ID and client secret handling.
- Capability-to-scope mapping examples for Slack actions such as channels:read and chat:write.
- Sample app testing flow for verifying token exchange and message-sending behaviour.
👉 Read Frontegg's guide to connecting Slack to an AI agent with OAuth 2 →
Slack OAuth for AI agents: are your controls keeping up?
Explore further
25/06/2026 10:17 am
Delegated tool access is now an identity governance problem, not just an app integration pattern. The article shows the standard OAuth shape for connecting Slack to an AI agent, but the governance question is who can authorise that access, how scopes are bounded, and how long the token remains valid. That places AI agent access squarely inside IAM, PAM, and lifecycle governance rather than leaving it to application teams alone. Practitioners should treat tool-connected agents as governed identities with explicit approval and review paths.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
- Another finding from the same survey shows that 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job.
A question worth separating out:
Q: What should IAM teams review after an AI agent is granted access to Slack?
A: IAM teams should review the approved scopes, token custody model, refresh behaviour, and revocation process. They should also confirm who owns the integration, what business action it supports, and whether the agent’s Slack privileges still match the current workflow. If the answer is unclear, the access model is already too loose.
👉 Read our full editorial: Slack OAuth for AI agents exposes the identity governance gap
