Help: Rules
How rules work
When an agent submits a request, funwatcher checks it against your account's rules and gives exactly one outcome. You see your rules on the Policies page.
The four outcomes
| Outcome | What happens to the request |
|---|---|
| auto allow | The agent is told at once that it may proceed. Nobody is asked. |
| hold | The action waits for the hold period, then the agent may proceed unless you cancel it first. See Held actions. |
| require approval | The request waits in the Inbox until a person approves or denies it, or it expires. |
| prohibit | The agent is told at once not to act. Nobody is asked. |
How one rule is chosen
- Only enabled rules are considered. A disabled rule, or a rule still awaiting confirmation, is skipped.
- Rules are checked from the highest priority number down. When two rules have the same priority, the one created first is checked first.
- If any matching rule has the outcome "prohibit", the request is prohibited. This holds even when a rule with a higher priority also matches.
- Otherwise the matching rule with the highest priority decides the outcome.
- If no rule matches, the request requires approval.
One exception: an agent can have its own default outcome, which replaces a catch-all rule for that agent. See Set a default policy for an agent.
The request's card shows which rule decided and why. See Read a request.
What a rule can look at
A rule's condition tests what the agent submitted: the action type, the amount and currency, the counterparty, fields of the payload, whether the action is marked reversible, which agent sent it and the time of day. See Build a rule with the form for each test.
What rules do not do
- Evaluation never uses an AI model. The same request against the same rules always gives the same outcome.
- The only place an AI model is used is when you write a rule in plain English: the model turns your sentence into a rule, and you confirm it before it takes effect. See Write a rule in plain English.
- Rules are applied once, when the request arrives. Changing a rule does not change requests that already have an outcome.
- Rules judge what the agent says it will do. funwatcher cannot check that the description is accurate and cannot stop an agent that acts without asking.
When your own decisions follow a pattern, funwatcher suggests a rule for you to review. See Suggested rules. To keep a copy of your rules, see Export your rules.
A new account starts with a set of rules already enabled. See The default rules.
Previous: Request statuses
Next: The default rules
All help pages
Inbox
- Read a request
- Approve, deny or edit a request
- Held actions
- Expired requests and history
- Request statuses
Rules
- How rules work
- The default rules
- Write a rule in plain English
- Build a rule with the form
- Reorder, enable and disable rules
- Suggested rules
- Set a default policy for an agent
- Export your rules
Teams
Ledger
- What the ledger is
- Browse and filter the ledger
- Export and verify the ledger
- Payload retention
- Monthly statements
Billing
Account and security
- Change your password
- Two-factor authentication and recovery codes
- Rotate or revoke an agent key
- How your data is protected
- Closing an account