Field types

When building a profile, each field has a type that decides how field users enter it and how it's validated. Here's the full set.

Type	What field users see	Use it for
Text	A single-line box	Short labels, names, model numbers
Long text	A multi-line box	Descriptions, narrative notes
Number	A numeric keypad	Counts, measurements
Currency	A money input	Estimated values, costs
Yes / No	A toggle	"Filed a police report?"
Date	A date picker	Date of loss, purchase date
Date & time	A date + time picker	Precise event times
Dropdown (select)	Pick one option	"Condition": New / Good / Fair / Poor
Multi-select	Pick several options	"Damage types": Smoke, Water, Soot
Phone	A phone input	Contact numbers (validated format)
Email	An email input	Contact emails (validated format)
Barcode	A scanner	UPC / QR for fast item identification
File	Attach a document/photo	Police reports, receipts, prior estimates
Media reference	Link to a captured item	Tie a field to a specific photo
Signature	Sign on screen	Acknowledgements / sign-offs

Validation options

Per field, you can require and constrain input:

• Required — must be filled before the form is complete (e.g. mandatory Condition).
• Min / Max — numeric bounds (e.g. value ≥ 0).
• Length — minimum/maximum characters for text.
• Pattern — a format rule for advanced cases.
• Options — the choices for dropdown / multi-select fields.

Conditional visibility

Any field can be set to appear only when another field has a specific value — so forms stay short and relevant. See the police-report example.

TIP

Prefer dropdowns over free text wherever you can. Consistent, pickable values make the downstream inventory and any reporting far cleaner than typed-in text.