Slack Integration

GovMatrixIQ bridges Slack and Chatter in both directions per channel. One Slack workspace install grants the bot access; you then bind individual Slack channels to individual Chatter channels.

• Outbound (Chatter → Slack) — messages posted in a Chatter channel forward to a bound Slack channel via chat.postMessage using the workspace bot token.
• Inbound (Slack → Chatter) — messages posted in the bound Slack channel land in the matching Chatter channel.

Prerequisites

• Slack workspace admin permission to install apps
• GovMatrixIQ account with admin or owner role on your organization

Step 1. Install the GovMatrixIQ Slack app

1. In GovMatrixIQ, open Settings → Integrations → Slack.
2. Click Install to Slack — redirects to Slack's OAuth consent screen.
3. Pick your workspace, review the scopes (channels:history, chat:write, etc.), click Allow.
4. Slack redirects back to GovMatrixIQ. The bot token is stored per-org in slack_workspaces — one row per workspace install. You'll see a success toast.

Each customer organization installs separately. Tokens are isolated per org_id; cross-tenant access is impossible.

Step 2. Invite the bot to each channel you want bridged

The bot only reads messages from channels it has been explicitly invited to. In Slack, in each target channel:

/invite @GovMatrixIQ

Step 3. Bind the Slack channel to a Chatter channel

1. In GovMatrixIQ, open Chatter.
2. Pick the Chatter channel that should be paired (e.g. #general).
3. In the channel header, click the Bind Slack ch pill → a modal opens.
4. Paste the Slack channel ID (e.g. C0123ABC). Find it: Slack → click the channel name → About → bottom of the panel shows the Channel ID.
5. Click Save.

The pill switches to → C0123ABC. Outbound + inbound routing both use this binding from now on.

Step 4. Enable forwarding per Chatter channel

1. In the same Chatter channel header, click the Slack off pill → confirm the "Not E2E" warning.
2. Pill flips to Slack ON.
3. Post in Chatter → the message appears in the bound Slack channel.
4. Post in the Slack channel → the message appears in Chatter.

Encryption note: Chatter is end-to-end encrypted by default. Forwarded copies travel as plaintext so the message reads correctly in Slack. The Slack channel itself is not E2E, so the net exposure matches what the toggle's warning advertises.

Troubleshooting

Symptom	Cause	Fix
"Slack ON" but messages don't appear in Slack	Channel not bound, OR bot not invited to the bound Slack channel	Verify the Bind Slack ch pill shows the channel ID. Run /invite @GovMatrixIQ in Slack.
Slack messages don't appear in Chatter	Bot not in channel, OR channel ID not bound, OR your Slack user not connected to a platform account	/invite @GovMatrixIQ in Slack. Verify the bind pill. Run /govmatrix connect in Slack.
"Connect first" in Slack even after installing	Workspace install ≠ per-user connect. Each user runs /govmatrix connect once.	Run /govmatrix connect in Slack and complete the OAuth flow.
Install button returns "SLACK_CLIENT_ID missing"	Platform admin hasn't set the OAuth credentials	Set SLACK_CLIENT_ID + SLACK_CLIENT_SECRET on the platform Render service; redeploy.

Security Notes

• Bot tokens are per-workspace + per-org. The Slack OAuth install yields a xoxb- token scoped to that workspace's installation and stored in slack_workspaces.bot_token. Other tenants cannot read or use it.
• Inbound messages are stored unencrypted in Chatter. Slack channels themselves are not E2E, so the net exposure is unchanged.
• The bot subscribes to ALL messages in channels it has been invited to. Make sure your team understands that the bot reads channel messages before adding it.
• Uninstalling. Slack workspace admin can remove the app at any time from Apps → Manage. The bot token is invalidated immediately on uninstall.

Need help?

Email [email protected] or open a ticket from Settings → Support. Include your organization name, the Slack workspace name, and a description of the symptom.