Approvals

Approvals are the mechanism Instub uses to make sure consequential actions don't happen without a person saying so. This page explains when they trigger, how to respond, and how to configure policies that pre-approve routine actions.

When does Instub ask for approval?

An approval request fires whenever a job is about to:

• Post a message in Slack or another connected platform
• Create, update, or delete a record in a connected tool (Notion, Linear, etc.)
• Send an email or calendar invite
• Trigger a webhook or API call that has side effects
• Spend credits above your configured per-job limit

How to approve or deny

When a job hits an approval gate, Instub posts a message in the same thread describing the action it wants to take. Reply with approve or deny. You can also reply with a correction — for example, if it drafted a message to the wrong recipient — and Instub will revise and ask again.

Approval policies

For actions your team runs frequently and trusts without review, you can create an approval policy that pre-approves them. Policies are scoped by action type, connected tool, and channel. They are visible in your workspace settings and can be revoked at any time.

Audit log

Every approval — granted or denied — is logged. You can see who approved what in the run log, accessible from the result link in any thread.