Organization settings

The Settings area

Settings, right under My Team in the sidebar, holds everything that configures the organization, so the sidebar can stay focused on the daily work. Click it and you get a page of cards, one for each settings screen. Click a card to open that screen.

The cards are grouped under section headings:

Section	Cards
Organization	Organization, Tags, Audit log
Automation	Workflows, Runs, Templates
Connections	Webhooks, Integrations

You only see the cards your role can open. See What each role sees in the sidebar.

Type in Search settings at the top to narrow the cards. It matches words in the title and the description, plus common words for what is inside, so typing email finds Templates and token finds Integrations.

Inside any settings screen, the line above the title reads Settings › Webhooks (or whichever screen you are on). Click Settings there, or the Settings back link above it, to return to the cards.

The Organization screen

Click the Organization card. It holds the settings for the organization you are viewing: its name, mobile app permissions, assignment visibility, and spreadsheet import.

Name card

Shows the organization's name and its org ID. Org admins can click the name to change it right there: type the new name, then press Enter or click anywhere else to save. Press Escape to cancel. Adjust Square admins switch to a different organization with Shift + T; see Which organization you see.

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.

Assignment visibility card

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

• Rows: team admins, members, and people an assignment was shared with (Shared: Can capture and Shared: View only).
• 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 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 people shared at Can capture 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 profile scaffolding. Covered in Assignments.

Admin (Adjust Square staff only)

Adjust Square staff have one more item in the sidebar, right under Settings: Admin, shaded yellow with an ADMIN tag. Customers never see it, including Org admins. It opens a page of cards laid out like Settings, under two headings, Customers and Platform:

• All organizations: every customer organization on the platform, with its customer type, how many teams and people it has, and whether it came from ContentsEstimation. The search box finds an organization by its name or by the name of any team in it. Show teams lists its business units and teams with how many people are on each, the Customer type menu switches it between Standard and Enterprise, Switch steps into one exactly like pressing Shift + T, Rename changes its name, Delete hides it, and New organization creates one. Only staff can change a customer type or create an organization; the server turns anyone else away.

• Device health: the last report from each phone.

• App release and systems, which has two cards:

  • App release: which mobile app version is the latest released one.

  • 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

These are platform-level settings that apply to every customer. Organizations never see them; 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.