Skip to content

Admin overview

Admins run the control plane. You decide what gets captured, spin up assignments, and bring the right people in — so field users get a focused, tailored experience and you get consistent, defensible documentation.

You'll work in the admin web console (in your browser). Field users work in the mobile app.

What you'll do here

AreaWhat it's for
TeamsOrganize your org into business units and teams; set team defaults.
Profiles & schema builderDefine your own rooms, item fields, and loss questions — saved as reusable profiles.
AssignmentsCreate a loss/claim from a profile and hand it to the field.
AccessInvite collaborators/observers and manage members and roles.
Capture settingsToggle timestamp, GPS, and watermarking.
WebhooksPush events to your other systems in real time.
Audit logA clean, complete record of who did what.

How the pieces fit

Org ─ Business Unit ─ Team
                       ├── Profiles  (your reusable schemas)
                       └── Assignments  (created from a profile)
                            ├── Rooms ─ Media ─ Groups   ← captured in the field
                            ├── Loss information           ← your custom fields
                            └── Collaborators / Observers  ← people you invite

The key idea: a profile is a saved, reusable schema. Build it once for a loss type, then every assignment you create from it gets the same fields and structure — consistently.

A typical setup, start to finish

  1. Create your team (e.g. "California Theft Losses").
  2. Build a profile with the rooms/items/questions that loss type needs, and publish it.
  3. Choose your capture settings (timestamp/GPS/watermark).
  4. Create an assignment from the profile.
  5. Invite the field user(s) by email or phone.
  6. Watch progress and the audit log; wire webhooks into your claim system if you like.

Start with Org structure & teams.

Mission-critical loss documentation. Offline-first. Nothing lost.