You may not be signed in to ISMS Copilot. Open the app in a new tab, sign in, then return to Connectors and try again. The authorization flow requires an authenticated session.
How to connect Slack to ISMS Copilot
Overview
Connect Slack to ISMS Copilot to ask compliance questions directly from your Slack workspace without switching to the app. Once connected, you can message ISMS Copilot in Slack channels using mentions or direct messages to get framework-specific guidance, policy help, and compliance answers.
Who This Is For
This guide is for:
Organization owners setting up ISMS Copilot for their team
Compliance teams who want AI assistance without leaving Slack
Security professionals integrating ISMS Copilot into their existing Slack workflows
Prerequisites
Paid plan: Slack integration requires a paid subscription. Free-tier accounts cannot connect Slack.
Organization owner role: Only organization owners can manage integrations. If you're a team member, ask your organization owner to set up the connection.
Slack workspace admin access: You'll need permission to install apps in your Slack workspace during the authorization step.
ISMS Copilot account: You must be signed in to complete the setup. The flow will show an error if you're not authenticated.
How to Connect Slack
Step 1: Open Connectors
Go to Connectors in the ISMS Copilot sidebar, or navigate directly to /connectors in your browser. This page shows all available integrations for your organization.
Step 2: Start Slack Authorization
Click Add to Slack. This opens Slack's authorization flow in a new window.
Step 3: Authorize in Slack
Select your Slack workspace from the dropdown
Review the permissions ISMS Copilot requests
Click Allow to grant access
Step 4: Verify the Connection
After authorization, you'll see a success message: Slack workspace connected. The Connectors page updates to show your connected workspace name and a Disconnect action.
Connection confirmed: If you see your workspace name displayed, the integration is active. You can now use ISMS Copilot in Slack immediately.
For detailed guidance on using ISMS Copilot in Slack—including thread behavior and best practices—see Use ISMS Copilot in Slack.
Using ISMS Copilot in Slack
Once connected, interact with ISMS Copilot from Slack:
Channel mentions: Type
@heygrcfollowed by your question in any channel where the app is installedDirect messages: Open a DM with @heygrc for private conversations
Questions work the same as in the web app—be specific about frameworks and controls for best results:
@heygrc What controls does ISO 27001 A.8.1 require for asset management?How to Disconnect Slack
If you no longer need the Slack integration:
Go to Connectors in ISMS Copilot
Click Disconnect next to your Slack workspace
Confirm when prompted with Disconnect Slack?
After confirming, you'll see: Slack workspace disconnected. The integration is removed and ISMS Copilot will no longer respond in Slack.
Disconnect removes the integration: Disconnecting deletes the connection entirely. You can reconnect later by repeating the setup steps.
Troubleshooting
I clicked Add to Slack but nothing happened
I got an authentication error during setup
If you see Authentication failed. Please try again., the OAuth flow couldn't complete. This usually happens when your ISMS Copilot session expired. Sign in again and repeat the authorization.
I don't see the Disconnect option
Only organization owners can disconnect integrations. If you're a team member who needs the integration removed, contact your organization owner.
ISMS Copilot isn't responding in Slack
Verify the connection shows as active on the Connectors page. If it shows your workspace name, the integration is connected. If Slack shows errors when mentioning the bot, try disconnecting and reconnecting.
What's Next
Organizing Work with Workspaces - Set up separate workspaces for different frameworks or clients
Use Teams and shared workspaces - Understand organization-level access and collaboration
Starting Your First Conversation - Learn how to ask effective questions for better responses