Profiles & the schema builder

This is your superpower. A profile is a reusable, saved schema — your own definition of the rooms, items, and questions a particular loss type needs. Build it once; every assignment created from it inherits the same structure.

Why profiles exist

Different losses need different documentation:

• Total Loss Fire — many rooms, thousands of items, deep item details, strict required fields for bulletproof documentation.
• California Theft Loss — self-serve, with Condition mandatory on every item and police-report questions.
• Public Storage — a single unit, minimal fields, low friction.

A profile lets you express exactly that, per team — no engineering required.

The building blocks

Concept	What it is	Example
Entity	A group of fields you capture	"Item", "Loss Information", "Room"
Field	One typed input on an entity	"Condition" (dropdown), "Estimated value" (currency)
Profile	A bundle of entities + settings, saved & reusable	"California Theft Loss"

Each entity has a scope — where it shows up in the field app:

• Assignment — once per claim (e.g. Loss Information).
• Room — once per room.
• Group / item — per item bundle (e.g. Item details).
• Media — on an individual photo.

Build a profile

1. Open a team → Profiles → New profile. Name it for the loss type.
2. Add an entity (e.g. "Item"); set its label and scope.
3. Add fields to the entity. For each field choose:
   • a type (text, number, currency, yes/no, dropdown, date, file, and more — see Field types);
   • validation — required? min/max? a pattern?
   • options for dropdowns;
   • conditional visibility — show this field only when another answers a certain way.
4. Reorder fields and entities into the sequence you want field users to follow.
5. Save as draft while you iterate.

TIP

Start from a template. The built-in California Theft Loss and Public Storage profiles are great starting points — clone one and adjust.

Conditional fields

Conditional visibility keeps forms short and relevant. Classic example:

• Field "Have you filed a police report?" → Yes / No
• Field "Attach the police report" → shown only when the answer is Yes.

Field users never see fields that don't apply to their answers.

Required fields

Mark a field required to guarantee it's captured — the field app won't let it be skipped. This is how "Condition is mandatory in California" is enforced for real, on every item.

Draft → Publish → Version

• Draft — edit freely; not yet usable for new assignments.
• Publish — make it selectable when creating assignments.
• Versioning — when you edit a published profile, it bumps to a new version.

IMPORTANT

Existing assignments are snapshotted from the profile version they were created with. Editing a profile never changes documentation already captured — historical evidence stays exactly as it was. New assignments pick up your latest published version.

Next: Creating assignments.