Skip to content

Migrating from Approveit to DueReason

Approveit answers a request with a Slack, Teams or email button. See what moving that step to DueReason's signed, payload-bound grant changes.

Updated · 8 min read

In short

  • Approveit is a Slack/Teams/email-native approval bot for finance, HR, IT and ops requests - the closest chat-native tool to what DueReason already does well, and the one most likely to come up when you are deciding whether a chat approve/reject button is enough.
  • A chat approve/reject button answers a message; it does not hand the acting system a signed, independently verifiable object to check before anything happens - the trust sits in the click having happened in the right channel.
  • DueReason also answers from Slack, Teams, email or a push notification by default - this is not an either/or move - but once answered it issues a signed, single-use grant bound to the exact payload, which whatever acts on the decision verifies rather than assumes.
  • A hash-chained ledger and an agent-native SDK/MCP/GitHub Action/REST API sit behind that same answer, neither of which a chat history or a chat-bot-only mechanism can offer by construction.

If your finance, HR, IT or ops team approves requests with a button in a Slack, Teams or email message, there is a good chance it is through Approveit: a chat-native approval bot built around exactly that approve/reject click. This walks through what that gets you today, and what changes if you move the same request to DueReason.

What Approveit does today

Approveit sits inside Slack, Microsoft Teams or email and turns a finance, HR, IT or ops request into a message with an approve/reject button, so the approver never has to leave the channel they already work in. That is also its whole mechanism: the request, the decision and the record all live as messages in a chat or inbox the bot posts to and reads back from.

What happens after someone clicks approve

A chat approve/reject button answers the message it is attached to. What is not published is a signed, independently verifiable object the acting system checks before anything happens - the trust sits in the click having come from the right channel and the right person, the same gap the Power Automate migration guide and the ApprovalMax migration guide describe for a chain that lives inside the system it approves into. A pure chat-approval bot's whole design assumes a chat message is involved at all; nothing in it answers a request an agent or a pipeline files without a human ever opening Slack.

The record has the same shape as the channel it lives in: a chat history anyone with channel admin rights can edit or delete, not an append-only log kept for the purpose of being produced later. The email/Slack/spreadsheet comparison covers this gap in more general terms if a chat-native tool is one of several channels you are weighing.

The same shape in DueReason, plus a verifiable record

DueReason answers from the same places Approveit does: email per person, a Slack or Microsoft Teams channel, and a browser or phone push notification, with an optional in-message Approve/Decline link, off by default. Moving to DueReason is not a trade of chat-native answering for something else - that part stays. What changes is what happens once someone answers.

Once a request is decided, DueReason issues a signed, single-use grant bound to a hash of the exact payload - the amount, the recipient, the change being made - which whatever executes the decision verifies before it acts, rather than trusting that the right person clicked the right message. That check runs at the acting system, not inside the chat tool that hosted the approval.

What changes, not just what moves

  • A grant the acting system checks, not a click trusted at the source. DueReason's signed grant (duereason/core/src/signing.ts) is bound to a hash of the exact payload and verified by whatever executes the decision, so a changed amount or target after approval is refused rather than carried out on the strength of an earlier click.
  • No payload in the message, by design, not by omission. Per DueReason's approve-where-you-are rule, a Slack, Teams or push message carries only the request's title, action and outcome by default - never the payload, reason, comments or evidence - and a link never answers a request on its own; it opens an authenticated confirmation page. A chat-approval bot that puts the whole decision in the message is making the opposite trade-off, not filling a gap DueReason is missing.
  • A hash-chained ledger, not a chat history. Every step of a request - filed, each answer, what happened after - is a ledger event (duereason/core/src/ledger.ts) from the start, checkable on its own without reconstructing a thread, and not something anyone with channel admin rights can edit or delete.
  • An agent-native surface, not a mechanism that assumes a chat message. The same actions reachable from Slack or Teams are reachable from @duereason/sdk, the MCP server, the GitHub Action or the REST API, so an agent can requestApproval() and waitForApproval() without a human ever opening a chat channel at all.

Moving one approval step over

  1. Install the template closest to what you route through Approveit today - Payments and refunds for finance requests, Vendor onboarding for a new-vendor sign-off - from Settings → Templates, or write your own action for an HR, IT or ops request shaped differently.
  2. Recreate the people each step currently notifies in Approveit as members of the template's approver groups.
  3. Turn on the channels you already use - email is on by default; add the Slack or Microsoft Teams channel from Settings → Notifications, and turn on in-message Approve/Decline links if you want the same one-click feel Approveit's button gives today.
  4. For requests your tools already raise automatically, requestApproval() and waitForApproval() from @duereason/sdk (or the no-code webhook recipe if you would rather not write a backend) replace the point where Approveit's bot used to post the message.
  5. Replace whatever read Approveit's outcome back into the finance, HR or IT system with a check of decided.status and a verification of decided.grant before the step that actually acts - the system doing the work should check the grant, not just trust that a button was clicked.

What has no direct equivalent

Approveit's entire surface is the chat message itself - there is nothing to port beyond the approve/reject step, since DueReason answers from the same channels already. If a stripped-down chat-only approval is genuinely all you need, with no requirement to prove later what was approved and no agent or pipeline ever filing a request on its own, Approveit's narrower scope may still be the simpler tool for that alone.

Questions

Do we lose Slack or Teams approvals by moving to DueReason?
No. DueReason notifies by email, Slack, Microsoft Teams and push by default, with an optional in-message Approve/Decline link - the channel stays the same. What changes is that the acting system verifies a signed, payload-bound grant once a request is decided, instead of trusting that the right click happened in the right channel.
What does Approveit cost, compared to DueReason?
Approveit does not publish pricing captured in this pass - treat any number you see elsewhere as unverified until quoted directly from approveit.today. DueReason is free today for one organization with up to five members, all core features included.
Does DueReason put the full request details in the Slack or Teams message like Approveit does?
Not by default. A chat or push message carries only the request's title, action and outcome; showing the payload, reason, comments or evidence in the message is a separate, per-channel, admin-only setting, off by default. This is a deliberate security choice under DueReason's approve-where-you-are rule, not a missing feature.
Can an agent file a request without anyone opening Slack?
Yes. The same actions answered from a Slack or Teams message are reachable from @duereason/sdk, the MCP server, the GitHub Action or the REST API, so a pipeline or an agent can request and wait for approval with no chat message involved at all.
Can I self-host instead of using the hosted product?
Yes. Self-hosting runs on one Postgres database and one pre-built image started with Docker Compose; the same actions, grants and ledger work the same way whether you use the hosted product or run it yourself.

Move your chat-approved requests to DueReason

Keep answering from Slack, Teams or email - add a signed, payload-bound grant the acting system checks and a hash-chained record it can't edit after the fact.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates