Rules

A rule is a standing instruction: watch for this on this client's books, and raise it when it happens. Kraal already watches the normal path, so you only add a rule when a client needs something extra.

Rules belong to clients

Every rule belongs to one client, and the page groups them that way with the client named on each row.

This matters when you first look at the list. Two clients that both use the same built-in rules will show the same rule names twice — once per client. That is not a duplicate. They watch different books, fire independently, and can be paused independently.

Reading a rule

Each row states the rule itself rather than its settings:

Overdue bills · Built in · TestCompany6 Alert when there are 3 or more overdue bills — notifies your phone Fired 14× in 30 days · 6 became work · last 2 hours ago

• Built in rules come with Kraal. Custom rules were written by someone on your team. You can filter by either, because they tend to be managed differently.
• The condition is the rule in words. Where a rule also waits for something to go stale, it says so — "untouched for 2 days". Where it watches a cash balance, it says the amount.
• What happens when it fires is stated as a consequence, not a severity grade. Only urgent rules reach your phone; the rest wait in your list.

Firing history

The history line is the part worth reading after setup, because it answers the only question that matters then: does this rule earn its place?

Two situations get flagged:

• Noisy — the rule fires often and almost nothing comes of it. Tighten the threshold or turn it off.
• Never fired — either the condition never occurs, or the threshold is set too high to ever trip.

Counts cover the last 30 days: long enough that a weekly rule still registers, short enough that "hasn't fired" means something.

Working with rules

• Check now runs the rule immediately and tells you whether anything met the condition.
• Pause stops a rule firing without deleting it. Paused rules stay visible so you can see what monitoring is switched off.
• Delete is in the ⋯ menu, since removing monitoring is not something to do by mis-click.
• Search covers rule names, clients and origin. Above a dozen rules the list becomes a table, which scans better than a grid of cards.

Adding a rule

Adding a rule reads as a sentence rather than a set of fields:

Alert when there is 1 close blocker for TestCompany6. Notifies your phone straight away.

Pick what to watch for, how many, and what should happen when it fires; the preview updates as you go, in the same words the finished rule will use. A rule belongs to one client, so pick a client in the scope bar first — the page says so if you have not.

Templates fill in the common cases: month-end close, AP and AR risk, a cash floor, reconciliation drift, inventory shortage, and sync failures.