Guide
How Settings Shape Workflows
Kasura settings shape workflows by making fields visible or required — enforced, not remembered — with exactly two modes, never a third 'recommended' tier.
What problem this solves
'We always record the odometer reading' is an intention; a required odometer field is an enforcement — settings convert the former into the latter without requiring a rule to be remembered at every single handover.
Why the alternative is insufficient
A three-tier system that adds a middle 'recommended' level between optional and required would promise commitment without enforcing it, which produces the worst outcome of all: incomplete data that staff nonetheless trust as if it were complete.
How Kasura handles it
Every configurable field across handovers, assets and customer records is either hidden, visible, or visible and required — no other combination exists.
What this does not mean
That Kasura offers a free-form form builder or a third 'recommended' visibility tier between visible and required; it offers exactly two modes — visible, and visible-and-required — on its existing field set, with no custom field creation.
Related concepts
Part of: Configuration Driven Workflows
Related glossary terms
Related guides
Principles: PR-04, PR-13 · Rationale: WHY-11 · Product Truth: T18
← Back to Guides