Slack approvals

Install and configure

Open Notifications in the Kastra console. An authorized administrator installs the Slack integration through its OAuth flow, selects an accessible channel, and configures any environment-specific channel overrides. Confirm the workspace and channel before sending a test notification.

Link the approver

Each person who resolves a checkpoint from Slack must link their Slack identity to their Kastra account. Installing the workspace app alone does not establish that human mapping. Direct-message notifications have a separate opt-in setting.

Review a checkpoint

Read the action, policy, expiry, and masked context in the notification. Approve or deny only when the linked Kastra account is authorized. The handler rechecks the relevant membership; a Slack display name is not approval authority.

Inspect the resulting checkpoint in the console to confirm resolution and attribution. Failed delivery and failed authorization are different issues.

Troubleshooting

Check installation status, bot channel access, the selected environment override, and personal account linking. Environment override keys currently use names; renaming an environment can leave an old channel override unmatched. If a notification is stale, inspect the current checkpoint state before acting.

Slack is an approval channel, not an integration that intercepts every chat message or an announcement of a commercial partnership.