Overview
ChangeBreeze integrates with Microsoft Teams to send automated notifications about change management activities. The system supports both organisation-wide monitoring and company-specific notifications through webhook configurations.
How It Works
Two-Tier Webhook System
Organisation-Wide Webhooks:
- Configured at the organisation level
- Fire automatically for all changes across all companies
- Hidden from users - operate in the background
- Perfect for centralized monitoring and compliance tracking
- Support default configurations per change type (Standard, Normal, Emergency, or All)
Company-Specific Webhooks:
- Configured per company
- Optional - users can select them when creating changes
- Visible in change form dropdown
- Allow teams to route notifications to their specific channels
Notification Flow
When a change event occurs (created, approved, started, completed, etc.):
1. Org-Wide Webhooks Fire First
- System finds all active org-wide webhooks matching the change type
- Sends notifications to each webhook automatically
- Logged as "Organisation-Wide webhook: [name]"
2. Company Webhook Fires (If Selected)
- If user selected a company webhook on the change form, it fires too
- If no webhook selected, only org-wide webhooks fire
3. Deduplication
- If the same webhook appears in both lists, it only fires once
- Prevents duplicate notifications
Change Form Behavior
Users see a Teams webhook dropdown with:
Use org defaults only (default selection) - Only org-wide webhooks fire
Company webhook options - Org-wide webhooks + selected company webhook fire
