I approved a production deploy from a chat button, then approved my own request
A teammate pings you at 18:50. The fix is ready, production needs a second pair of eyes, and you are on a train with a phone and no laptop. The dashboard works on mobile, but the real question is whether the approval can come to you, as a button in the chat you already have open.
Levelrail, the open source self-hosted platform I work on, has exactly that: Approve and Deny buttons on a Slack or Discord message. I tested it, and the result is more useful for what it showed than for the happy path. I will say plainly which parts I ran, which parts only ever ran against fakes, and where the feature can approve your own request.
TL;DR
| Question | Answer |
|---|---|
| Which chat platforms get buttons? | Slack and Discord only |
| Do other channels (Telegram, Teams, ntfy and so on) get buttons? | No, they get plain notifications |
| Did I test against a real Slack or Discord? | No. I sent signed requests to a real local control plane |
| What decides the approval? | The channel, not a person. Anyone who can click in that channel |
| Can the requester approve their own deploy by chat? | Yes. The docs say so, and my run confirmed it |
What the feature is
A protected environment, such as production, makes a deploy or promotion wait for approval. A different user must approve it, and the person or token that requested it cannot. The usual place to do that is the dashboard's Approvals queue, or the CLI.
Chat approvals add buttons to the message Levelrail already sends to a notification channel when a request comes in. It adds to an existing channel. You connect a Slack or Discord channel the normal way, then turn on interactive approval buttons for that channel. It is off by default. Only a caller with the root ability can turn it on, change the secret or change the webhook URL of a channel that has it on.
Per the docs, setup differs by platform:
Slack. The incoming webhook must belong to a Slack app with Interactivity turned on. You set the Request URL to /api/v1/webhooks/slack/interactions on your Levelrail host and paste the app's signing secret into the channel. Levelrail checks an HMAC-SHA256 signature on every click.
Discord. You set the app's Interactions Endpoint URL to /api/v1/webhooks/discord/interactions on your Levelrail host and paste the app's public key into the channel first, because Discord pings the URL when you save it. Verification is Ed25519.
Neither route takes a session or API token, because neither platform can send one. The signature is the authentication.
What I ran
I did not create a Slack app. I ran a real throwaway control plane on my laptop, created a protected environment, a Slack-kind channel with interactive approvals on, and an app inside that environment. The channel setup has no CLI flag today, so I created it through the API. Then I deployed with the CLI and checked the pending approval:
levelrail-cli apps deploy shop --image localhost:42301/w2c-web:1 --confirm
levelrail-cli deploy-approvals list
deploy of "shop" to image "localhost:42301/w2c-web:1" is pending approval (id apr_XPHz83HNN8cv)
the target environment is protected: a different, sufficiently privileged user must approve it before it deploys.
First, the guard that should hold. Approving as the same token that requested it:
approve deploy approval "apr_XPHz83HNN8cv": server returned 403: the same user or token that requested this deploy cannot approve or reject it; a different privileged user must decide
Good. Then I played Slack myself. Slack posts a form body with a payload field and signs v0:<timestamp>:<body> with the signing secret. Anyone with openssl and curl can reproduce a click:
# LR_URL is your control plane address, SECRET the channel signing secret
BODY="payload=$ENCODED_JSON" # block_actions JSON with action_id and the approval id
TS=$(date +%s)
SIG="v0=$(printf 'v0:%s:%s' "$TS" "$BODY" | openssl dgst -sha256 -hmac "$SECRET" | sed 's/^.* //')"
curl -s -X POST "$LR_URL/api/v1/webhooks/slack/interactions" \
-H "X-Slack-Request-Timestamp: $TS" -H "X-Slack-Signature: $SIG" \
-H 'Content-Type: application/x-www-form-urlencoded' -d "$BODY"
Three results, in order:
A click signed with the wrong secret returned HTTP 401 invalid signature, and the approval stayed pending.
A click signed with the right secret returned 200 and a reply for the chat message:
Approved by Slack:team-slack (clicked by alice). shop now targets localhost:42301/w2c-web:1.
deploy-approvals get then showed status: approved and decided by: Slack:team-slack (clicked by alice). The app's desired state moved to the new image, and a new deploy row appeared.
Sending the same click again returned deploy approval ... is no longer pending (status: approved). A replay cannot decide twice.
Now the catch. My CLI token requested the deploy, and a chat click approved it. The self-approval check that blocked my CLI attempt did not stop the click, because the click is not a person. The docs say this directly: a verified click counts as the channel, the clicker's name gets noted but grants nothing, and anyone in that channel, including the requester, can approve.
How well each piece is tested
This is the part to read before you rely on it. I checked the repo's own status page and the tests.
| Piece | Evidence |
|---|---|
| Dashboard and CLI deploy approvals | Live end-to-end test: two sessions, same-user approval rejected, container untouched until a different user approves. Marked stable |
| Chat approval click handlers (Slack and Discord) | Handler tests that sign requests locally: approve, deny, wrong signature, replay, Discord ping. No end-to-end test, and I found no row for it on the status page |
| Slack and Discord message delivery with buttons | Unit tests cover the payload shapes. I found no record of buttons rendering in a real Slack or Discord workspace, and I did not see them either |
| Webhook and email channels | Live tests against a local receiver and a local SMTP server. Marked stable |
| The 15 vendor channel kinds, Slack and Discord among them | End-to-end tests against local fakes that check each vendor's documented payload and auth header. No real vendor has accepted a send, per the status page |
| Requiring N approvers | Unit tested. The N-approver rule has no end-to-end test |
My own run adds one live data point: the control plane did try to deliver the approval message to the Slack URL I gave it. That URL was a fake webhook path on the real Slack host, and the channel's delivery history shows deploy-approval-requested failed receiver returned status 404. So the send path runs and records its result. It tells you nothing about how the buttons look. I should not have let a fake token reach a real host, and I removed the channel right after.
Where this is a good idea, and where it is not
If your approvers are a small team in one private channel, a button on a phone beats a login. The channel is your trust boundary, and for a handful of people who already trust each other, that is a fair deal.
Skip it when you need separation of duties. The docs say it plainly: for approvals that need true separation, approve only from the dashboard or the CLI, and leave interactive buttons off on every channel. There is no global switch, so it is a per-channel decision to audit. I would also keep the channel small. A channel that includes a bot, a contractor or a client is now a production approval surface.
Telegram, Teams, ntfy, Pushover and the rest can notify you that a request is waiting. None of them carry approve buttons. For those, you get the message, then open the dashboard or run levelrail-cli deploy-approvals approve <id> as a different user.
FAQ
Does this work with Microsoft Teams, Telegram or Mattermost?
Not for buttons. Teams, Telegram and Mattermost are notification kinds only. The code returns an "unsupported" error for any kind other than Slack or Discord.
Is the click tied to a Levelrail user?
No. Levelrail keeps no link between a Slack or Discord user and a Levelrail account. The decision counts as the channel's, with the clicker's chat name noted for visibility.
Can I turn it on from the CLI?
Not today. levelrail-cli channels create has no flag for it, so use the dashboard channel dialog or the API fields interactive_approvals and interactive_secret.
Can a forged request approve a deploy?
Every request is signature-verified against the channel's own secret first, and a bad signature changes nothing. My wrong-secret test returned 401 and left the approval pending. Treat the signing secret like a deploy credential.
Where I landed
Chat approval is a convenience layer on a gate that is itself well tested, and the convenience layer is the less proven half. Before I use it for anything that matters, I want one real Slack workspace to accept a real message with real buttons. Would you accept a channel as the approver, or does your process need a named person on every production deploy?
glincker
/
levelrail
Self-hosted alternative to Vercel and Coolify. Git push, HTTPS, logs, rollback. No Kubernetes.
Levelrail
Your own Vercel, on your own servers.
Push to deploy with HTTPS, logs, metrics and one-step rollback. One Go binary, no Kubernetes. Apache 2.0.
Website · Docs · Install · Compare · FAQ · Roadmap · Discussions
English · 简体中文 · Español · Português (BR) · Deutsch · Français · 日本語
Turn any Linux server into a private cloud: Git deploys, HTTPS, databases with verified backups, metrics, logs and alerts, without Kubernetes and without a monitoring stack to bolt on. Pre-1.0: single-server is production ready, multi-node is beta (Feature status).
idle RAM, 1.5% of one CPU Go control plane, Docker runtime one-click service templates MCP tools for coding agents
200 MB
measured, method included
1 binary
no Kubernetes
360
smoke-tested
240+
scoped, read-only by default
Install
curl -fsSL https://levelrail.com/install.sh | sudo sh
Needs Linux (amd64 or arm64) with systemd and root; the installer adds Docker. Open ports…
If this saved you time, a star on the repo helps others find it.
Sources checked
- Levelrail docs on the v1.0.1 release branch: docs/chat-deploy-approvals.md (setup, endpoints, identity scope warning, root requirement), docs/feature-status.md (deploy approvals stable, notification channels, vendor kinds tested against fakes, required approvers), docs/cli-reference.md (channels and deploy-approvals commands, supported kinds), docs/environments.md (protected environments)
- Levelrail code: internal/alerting/chat_approval.go (Slack and Discord payloads, unsupported error for other kinds), internal/api/chat_interactions_test.go (handler tests), internal/api/notification_channels.go (interactive_approvals and interactive_secret fields)
- Local run on 2026-11-11 on a laptop with a local control plane build from 10 November 2026


Top comments (0)