Glossary

Plain-language definitions of the terms used across ContentsCapture. Note that your organization may have renamed some nouns in Terminology, so "Team" below might read "Crew" in your console; the meaning is identical.

Structure

Organization Your whole company. The top of the hierarchy, holding business units, teams, users, and all their work.

Business unit A division inside an organization: a region, a line of business, or an event-level operation. Contains teams and can have its own admin.

Team A durable group of people who work losses together. Assignments, profiles, and capture-setting defaults all belong to a team.

Member A role for regular field staff: capture media and view media, within their teams.

Can capture A share level for one assignment: the person can capture and edit there, like a member, and sees nothing else. The standard way to bring in contractors. Called Collaborator before version 2.0.

View only A share level for one assignment: the person can look but not change anything. For carrier representatives and oversight. Called Observer before version 2.0.

Roles

Org admin Runs the whole organization: every team, its people, and their roles, plus org-wide field activity on the Dashboard. Webhooks and integrations are set up by Adjust Square. Called Business Unit admin before version 4.0.

Adjust Square admin The retired role that used to be called Org admin. Only Adjust Square staff still hold it, and nobody can be given it.

Team admin Runs a team day to day: members, profiles, assignments, access grants, and audit access.

Work

Assignment A unit of work, usually one loss. Created inside a team from a published capture profile, with capture settings snapshotted at creation.

Capture profile The form/schema attached to assignments: the entities and fields adjusters fill in, for example "Loss Information" or "Item".

Entity A named collection of fields inside a profile, with a cardinality (single or many) and a scope.

Field One question or data point inside an entity. One of 15 types, from text to signature. See Field types.

Scope Where an entity's fields attach: the assignment as a whole, each location, each group, or each media item.

Published / draft / archived profile The profile lifecycle. Drafts are editable; published profiles are locked and usable for assignments; archived profiles are retired.

Snapshot A frozen copy taken at assignment creation. Assignments snapshot both the profile schema and the capture settings, so later changes never alter existing assignments.

Capture

Capture settings The evidence rules applied to every capture: timestamping, GPS metadata, proxy requirement, and watermark. See Capture settings.

Watermark A visible mark burned into review copies of captures: time, user, location, assignment, custom text, and a logo. The original master always stays clean.

Proxy A compressed copy of a capture used for fast review in the console. The original is always retained alongside it.

Submission A locked, immutable hand-off of media from the field. Creating one locks every included item read-only. See Submissions and media.

Sync state Where a media item is on the path from device to server: captured, processing, queued, uploading, synced, or failed.

Tag A word your organization agrees on, attached to an assignment, a room, or a media item, for the classifications the fixed fields do not cover. Matched without regard to capitalization, so "Roof" and "roof" are one tag. Workflows can read tags, trigger on them, and apply them. See Tags.

Tag registry The org-wide list of defined tags, with their colours, descriptions, and live usage counts. A tag anyone types is added automatically, so the list is the complete vocabulary in use rather than a curated subset.

Operations

Dashboard The landing screen and live operations view: a real-time feed, a field map with GPS trails, and productivity stats grouped by person or by job. Org-wide field activity is limited to org admins. Called Overview before version 6.0, and before that a separate screen called Mission Control. See Dashboard.

Automation

Workflow An event-driven automation: when something happens, send messages, update statuses, or call webhooks. See Workflows.

Trigger The event that starts a workflow, for example submission.created.

Condition A branch in a workflow that runs steps only when checks pass, such as "status equals submitted".

Tag action A workflow step that puts a tag on something or takes one off. Because a workflow can also read tags, a tag is how an automation remembers that it has already acted.

Run One execution of a workflow. The runs feed shows every run with per-step detail and replay.

Template A reusable, versioned email or SMS message with {{variable}} placeholders, used by workflow send steps.

Webhook An outbound HTTP POST to your URL when events happen, signed so you can verify the sender. See Webhooks.

Signing secret The per-endpoint secret used to sign webhook deliveries. Shown once at creation; store it safely.

Integration token A read-only bearer token giving a partner app access to your org's assignments and media. See Integration tokens.

System

Audit log The record of every significant action in your org: actor, subject, source, IP, and detail, including denied actions. See Audit log.

Impersonation A support capability where platform staff act as a user to diagnose problems. Every impersonated action is recorded in the audit log.

Terminology An organization's own words for the platform nouns (business unit, team, assignment, location), shown across the console and mobile app. Organizations that already have their own words keep them; they are no longer changed from the console.

Assignment visibility The role-by-status matrix in Settings → Organization controlling which assignment statuses each role sees in the mobile app, enforced server-side.