# `frontline settings`

Account-wide data & sync defaults every user inherits, per channel: how email, WhatsApp, calendar and meeting activity turns into CRM records. Read-only — one change here applies to every user at once, so these are edited in the app by an administrator. Works with an account API key, or a user key belonging to an OWNER or ADMIN. A user's own overrides live in `max settings`; meeting analytics is `frontline meetings analytics`.

```bash
frontline settings [options] [command]
```

## `frontline settings email`

Defaults for how email activity becomes CRM records: contact auto-creation, People linking, record assignment, which People record type new contacts get, and whether administrators may view everyone's mail activity.

```bash
frontline settings email [options] [command]
```

### `frontline settings email get`

Show the account's email defaults, and which of them users are allowed to override on their own profile.

```bash
frontline settings email get [options]
```

**Options**

| Flag | Description | Default |
|  --- | --- | --- |
| `--api-key <key>` | Override API key for this run (else FRONTLINE_API_KEY env, else stored profile key) |  |
| `--base-url <url>` | Advanced: override Public API base URL for this run |  |
| `--profile <name>` | Credentials profile: uses that profile's saved API key and Public API base URL (see `frontline auth profiles list`) |  |
| `--debug` | Show debug info on stderr (token is redacted) |  |
| `--pretty` | Pretty-print human-readable output (instead of default JSON) |  |
| `--table` | Render list results as a table (implies --pretty) |  |
| `--json` | Output raw JSON (default behavior — accepted as a no-op) |  |


## `frontline settings whatsapp`

Defaults for personal WhatsApp sync: contact auto-creation, which chats are in scope, whether muted, archived or group chats are skipped, and which People record type new contacts get. The Business numbers your agents answer on are separate — see `frontline channels`.

```bash
frontline settings whatsapp [options] [command]
```

### `frontline settings whatsapp get`

Show the account's personal WhatsApp sync defaults.

```bash
frontline settings whatsapp get [options]
```

**Options**

| Flag | Description | Default |
|  --- | --- | --- |
| `--api-key <key>` | Override API key for this run (else FRONTLINE_API_KEY env, else stored profile key) |  |
| `--base-url <url>` | Advanced: override Public API base URL for this run |  |
| `--profile <name>` | Credentials profile: uses that profile's saved API key and Public API base URL (see `frontline auth profiles list`) |  |
| `--debug` | Show debug info on stderr (token is redacted) |  |
| `--pretty` | Pretty-print human-readable output (instead of default JSON) |  |
| `--table` | Render list results as a table (implies --pretty) |  |
| `--json` | Output raw JSON (default behavior — accepted as a no-op) |  |


## `frontline settings calendar`

Defaults for how calendar events become CRM records: whether attendees become contacts, whether internal colleagues are skipped, and which People record type new contacts get.

```bash
frontline settings calendar [options] [command]
```

### `frontline settings calendar get`

Show the account's calendar defaults.

```bash
frontline settings calendar get [options]
```

**Options**

| Flag | Description | Default |
|  --- | --- | --- |
| `--api-key <key>` | Override API key for this run (else FRONTLINE_API_KEY env, else stored profile key) |  |
| `--base-url <url>` | Advanced: override Public API base URL for this run |  |
| `--profile <name>` | Credentials profile: uses that profile's saved API key and Public API base URL (see `frontline auth profiles list`) |  |
| `--debug` | Show debug info on stderr (token is redacted) |  |
| `--pretty` | Pretty-print human-readable output (instead of default JSON) |  |
| `--table` | Render list results as a table (implies --pretty) |  |
| `--json` | Output raw JSON (default behavior — accepted as a no-op) |  |


## `frontline settings meetings`

The notetaker defaults every user in the account inherits: bot branding, recording region and duration cap, custom vocabulary, CRM sync behaviour (including which People record type new contacts get), pre-meeting reminders, and who may create folders and note templates.

```bash
frontline settings meetings [options] [command]
```

### `frontline settings meetings get`

Show the account's notetaker defaults, and which of them users are allowed to override on their own profile.

```bash
frontline settings meetings get [options]
```

**Options**

| Flag | Description | Default |
|  --- | --- | --- |
| `--api-key <key>` | Override API key for this run (else FRONTLINE_API_KEY env, else stored profile key) |  |
| `--base-url <url>` | Advanced: override Public API base URL for this run |  |
| `--profile <name>` | Credentials profile: uses that profile's saved API key and Public API base URL (see `frontline auth profiles list`) |  |
| `--debug` | Show debug info on stderr (token is redacted) |  |
| `--pretty` | Pretty-print human-readable output (instead of default JSON) |  |
| `--table` | Render list results as a table (implies --pretty) |  |
| `--json` | Output raw JSON (default behavior — accepted as a no-op) |  |