Skip to content
Dash
Request early access Early access

How approvals work

The core idea: Dash drafts, you ship. Anything that changes the outside world goes through an in-Slack approval prompt with the exact action laid out. You click Approve or Deny, and Dash does the thing (or doesn’t). Nothing irreversible happens without your click.

What always requires approval

Section titled “What always requires approval”
  • Sending an email
  • Posting in a public channel
  • Writing to your CRM (creating a deal, updating a contact, changing a stage)
  • Charging or refunding through Stripe
  • Posting on social
  • Creating, editing, or deleting calendar events on someone else’s calendar
  • Anything else that touches the world outside your private DM with Dash

What does NOT require approval

Section titled “What does NOT require approval”
  • Reading data from a tool you have connected
  • Drafting a message, document, or summary that lands in your DM with Dash for review
  • Internal calculations, queries, and analysis
  • Posting back to the same channel you asked Dash from, when Dash is just answering you in thread

The rule of thumb: if the result only lives in your conversation with Dash, no approval needed. If it leaves the conversation, Dash asks first.

What the approval prompt looks like

Section titled “What the approval prompt looks like”

When Dash needs your approval, it posts a card in the same Slack thread. Above the card you see the agent’s own preview of what it’s about to do (the draft email, the row it’s about to write). The card names the pending tool call and gives you three buttons:

  • Approve — run this one action now.
  • Always approve this tool — run it now AND stop asking for this tool in the future. Useful once you trust Dash on a low-stakes tool (like reading a spreadsheet).
  • Deny — cancel this action. Dash goes on with the rest of the turn without it.

If you want to change the wording of a draft first, tell Dash in the thread — “make it shorter” or “swap the link” — and Dash re-drafts, then re-asks.

Who can approve

Section titled “Who can approve”

Only the person who asked Dash to do the thing can approve or deny it. You cannot approve someone else’s pending action, and the Slack card refuses the click if a different user hits the button.

Always approve this tool goes further: it takes effect only if you’re the one who connected the tool (or a workspace admin). If you’re neither, the one-time approval still runs, but the “always” setting won’t stick — Dash will tell you to ask an admin.

Changing the approval rules

Section titled “Changing the approval rules”

Workspace admins can tighten the rules from the Dash dashboard at app.dashpup.ai. Two controls are in your hands per tool:

  • Per-user access. Each connection has a four-tier access matrix: none (can’t use it), read (read-only), ask (writes need approval — the default), or full (writes run without approval). Set it per member, and a workspace-wide default for people you don’t recognize.
  • Per-tool run mode. For any specific tool on a connection, set its default to ask (always ask, even if the caller has full), auto (never ask), or off (block that tool entirely).

These are the levers that let admins say “Dash may never post on social” or “Dash must ask before touching this integration.” You cannot loosen approval below the default: if a tool is a write, the gate still trips unless someone with the authority to lift it does so explicitly.

What’s next

Section titled “What’s next”