Prerequisites
- Unbound account with Admin role
- Slack workspace where you have permission to install apps
Setup
- Go to Settings → Integrations in the Unbound dashboard
- Find Slack and click Connect
- Complete the Slack OAuth flow to authorize the Unbound app for your workspace
- Once authorized, the Slack card shows Connected to followed by your workspace name
How the Approval Flow Works
When an agent triggers a Require Slack Approval policy:- The tool call is held in a pending state
- A Slack DM is sent to the developer who owns the AI tool, matched by email address
- The DM shows the matched policy, the command preview, and three action buttons:
- Allow Once — approves this specific request (valid for 10 minutes)
- Allow 1 hour — approves all matching commands from this tool for 60 minutes
- Deny Once — rejects this specific request (the denial is also remembered for 10 minutes)
- The agent receives the decision and either proceeds or surfaces the denial to the user
If the developer cannot be reached on Slack (no Slack account with the same email, or the DM fails), the request goes to one org admin instead, and the agent tells the developer who to ask. If no admin can be reached either, the request is denied. By default the request goes to the developer who ran the command, and whoever receives it can approve or deny it.
Creating a Require Slack Approval Policy
- Go to Policies → Agentic Use and click Create Policy
- Select Terminal Commands or MCP Actions
- Configure the command family or MCP tool to monitor
- Set Action to Require Slack Approval
- Optionally scope to specific user groups or AI tools
- Click Create Policy
Tool Policies
Configure the Require Slack Approval action
CLI Policy Management
Create Slack approval policies from the terminal

