What runs on its own
The workflows Dardaris ships with, how they are written, and why every one of them is auditable.
Updated
The categories
Sixty workflows come with the product, across eleven categories: rent collection, arrears, lease lifecycle, maintenance, compliance, move in / out, communication, vacancy and letting, finance, short stay and reporting. Every one can be switched off, and every one's trust level is yours to set.
A workflow is data
A workflow is not code. It is a trigger, a set of conditions and a list of actions, stored with your portfolio. Its trigger, its conditions and its steps are shown in full, in the same words as here, so you can read exactly what one will do before you let it run.
Conditions
Conditions are written in a small grammar: a field, a comparison, a value. Every condition on a rule has to hold before it runs. "Invoice is more than 5 days overdue, and the tenant is not marked vulnerable, and the amount is over your threshold" is three of them, and they read the same way on the automations screen as they do here.
The audit trail
Every action Dardaris takes writes an entry with the workflow that fired it, the records it touched, and a sentence saying what it did and why. Nothing it does is unexplainable after the fact. That is not a nice-to-have. An action you cannot trace back is an action you cannot supervise, and supervising is your half of the arrangement.
How far a workflow is allowed to go on its own is a separate setting: autonomy tiers and spend caps. What it does when it has to stop: approving something.
Most of what runs day to day is money: rent and invoicing.