Appearance
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
| Area | What it's for |
|---|---|
| Teams | Organize your org into business units and teams; set team defaults. |
| Profiles & schema builder | Define your own rooms, item fields, and loss questions — saved as reusable profiles. |
| Assignments | Create a loss/claim from a profile and hand it to the field. |
| Access | Invite collaborators/observers and manage members and roles. |
| Capture settings | Toggle timestamp, GPS, and watermarking. |
| Webhooks | Push events to your other systems in real time. |
| Audit log | A 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 inviteThe 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
- Create your team (e.g. "California Theft Losses").
- Build a profile with the rooms/items/questions that loss type needs, and publish it.
- Choose your capture settings (timestamp/GPS/watermark).
- Create an assignment from the profile.
- Invite the field user(s) by email or phone.
- Watch progress and the audit log; wire webhooks into your claim system if you like.
Start with Org structure & teams.