Approve in Slack, act for real
Owner-routed Approve/Dismiss buttons in Slack drive the real approval funnel end to end, with the outcome threaded back onto the card — and safety blocks + overrides routed per account.
Approvals that live in yet another dashboard stall. The person who can say yes is in Slack, not your console, so remediations wait days for a click.
Built to do the work, not just show it
Owner-routed cards
The right owner gets an interactive Approve/Dismiss card in Slack.
Real funnel, not a webhook
A click drives the same approval → execution path as the app.
Outcome thread-back
The result is posted back onto the original card.
Per-account routing
Blocks + overrides go to the account’s channel with the account named.
From signal to result
Notify
A pending approval posts to the owner’s Slack channel.
Decide
Approve/Dismiss drives the funnel; server-side authorization is re-derived.
Thread back
The execution outcome updates the card.
- Approve/Dismiss re-derives all authorization server-side from the Slack signature.
- Safety-block cards name the account and offer a single-use "Override & run once".
- Self-service account linking connects a Slack user to their GetFinOps identity.
Questions
Is approving in Slack as safe as the app?
Yes — authorization is re-derived server-side from the signed request; the Slack click just drives the same funnel.
Where do blocks show up?
In the account’s Slack channel, naming the account, with an optional single-use override.