Notifications
What notification integrations do
Notification integrations push project activity into external team channels. They are for awareness and coordination, not for bringing evidence into Colabra.
Use them when you want deal activity to appear where the team already communicates:
- new updates
- project activity
- workflow progress
- alerts worth surfacing in a shared channel
The right mental model is ambient visibility. A notification tells people that something changed. The actual work, evidence review, and decision trail should still live back in Colabra.
The internal deal channel stays in the loop
Real deal example: faster awareness without moving the audit trail
A deal lead wants the private channel to see that new findings landed overnight and that several requests were answered. Slack or Teams is the right place for that signal. The formal comments, request resolution, and evidence review still happen inside the project, where the context is preserved.
Compare the notification tools
| Provider | Best for |
|---|---|
 Slack | Teams already running day-to-day diligence communication in Slack |
 Microsoft Teams | Organizations standardized on Microsoft 365 collaboration |
Good operating pattern
- Notify the internal working channel, not a broad company channel.
- Treat notifications as prompts to review Colabra, not as the place to resolve diligence items.
- Keep final judgement in task comments, findings, and request threads so the audit trail stays attached to evidence.
What they do not replace
Notifications do not replace:
- External requests for formal asks and responses
- Cloud storage for evidence import
- Webhooks for system-to-system automation