# Settings

Two things about the feedback form you can change without a new app version: which kinds of feedback are on, and two texts, per language. Everything else about the form comes from the component, translated into 20 languages.

## What you can set

| Setting | What it does |
|---|---|
| General | A comment without pointing at anything. On by default |
| Point at something | The user taps an element and comments on it. On by default |
| `footer` | The sentence under Send. Per language |
| `thanks` | The thank-you after sending. Per language |

If both kinds are off, the edge tab disappears. A language you leave empty shows the component's own translation. The codes are case sensitive: `en`, `nl`, `de`, `fr`, `es`, `pt`, `it`, `pl`, `tr`, `ru`, `uk`, `sv`, `da`, `nb`, `ja`, `ko`, `zh-Hans`, `zh-Hant`, `ar`, `hi`.

A text is 1 to 140 characters. It is shown as plain text and cannot hold links, domain names, email addresses, phone numbers or markup; the platform refuses those. No other text can be changed.

## When it applies

Changes reach your users within a minute, the next time the app starts or comes back after more than an hour in the background.

An open feedback form keeps the settings it had when it was opened.

## Where to change them

**Dashboard.** Open the app and then Settings: two switches, the two texts per language (with the component's own translation as the example in an empty field), and the line "Last changed ... via ...".

**CLI.**

```bash
nitpick settings show --app <id>
nitpick settings set --app <id> --specific off
nitpick settings set --app <id> --footer nl="Je feedback gaat naar de maker" --thanks en="Thanks, we read every note"
nitpick settings set --app <id> --footer nl=
```

An empty text removes it. See the [CLI reference](/docs/cli).

**MCP.** `get_app_settings` and `update_app_settings`. Do not put `update_app_settings` on a list of tools your agent may use without asking: a report could try to talk the agent into changing your settings. See the [MCP reference](/docs/mcp).

**API.** `GET` and `PATCH /api/v1/apps/{id}/settings`. See the [API reference](/docs/api).

All four use the same rules and the same merge: a change from one place does not overwrite something you changed in another.

## What stays in the code

The public app key, the API address, the color, the font, the place of the tab, the brand mark and the dry run are set in your app and change with a new app version. See [Theme](/docs/theme).