An approval rule names one action class and an optional amount in USD. Above the amount, the seat's Actions of that class wait for you; everything else, the agent does.

For developers

What you get

1approval rule on the support seat: every spend over $50 waits for youRole
1request to you for each Action the rule catches, with the amount and the reasonApproval
1record of the change, on the seat’s historyDecision

Your agent does

Role.update

You, to your agent

Change which approvals come to me.

Ask me before any refund over $50.

Ask me before anything goes live.

# Role.update
curl -X PATCH https://api.sb/leaseline.app/roles/customer-lead \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Leaseline","approvals":[{"class":"spend","above":50}]}'

import { $ } from 'startup-builder'

await $.Role.update({ id: 'customer-lead', name: 'Leaseline', approvals: [{ class: 'spend', above: 50 }] })

npx startup-builder do Role.update --json '{"id":"customer-lead","name":"Leaseline","approvals":[{"class":"spend","above":50}]}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Role.update({ id: 'customer-lead', name: 'Leaseline', approvals: [{ class: 'spend', above: 50 }] })"
  }
}

Change it

Raise it to $200.
Ask me before every publish, on every seat.
Stop asking me about sends to fewer than 100 people.

Under the hood

Systems: Workforce, Work queue
Nouns: Role, Approval, Action, Decision
Events: Role.updated

Change what waits for me

What you get

Your agent does

Change it

Under the hood

Contents

What you getCopy Anchor Link

Your agent doesCopy Anchor Link

Change itCopy Anchor Link

Under the hoodCopy Anchor Link

What you get

Your agent does

Change it

Under the hood