Answer a request
A request asks for a decision about a Bot action. Answer only requests that are waiting for you. They can arrive in your client or a linked Channel.
Review the action
Section titled “Review the action”Read which Bot asks, what it will do, its target, and its reason. For an App call, check the supplied values too. A Bot reason explains its request; it is not an instruction you must follow. Deny the request with a reason when the action does not fit your task.
Choose the scope
Section titled “Choose the scope”| Choice | Effect |
|---|---|
| Allow once | This call may run |
| Allow in this Chat | Keep a Grant for matching work in this Chat |
| Allow for the lifetime | Keep a Grant until you revoke it |
| Deny | The call does not run |
A Chat can last a long time. Use one call when you only mean one call. A denial can also be kept for the Chat or lifetime when your client offers those scopes. Review saved decisions in Rules and Grants.
An approval for one call stays with that saved call and its input. A restart can resume the same call, but cannot spend its Grant on another call. A revoked Grant or a new deny still stops the call.
Check what follows
Section titled “Check what follows”An allowed call runs and its result returns to the Chat. A denied call does not run. Normal unanswered requests expire as denied, by default after 24 hours. Plan requests have their own expiry result; read it rather than assuming that waiting means denial. If another person must decide, ask that person to review the request.
Requests kept from an older version can still show as pending while their execution is interrupted. You can read them, but you cannot allow the old action. Send a new message to the Bot to ask again with your current rights.