Slack and Teams
Where Proxara shows up in the flow of work.
Updated June 2026
Proxara's daily surface is wherever the team already works. The console holds the proof; Slack, Teams, and email carry the signal. The design constraint behind all three: quiet by default. A compliance leader hears from Proxara when something would genuinely concern them, at a threshold the firm sets, and otherwise gets one digest a day.
Alert cards
When an event crosses the firm's severity threshold, a card arrives in the connected Slack channel or Teams team: severity, employee, AI provider, and a one-sentence narrative of what happened. The card carries three actions, Approve, Escalate, and Dismiss. Each action updates the event and appends a signed row to the firm's audit record, so a decision made in Slack at 9pm carries the same evidentiary weight as one made in the console. Escalation re-posts the event to the channels subscribed to escalations.
The digest
Once a day, at the hour each subscription chooses, one message summarises the day: volume, what was sealed, the severity split, and up to three events worth a look, each with a direct link. One message. The digest exists so that silence the rest of the day is trustworthy rather than worrying.
Asking from the channel
The same questions the console answers are reachable in place. Slack uses the slash command, Teams uses an @proxara mention; the verbs are the same:
| Command | Returns |
|---|---|
summary | The last day in one narrative |
event | One event in full, with its actions |
search | Matching recent events |
band | The employee's pattern as a band and a sentence |
pause / resume | Mute non-critical alerts for an hour, and unmute |
status | System health |
Two postures are worth knowing. Quiet hours per subscription hold non-critical alerts for the morning digest. And neither quiet hours nor pause silences critical events; those page through regardless, by design.
Teams tab
Teams deployments can also pin the console itself as a personal tab, signed in through the Teams identity, so the deep-investigation surface is one click from the conversation where the alert landed.
Email and webhooks
Email subscriptions receive the same alerts and digest, with one-click action links that authenticate statelessly. For internal systems, a webhook subscription delivers each event as JSON to an HTTPS endpoint the firm controls, with an HMAC-SHA256 signature header for authenticity when a secret is configured. Webhooks are delivery, not decisioning: the approve and escalate verbs live in Slack, Teams, email, and the console, where actions write to the signed record.
Configuration
Each subscription sets its own severity floor (medium by default), quiet hours and timezone, digest hour, and which of alerts, daily digest, and weekly digest it receives. Connecting Slack is an OAuth install; tokens are stored encrypted. Teams connects through the standard bot registration, and the trial demo keeps integrations off unless the operator enables them for a session.