Slack
Run the whole vendor review from the channel that already owns it. Requests arrive as messages, approvals happen in the thread, and every click writes straight back to the review record — no tab switch, no second audit trail.
- Category
- Communication
- Auth method
- OAuth 2.0
- Direction
- Two-way
- Sync frequency
- Real time
- Scopes requested
- 6
- Available on
- All plans
- Maintained by
- Urengi
- of Urengi workspaces install it
- 82%
- median time to connect
- 2 min
- scopes requested, none optional
- 6
- vendor records stored in Slack
- 0
What the Slack integration does
Three jobs, all of them things your team currently does by hand in a DM.
Intake from a slash command
/urengi review datadog opens the intake form in-channel. Four questions — data, users, systems, spend — and the request routes itself to the reviewer who owns that category.
Approvals in the thread
Tier decisions, evidence requests and exceptions get approved where the conversation already happened. Every click lands in the audit log with the approver and a timestamp.
Chase reminders that stop
Urengi nudges the vendor and the internal owner on a schedule you set, then goes quiet the moment the evidence arrives. Nobody has to remember to follow up.
The whole review, in one thread
This is a real request as your reviewers see it — nothing to click through to.
#vendor-reviews · 14 members · IT, Security, Procurement
UrengiAPP10:42
New review request — Datadog
Requested by J. Kim · Observability · $48.2k / yr
4 sub-processors · SOC 2 Type II on file · last reviewed Mar 2025
R. Patel10:44
Approved Tier 2 — renewal review set for 12 Jan 2027
Written back to review #4,182 · audit entry a91f7c2e
Chase queue
- DatadogSOC 2 reportin 2 days
- Twiliosub-processor listin 5 days
- Oktapen test summarysent 1d ago
- SnowflakeDPA countersignin 9 days
Exactly what Urengi can see
Six scopes, listed in full before you authorise. Revoke any of them from Slack at any time.
Urengi reads
- Channel names it has been invited to
- Display names and work emails
- Slash command payloads
- Message timestamps on its own posts
Urengi writes
- Review request messages
- Approval and rejection confirmations
- Reminder DMs to vendor owners
- A Monday digest to #vendor-reviews
Urengi never touches
- Message history in any other channel
- Files, uploads or shared links
- Direct messages between your team
- Anything after you revoke the token
Connect it in four steps
One admin approval, one channel, and a test request you send to yourself.
01
Add Urengi to Slack
Install from the Slack App Directory, or hit Connect at the top of this page. A workspace admin approves the six scopes once.
02
Pick the channel
Choose where requests land. Most teams run a single #vendor-reviews channel; larger orgs route by category to one channel per reviewer group.
03
Map your reviewers
Match Slack users to Urengi reviewer roles. Urengi suggests matches by work email, so a 20-person team takes about a minute.
04
Send a test review
Fire a request at yourself and approve it. The audit entry confirms routing works before a real vendor ever sees a message.
Your token, your rules.
Urengi stores the Slack token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Slack and every Urengi write stops within seconds — the audit log keeps the history, the connection simply ends.
Read the security statement- SOC 2 Type II
- audited annually
- Per-tenant keys
- no shared secrets
- Revocable in Slack
- one click, no ticket
- EU or US residency
- chosen at signup