Complete step-by-step guide for setting up Slack Channel Manager with Slack Enterprise Grid, including screenshots.
- Slack Enterprise Grid organization
- Organization Admin permissions
- Node.js 18+ installed
Recommended: Use the guided setup wizard:
npm run setupChoose "Create new app" and follow the interactive prompts.
-
Start the setup wizard:
npm run setup
Choose "Create new app" → "Yes" to open browser
-
- Click "From scratch"
-
- App Name:
Slack Channel Manager Enterprise - Select any workspace in your Enterprise Grid
- Click "Create App"
- App Name:
-
- Note the sidebar options
-
- Click "OAuth & Permissions" in sidebar
-
Add bot scopes:
Add these to "Bot Token Scopes":channels:readchannels:historychannels:managegroups:readgroups:historygroups:write
- Add redirect URL:
- In "Redirect URLs" section
- Add:
https://slack.com/oauth/callback - Click "Save URLs"
-
- Click "Manage Distribution" in sidebar
-
- Enable "Org-Wide App Installation"
-
Complete distribution requirements:

- Complete any required sections
- You can skip "Activate Public Distribution" for internal use
-
Return to OAuth & Permissions:

- Should now see "Install to Organization" button
-
Install to organization:
- Click "Install to Organization" (NOT workspace)
-
- Review permissions
- Click "Allow"
-
- Copy the "Bot User OAuth Token" (starts with
xoxb-)
- Copy the "Bot User OAuth Token" (starts with
-
Paste in setup wizard:
- Return to terminal and paste token
- Complete workspace selection
-
First test run:
- Run
npm startto test
- Run
✅ App created with correct name
✅ Bot scopes added (not user scopes)
✅ Redirect URL configured
✅ Org-wide installation enabled
✅ Installed to organization (not workspace)
✅ Bot token obtained and configured
✅ Multiple workspaces discovered
✅ Test run shows channel analysis
- Ensure redirect URL is set correctly
- Try uninstalling and reinstalling the app
- Make sure scopes are added to "Bot Token Scopes" (not "User Token Scopes")
- Verify organization-level installation (not workspace-level)
- Check that org-wide installation is enabled
- Normal behavior for private channels
- Tool uses conservative rules for inaccessible channels
All setup screenshots are stored in docs/screenshots/ and referenced in this guide.
To add your own screenshots:
- Save screenshots with descriptive names
- Place in
docs/screenshots/folder - Update this guide with references
- Use
git add docs/screenshots/specific-file.pngto include them
After successful setup:
- Run channel analysis:
npm start - Customize archiving rules:
npm start -- --max-members-inactive 5 - Add more workspaces:
npm run setup→ "Add/remove workspaces"







