For the complete documentation index, see llms.txt. This page is also available as Markdown.

Slack

Overview

Arnica's Slack bot feature creates a connection between Arnica, Slack, and your integrated source code management systems providing users with a streamlined process for requesting access and receiving Arnica event alerts.\

Integrating with Slack

The Slack integration can be setup within the Integrations page in the Admin section. After beginning the integration, access must be permitted to allow Arnica to communicate with Slack.

Based on your permissions to install Slack apps, this will create a new Slack channel where all notifications and permission requests will be handled.

Operational guidance

Alerts are not arriving after integration

Slack integration creates the communication channel, but alerts are sent only when matching policy rules include Slack/ChatOps actions.

  1. Verify the relevant Code Risks or Secrets policy includes a notification action.

  2. Confirm the configured recipients (user lookup, specific users, or channels) are correct.

  3. Confirm the arnica bot is added to the target private channel.

Reducing notification volume

If developers receive too many low-priority alerts, tighten the policy conditions:

  • Add a severity threshold (for example, High and above).

  • Scope rules by repository, product, or finding type.

  • Route informational alerts to a shared security channel instead of direct messages.

External collaborators in Slack

For external users who cannot be resolved as direct recipients, route notifications to a shared channel that includes those collaborators.

Last updated

Was this helpful?