Go to Report configuration (open to managers, location managers, and admins alike — deliberately, so a location manager can tune their own location's report without needing an admin) to control exactly which fields workers see and fill in.
Field visibility
Every field — cash totals, weather, temperature, and so on — has one of three visibility settings:
- Visible — both the worker and the manager see and fill it in.
- Hidden from worker — only you see and fill it in; useful for figures you don't want workers entering themselves, like final cash reconciliation.
- Hidden from all — fully disabled; use this if your company doesn't track that metric at all.
Custom fields
You can add your own fields beyond the built-in set — up to 20 active custom fields per company. Once you exceed that, adding another returns "Custom field limit reached (20)".
A custom field's type can't be changed after creation — you can rename it, relabel it, or toggle whether it's required, but not switch it from text to a number field (or similar) later. Plan the type before creating it.
How "required" validation actually works
A brand-new report missing a required field is rejected outright with
"Field required: <field>". But if you make a field required after some
reports already exist with it blank, editing one of those older reports
won't suddenly force you to fill in a blank you didn't create — the rule
only blocks you from clearing a field that already had a value, not from
leaving alone one that was already empty. In short: this only tightens
going forward, it doesn't retroactively demand backfilling old data.
One field you don't control directly
Garage arrival time can be gated by the platform itself — if that feature isn't enabled for your company at the platform level, the field stays hidden even if your own report configuration says "visible." If a field seems to ignore your setting, this is the first thing worth checking with support.
Known limitations
Weather fields are currently optional by default even where they're intended to be mandatory, and there isn't yet a single consistent rounding rule applied across report numbers — both are known, tracked gaps, not something wrong with your configuration.