docs: CRM status changes and detection configs

[NikitaVr]

Knowledge Update: CRM status changes and detection configs

This PR was automatically generated from a knowledge base update.

Changes

• Detections (concepts/detections.mdx): Added clarification about which CRM status changes automatically affect threat detection configurations

Knowledge Entry

Topic: CRM status changes and detection configs
Added by: maksym@chainpatrol.io
Date: 2026-05-26

Content:

Currently, changes to the organization's priority in the CRM is the only thing that automatically adjusts threat detection configs. Other CRM changes (e.g., moving an account from Active to Trial subscription status) do not automatically adjust detection configurations or other org settings.

Original Message

update knowledge, currently changes to the organization priority in the CRM is the only thing that’s adjusting threat detection configs automatically

---

Auto-generated by the ChainPatrol Knowledge Agent

---

Note

Low Risk
Documentation-only change with no runtime, security, or data-handling impact.

Overview
Adds a Configuration section to the detections concept doc explaining how detection sources are set up and which CRM-driven updates apply automatically.

The new Info callout states that only organization priority changes in the CRM auto-adjust threat detection configs; other CRM updates (e.g. Active → Trial) do not change detection settings or other org configuration. It also directs readers to ChainPatrol for custom detection changes.

Fixes a minor formatting issue in Key Takeaways (deduplication bullet indentation).

^{Reviewed by Cursor Bugbot for commit b31b16d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
chainpatrol	🔴 Failed	–	May 26, 2026, 3:26 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.