Guide

Approvals and boundary rules

How a Bot asks before it acts, where you answer, and the rules that decide what it may do without asking, what it must ask about and what it may never do.

4 min read

The approval inboxCopy link to this section

Requests wait for you on Approvals, and the same request appears as a card in the chat, so one answer counts in both places. Each card shows the risk (low, medium or high) with its reasons, what the Bot wants to do and to what, What the Bot saw, Why it asked, recent messages and earlier decisions on the same action. Filter by Bot, risk, how long it has waited or who it is for, and decide several similar requests at once with Select similar.

Ways to answerCopy link to this section

ChoiceWhat it does
Allow onceThis action only; the next one asks again.
Allow for this conversationThe same action in this conversation, for 24 hours at most.
Allow for the next hourThe same action anywhere for 60 minutes.
Always allow hereSaves a rule so this action no longer asks.
Edit, then approveChange the text, command or arguments first; your version is checked against the same rules, and both are kept in the audit trail.
Deny, or Refuse with a noteThe Bot does not do it. A note (up to 500 characters) tells it why, so it can try another way.

Only a request's owner sees the three longer allows; a delegate or a second approver answers once or denies. A request nobody answers is refused after 24 hours unless your administrator set another time, and the Bot is told it expired rather than that someone said no. You can also answer from a push notification (a high-risk request opens the app instead) or from Slack, Microsoft Teams or LINE once you link them on Reachability; requests are sent to you privately, never into a shared channel.

Your own settings and rulesCopy link to this section

  • Ask before making changes (off until you turn it on) makes every change to websites, connected apps and files wait for you. Reading never asks.
  • Auto-review has a model check an action that could affect your accounts or share information against what you asked for and your rules; when it cannot decide, it asks you.
  • Add a rule names a tool or app, a kind of action, a target and a Bot (* matches anything), and one behaviour: take action without asking, take action if pre-approved, ask before taking action, or hand off to you. When several rules match, the strictest wins.
  • After you approve the same kind of action 5 times without a denial in 30 days, Suggestions offers to let the Bot do it without asking. Not now hides the offer for 30 days.

Some things are always handed to you whatever the rules say: entering passwords, codes or keys, changing security, sharing or access settings, and payments.

Team rules (administrators)Copy link to this section

Under Team settings on the Approvals page an administrator can add team rules, which members cannot remove; require auto-review for everyone; require a reason to approve a high-risk request; stop members setting personal rules; set how long a request waits and who it is escalated to; create approver groups; and require two-person approval for a Bot or tool, where either person refusing refuses the action and the Bot owner's own approval does not count. Members can set an out-of-office delegate for themselves.

Boundary rulesCopy link to this section

On Admin › Boundaries an administrator writes rules that are checked before every action a Bot takes on its computer, in three lists: It may never (checked first), Ask a person first (the Bot waits in Approvals whatever the person's own settings say) and Otherwise it may. Each rule is one CEL expression over the action, such as page.host, element.type, intent, file.extension, time.hour, time.weekend or pii.count, with contains(field, text) and matches(field, pattern), both ignoring case. A rule that cannot be evaluated counts as matching, so a mistake refuses rather than allows.

Examples to copy:

intent == "type" && contains(element.name, "password")
intent == "navigate" && matches(page.host, "(^|[.])(facebook|x)[.]com$")
intent == "download_file" && matches(file.name, "[.](exe|msi|dmg)$")
time.weekend || time.hour < 9 || time.hour >= 18
pii.count > 0 && !matches(page.host, "(^|[.])example[.]co[.]jp$")

The first three belong under It may never: no typing into password fields, no social media, no downloading programs. The fourth, under Ask a person first, makes actions outside business hours wait for approval. The last asks before personal data goes to any site other than your own domain (put yours in place of example.co.jp).

Build a rule writes an expression for you from an action type, a site and element text, and Test first checks it. Ready-made rules cover business hours (weekdays 9:00 to 18:00 in the workspace's time zone) and personal data leaving the company, and Policy packs such as read-only research, no outbound email and no purchases install in record-only mode until you switch them to stop actions. Every change is kept in History, and refusals appear in the audit trail.

Last updated