SurfacesAvailable
Approve the fix in the Slack thread.
When a compliance fix needs a named approver, the request lands in Slack with the control, the change, and the reason it is sensitive. Approve or deny it there, and Dex finishes the fix in the same thread and posts the closure.
A sensitive fix, decided in the thread.
Example thread with demo data. Control CC6.3 is failing.
- Dex
Approval needed. Remove two production admin grants from a departed contractor. Control CC6.3. Sensitive change, so it waits for a named approver.
- Priya Shah
Approves, with the reason: contractor ended on 9/30.
- Dex
Removed. I read the grants back and none remain. Evidence is attached to the test, and the test re-run passes.
- Dex
CC6.3 is closed. The receipt is in the app thread.
Approve or deny where the team already is
The Slack decision is recorded with the approver, the reason, and the result.
Status when someone asks
Tag @Dex in any channel or DM to ask where a failing control stands or to hand it a new one.
Only the approver decides
A change waits for its named approver. Low-risk changes run within your written policy, and out-of-authority actions are not run.
The same rules as everywhere
Slack requests use the app's context, connections, and approval policy. Adding Dex to Slack does not create a connection for reading other Slack resources.
Questions from other work
Dex reads the thread and the files in it, so a question about an account gets an answer in place.
