Field Visibility

In Kasura

Field visibility in Kasura follows exactly two modes for every configurable field: a field can be visible or hidden, and a visible field can additionally be marked required. This applies consistently across handover fields (pickup, return, check-in, check-out), asset fields and customer fields. There is deliberately no third, 'recommended' tier between optional and required: a middle tier would promise commitment without enforcing it, and the resulting outcome — a field that staff often skip but that appears in the data as though it were reliably filled — is worse than either a clearly optional or a clearly required field. A blunt binary between visible/hidden and required/not-required is more honest about what is actually enforced, and in practice produces more trustworthy data than a soft middle ground would. This mechanism lets each workspace match its field configuration to its own actual diligence level: a business that never records odometer readings can hide that field entirely rather than being forced through it repeatedly, while a business with strict documentation requirements can make relevant fields mandatory. Field visibility is explicitly not a form builder: users cannot create new custom fields, and there is no way to add a field the product does not already define — configuration is limited to visibility and requirement of the existing field set.