SurfacesAvailable
Forward the alert. Get the outcome by reply.
Forward a failing-control alert to Dex, or CC Dex on a thread. Dex does the work and replies with the outcome once your rules say it can send. A change that needs a named approver is decided in the app queue or in Slack, and the email carries the link.
An alert in, an outcome back.
Example messages with demo data. A failing-test alert is forwarded.
- You
Forwarded: failing test, required code review is off on three repositories (CC8.1).
- Dex reply
Fixed within policy. Required reviews are on for all three repositories. I read the settings back, attached the evidence to the test, and re-ran it. It passes.
- Dex reply
One more finding needs a named approver. Decide in the app queue: the link is below. Nothing has changed yet.
- Dex notice
Closed after approval. The receipt is in the app thread.
One address for your company
Your company gets its own Dex address. Forward the alert or the auditor's request straight to it.
Only your people
Dex verifies every message and only takes work from members of your organization.
Replies follow your rules
Outbound email is an action like any other, so it goes through your approval policy.
Reply to keep going
Answer the thread to add detail or ask where the fix stands.
Ignores the noise
Out-of-office replies, auto-responders, and mailing lists never start work.
