Slack
Connect Slack so Kadryn alerts, digests, reviews, and activation workflows reach the right channel reliably.
What this tab is for
Slack is the operational destination for Kadryn notifications. Use it to connect a workspace, choose the default channel, verify health, and route alerts, digests, recommendations, and activation reviews.
Connection model
Kadryn stores Slack installation metadata and encrypted tokens server-side. The application should refresh Slack credentials before they expire and retry recoverable delivery failures with a fresh token.
Users should not have to reconnect Slack regularly. Reconnection should be required only when authorization is revoked, the app is removed from Slack, required scopes change, or the workspace intentionally reinstalls the app.
Setup checklist
- Connect Slack from an account allowed to install apps in the Slack workspace.
- Confirm the Slack workspace name and connected status.
- Choose a default channel for Kadryn notifications.
- Send a test or trigger a low-risk notification flow.
- Check that the channel receives the message and that the integration remains connected.
Channel guidance
Use a channel that has a clear owner. For production alerts, avoid personal channels and ad hoc test channels. For finance digests, use a channel where finance and platform owners can both review cost context.
Troubleshooting
- Not connected: reconnect Slack from an admin account.
- Connected but no channel: select a default channel.
- Message not delivered: check channel access, app permissions, and whether the Slack app was removed.
- Frequent reconnect requests: review token refresh health and installation status.
- Wrong audience: update the default channel or the product workflow that sends the message.
Security notes
Slack tokens must never be copied into client-side code, documentation, tickets, or browser logs. Treat Slack delivery as a server-side integration with audit-friendly status and retry behavior.