Slack Integration Guide for Greyball
Overview
Legal doesn’t live in email alone — so neither does Greyball. Integrate Slack to receive legal requests, trigger automated workflows, and keep business stakeholders informed — all directly from your preferred Slack channels:
- Handle legal intake from any Slack channel or DM
- Trigger workflows by mentioning
@Greyballor sending a direct message - Keep business teams in the loop with real-time legal status updates and escalations
Setup Instructions
1. Connect Slack
Option 1: Via Greyball App
1A. Go to Settings → Inbound & Integrations --> Scroll to bottom of page
1B. Click “Connect Slack”
1C. Authorize Greyball to access your Slack workspace
1D. Choose the channels where legal requests should be enabled
NOTE: User and channel access can be updated from the Slack Admin dashboard for your organization at any time (see details below). Channel access and auto-reply settings may also be updated in the Greyball app under Slack Settings.
---
Option 2: Via direct link (NOTE: You must have already created a Greyball workspace in the Greyball app for your domain)
2A. Go to Slack App web link HERE while signed in to Slack (note: if Admin permissions are set, this will require an admin account)
2B. Follow steps to authorize Greyball and choose channels
For more information, see our Slack App Listing here
---
2. Slack Admin Approval
If your workspace requires admin approval for apps, a Slack admin must approve the Greyball app before it can be used:
Steps to approve an app:
2A. Open App Management: In the Slack desktop app, click your workspace name → hover over Tools & settings → click Manage apps
2B. Access App Management Settings: In the left sidebar, click App management settings
2C. Configure Approval Settings (Admins only): Toggle the "Approve apps" setting to control whether apps need admin approval. Optionally require comments for each app request
2D. Manage Requests: Pending app requests will appear in Slackbot DMs or the designated approval channel. Admins can approve or restrict access directly from there
---
3. Manage channel & user access over time
3A. Admins can manage app settings at any point here
----------------
Where IT assistance may be required
1. App Authorization
- When? The Slack workspace has app approval enabled
- Why? Admin-level privileges are required to approve and authorize Greyball
2. Enterprise Grid Settings
- When? If your organization uses Slack Enterprise Grid
- Why? Org-level policies may override individual workspace settings
3. Channel Access
- When? When selecting or modifying private channels
- Why? Admins may need to add Greyball manually to private channels or adjust permissions
4. Security reviews
- When? For high-security environments
- Why? Your IT team may want to conduct a review of Greyball’s Slack scopes and permissions
Tip: Share this documentation with your IT team ahead of time to ensure a smooth rollout.
----------------
Enterprise Grid Considerations
If your organization uses Slack Enterprise Grid, app installations and permissions may be governed at the organization level, not just the workspace level. Key implications:
- Greyball may need to be approved by an Org Admin, even if it was previously approved in another workspace
- Channel selection might be limited based on org-wide policies or security settings
- Slack Enterprise Grid orgs can enforce domain-level OAuth controls, which may delay or block installation if not pre-approved
To ensure success in an Enterprise Grid environment:
- Engage with your Org Admin early
- Request a review and pre-approval of the Greyball Slack app
- Confirm the app’s Slack scopes with IT/security teams