City settings

Overriding the widget's platform wording for your organization

How to see and edit your own per-key text overrides for the widget's built-in strings, without touching what other cities see.

By The Kav team Published 2 min read

The widget ships with built-in strings for every language — button labels, prompts, small pieces of chrome. This screen is where your organization can replace any one of them with its own wording, without affecting anyone else.

1. Open City → Widget copy

Every key the widget can render is listed, grouped by key and then by language, with the platform's default text and your override (if any) shown side by side.

They're shown side by side on purpose. This screen reads the raw rows rather than a merged, resolved view — so you always see exactly what you'd be replacing, not just what's currently in effect.

2. Search for the key you want to change

Use the search box to filter by key. If you don't already know the exact key, the platform default text beside each row is usually enough to recognize which one you're looking at.

3. Override one language at a time

Click "Override" (or "Edit," if you already have one) next to a specific language row. The editor opens pre-filled with your current text if you have an override, or the platform's own text if you don't — so you're always editing from a real starting point, never a blank box.

4. Save replaces exactly that one row

Each save touches one (key, language) pair and nothing else. Overriding your Hebrew greeting text doesn't touch your English one, and doesn't touch any other key at all — there's no whole-table publish here that could accidentally revert something you changed last month.

5. Remove an override to go back to the platform's wording

Removing an override isn't the same as setting it to an empty string. Empty text would publish as empty text; removing the row goes back to inheriting whatever the platform ships — including any future improvement the platform makes to that string.

A key with no override shows an "Inheriting" badge rather than a blank cell, so it's always clear which of your strings are genuinely your own wording and which are quietly following the platform's.