Organization settings

The Settings page holds org-wide configuration: organizations, mobile app permissions, terminology, assignment visibility, spreadsheet import, capture settings summaries, and platform integrations.

Find it at System → Settings.

Organizations card

Create, switch, rename, and delete organizations. Covered in full in Structure and terminology.

Mobile app card

A single checkbox: "Let org, business unit, and team admins create assignments and manage assignment access from the mobile app" (default: on).

When on, admins in the field can spin up assignments and grant access from their iPhones, which is valuable during catastrophe responses when nobody is at a desk. Turn it off if your operation requires all assignment creation to go through the office console, for example when assignments must follow a strict intake process.

Terminology card

Rename the eight nouns the platform uses (business unit, team, assignment, and location, singular and plural). Applies to both the console and the mobile app. Covered in Structure and terminology.

Assignment visibility card

A role-by-status checkbox matrix controlling which assignment statuses each role sees in the mobile app:

• Rows: team admins, members, collaborators, observers.
• Columns: the assignment statuses (draft, active, in review, submitted, completed, archived).

Check a box to let that role see assignments in that status on their devices. Uncheck to hide them.

Key behaviors:

• Org and business unit admins always see every status, regardless of the matrix.
• All boxes checked means no restriction, which is the default.
• The server enforces this in sync. Hidden assignments are never sent to the device, so the restriction cannot be bypassed from the app.

A common setup: hide draft and archived from members and collaborators so field staff only see work that is actually live.

Import assignments from spreadsheets

Bulk-create assignments from multiple spreadsheet files with per-file column mapping and a progress view, plus the one-shot Field Inventory (Sedgwick) profile scaffolding. Covered in Assignments.

Capture settings by team

A summary card showing each team's watermark and GPS status, with links into each team's Settings tab. Use it as a quick compliance check: if a carrier requires watermarks on a given team's work, this card confirms at a glance whether that team's defaults comply. The settings themselves are documented in Capture settings.

System integrations

Platform-level email and SMS delivery settings:

• Mailgun: API key (write-only, never displayed back), domain, from address, and a test email button.
• Twilio: Account SID, auth token (write-only), from number in E.164 format, and a test SMS button.

These values power the email and SMS steps in workflows and message delivery generally. Values stored here override environment defaults.

Platform-level settings

System integrations are a super-admin, platform-level concern. Most organizations never touch this card; delivery is configured for you. If your workflows' emails or SMS messages are not arriving, contact support rather than changing these values blindly.

What is not here

So you do not hunt for them: the console currently has no retention controls, no storage quotas, and no sync-policy or upload-quality settings. Media retention is not time-limited, and capture quality is managed by the field app itself. If your organization has compliance requirements around retention, raise them with support.