Widgets settings reference

Last updated: August 16, 2026

Every control on the Widgets settings page, grouped by its section. For the end-to-end setup, see embed a Nash widget on your site.

Find the page under Settings ▸ Connections ▸ Widgets.

Note

You'll need organization-management permissions to open and edit Widgets.

Which widgets you can turn on, and whether Nash has paused one, are decided by Nash on the server — the page reflects that state rather than setting it. The same is true of embed sessions: session minting, the 15-minute session cap, and rotation wind-down timing are enforced by Nash. Labels and defaults below are what the page shows.

Widget catalog

Each row has a name, a description, an On/Off switch, and — for a widget with a published snippet that's turned on — an Embed snippet copy link. The catalog and allowed origins save together with the Save changes bar.

Widget What it embeds Embeddable today?
Live Map Live courier positions and planned routes on an embedded map Yes — shows an Embed snippet link when on
ETA Chip A compact inline arrival time for one delivery No — can be turned on, but produces no snippet yet
Delivery List A list of deliveries with status, ETA, origin, and package count No — can be turned on, but produces no snippet yet
Delivery Details A focused single-delivery summary (courier, arrival, stops, packages) No — can be turned on, but produces no snippet yet
Nash Agent The AI assistant customers talk to about their orders and deliveries Configured per agent, not here — see what Nash Agent is

Only Live Map yields a copy-paste embed snippet. ETA Chip, Delivery List, and Delivery Details carry a New badge and can be switched on, but there is no snippet to hand out for them yet. Nash Agent's embeds are set up on each agent's own Embed tab and are unaffected by the switch here.

An On the roadmap footer lists candidate widgets as name chips with no switches — none are built yet.

Paused by Nash

When Nash temporarily pauses a widget, its row shows a Paused by Nash badge and a strip. Your own On/Off setting is unchanged and preserved; the widget just won't serve until Nash lifts the pause. Only Nash can lift it — the strip has a Contact Nash support button. Whether a widget is paused is server-driven.

Allowed origins

The exact web origins allowed to embed a widget. An embed session is minted only for pages on a listed origin — enforced by Nash.

Rule What it means
Exact origin only scheme://host, plus a port only if non-default (https://shop.example.com).
Scheme required http:// and https:// are different origins; a bare host is rejected.
No path, query, or fragment Authorization is per origin, not per page. A trailing slash is trimmed.
No wildcards *.example.com can't be authorized — add each subdomain on its own.
No duplicates An origin already on the list can't be added again.

Adding and removing origins lands in the shared draft and writes on Save changes. Removing a saved origin asks you to confirm; after it saves, new sessions stop being minted for that origin and running sessions finish out — up to 15 minutes (server-enforced). This list is separate from the Nash Agent per-agent domain allowlist, which accepts bare hosts and *. wildcards.

Embed credentials

Long-lived secrets your backend exchanges for short-lived embed sessions (15 minutes at most). The secret belongs on your server; the browser only sees the session. These actions commit immediately — they are not behind the Save bar.

Statuses

Status What it means Has row actions?
Active Working now. Yes — Rotate, Rename, Revoke
Retiring An active credential winding down after a rotation; works until the shown expiry, then stops. Yes
Expired A wound-down secret whose window has passed. No — terminal
Revoked Stopped immediately, no undo; hidden by default behind Show revoked. No — terminal

Lifecycle actions

Action What it does
Issue credential Name it, then copy the one-time secret. Shown once; Nash stores only a hash.
Rotate Replace the secret. Wind down the old one for 60 minutes (recommended) or retire it immediately. Reveals the new secret once.
Revoke Stops the credential immediately. No wind-down, no undo.
Rename Cosmetic — the secret and status don't change.

Save vs immediate commit

Two write models coexist on the page:

  • Widget catalog + allowed origins share one draft. Edits mark the page as having unsaved changes and nothing is written until you select Save changes; both sections save together. Leaving the page while dirty prompts you first.
  • Embed credentials commit immediately. Issue, rotate, revoke, and rename each take effect the moment you confirm — never behind the Save changes bar.

Related