> For the complete documentation index, see [llms.txt](https://docs.arnica.io/arnica-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arnica.io/arnica-documentation/getting-started/chatops.md).

# ChatOps Integrations

## Arnica Chat Integration <a href="#h_121d1c4e0b" id="h_121d1c4e0b"></a>

Arnica’s chat integration allows you to interact with the Arnica solution directly from your existing collaboration tools such as Slack or Microsoft Teams to complete mitigations, respond to threats, request permissions, and push notifications and alerts to developers without interrupting their normal development process.\
\
Below are some of the primary features that Arnica provides for Slack or Microsoft Teams.

### Arnica Notifications Channel

The Notification channel pushes Arnica notifications directly to your chat, including ingestion and analysis job completion alerts, notifications for when risks are mitigated, or mitigations are reversed. The Arnica notifications channel can also be used to review and grant permissions requests submitted through the self-service permissions bot.

### Arnica Self Service Permissions

An Arnica self-service access provisioning bot will be accessible by typing “/Arnica” into slack or teams which prompts the Arnica permissions window. This window will allow users to request access to a specific org, repo, and permission level. Based on policies set out within Arnica, these requests can be automatically granted, or result in requests being sent to the notifications channel.

### Secret Detection & Mitigation

The Arnica chat bot can be configured to alert developers directly when a hardcoded secret is identified within a code push, allowing them to remove the secret before it becomes a risk. These alerts are triggered in real time, and are sent directly to the responsible developer, alongside other channels (if needed) immediately. They can also include one-click mitigations, or automated mitigations that remove the secret and erase any history of the secret within the merged branch.

### Code Risks

The Arnica chat bot can be configured to alert developers when certain code risks (i.e. SAST, SCA, licenses, IaC, low reputation) are introduced as early as code is pushed to a feature branch. The chat bot allows developers to mark the risks as in progress, dismiss with a justification, or suggest a dismissal.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.arnica.io/arnica-documentation/getting-started/chatops.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.