Automations
What it's for
Automations is where you decide how much the product is allowed to do on its own, and where you approve the things it wants to do. Every module can be off, can suggest and wait for you, or can act within limits you set — and whatever it does is labelled, explained, and reversible.
Reach it from Automations in the sidebar, at /automations.
Tabs
The screen has no tabs. It is two things on one page: the approval queue, and the rules that produce it.
Panels and controls
The approval queue
Items waiting on a human decision. Approve accepts one, Reject turns it down with an optional "Reason / what to fix", and there is an approve-all for a queue you have already reviewed. An approved item can be undone, and a rejected one restored — no decision here is a one-way door.
No approvals waiting is the empty state, and it is the state you want.
The rules
Each rule has a mode and a threshold. The threshold is the boundary between "handle it" and "ask me": below it, the module acts and tells you; above it, the item lands in the queue above.
Automation cap is the tighter of two numbers — it can never exceed the human threshold, and the screen refuses to save a configuration where it does. That is the safety property worth understanding: the cap is what the product may do unattended, and it is always at or inside what a human would have to approve.
Save changes commits; Cancel discards.
What it accepts
| Field | Format | Required | Rule |
|---|---|---|---|
| Rule mode | Off, suggest, or act | Yes | |
| Threshold | A non-negative number | Yes | "Enter a valid, non-negative threshold." |
| Discount threshold | A percentage | Yes, for discount rules | "Discount threshold can't exceed 100%." |
| PO threshold | Dollars | Yes, for purchase-order rules | "That PO threshold looks too large." |
| Automation cap | A non-negative number | Yes | "Enter a valid, non-negative automation cap."; "Automation cap can't exceed the human threshold." |
| Rejection reason | Free text — optional | No | Recorded with the rejection |
These refusals state a policy rather than a validation error:
- "Refund automation stays off while every refund requires human approval." — refunds are money leaving; the product will not take that decision.
- "<module> can't run on Auto yet — its reviewed limits only cover Suggest." — a module only runs unattended once its limits have been reviewed for it; Suggest and Off are always available.
- "Only an owner can turn on Auto for <module>." — Auto is included for every shop, but turning it on for a module is the owner's decision.
How to configure it
- Automations settings on this screen are the configuration.
- Not-to-exceed and Deposits settings interact with the money-related thresholds here.
Who can see it
This screen sits behind the Automations area.
Owners and office managers can open it. Dispatchers and technicians cannot — how much autonomy the shop grants is an owner's decision. The gate is checked on the server, not just hidden in the sidebar, so a direct link does not get around it.
The full role matrix is on Roles & permissions.