Approving something

What lands in Signing

Anything a Review workflow prepared, and anything an Auto workflow prepared that a guardrail stopped. See the three tiers.

In practice that is money out above your cap, formal notices, indexation, terminations, deposit deductions, and anything touching a tenant you flagged as vulnerable. A tenant marked as not to be automated is different: nothing is prepared for you at all, the run stops and says so.

What you are shown

Three things, always:

1. What Dardaris proposes to do, written as a sentence rather than a field diff.
2. The records it is based on, linked, so you can read the source rather than trust the summary.
3. Why it stopped. The limit that held it, named. That is the sentence that tells you whether this needed you or whether your cap is set too low.

An indexation shows its whole calculation. See indexation.

Approving, changing, refusing

Approve and it runs immediately. Change it and what you changed is what runs, with your version recorded next to the proposal. Refuse it and it stops, and Dardaris asks whether the rule that produced it should change.

Answer that question honestly. A rule you refuse every month should not be a rule.

After you decide

Either way it goes into the activity log with your name on it and the workflow that produced it. Approvals waiting on you also appear on the front desk the next morning, until they are dealt with. See the front desk.

A request you never answer has a deadline, 48 hours by default. What happens when it passes is your standing rule under settings: keep waiting, which is what it does out of the box, drop it, or let it go ahead. The last of those is the only setting in the product that turns silence into a yes, so change it deliberately or not at all.