Managing widgets

A widget is a saved workspace resource. A dashboard contains placements of that resource: its position, size, and optional dashboard-only title or frame. This means one widget can appear on several dashboards, or more than once on the same dashboard, while keeping one canonical data and style definition.

Find and understand a widget#

Open Widgets beside Dashboards. The card grid shows saved widgets rather than the chart-type catalog. Its compact top toolbar keeps the filters and creation action together; choose the search icon to expand search. Search matches names, widget types, tags, and source details, while filters narrow the list to Charts, Controls, BankSync widgets, Custom widgets, or your drafts.

Each card gives you the information needed before opening it:

• the widget icon, name, and meaningful status;
• its primary feed, bank, table, or query, plus any additional sources;
• the number of transformations applied to its data;
• the widget type; and
• its total source-and-dashboard dependency count.

Every widget shows an icon: the one you picked, or else its kind's own drawn icon (each chart, KPI, table, control, and native widget kind has one). To pick a different icon, click the icon beside the widget's name in the inspector. The picker leads with Widgets, Charts, Visuals, and Controls tabs of drawn icons, followed by other icons and emoji.

Editors can drag cards to set the workspace-wide order while All is selected and search is empty. Ordering pauses during filtering so hidden widgets never move unexpectedly.

Preview and configure#

Select a card to open its responsive detail pane. Existing widgets always open on Preview. A newly created data-bound widget opens on Data for its first setup.

The tabs have distinct jobs:

• Preview renders the real widget in a dashboard-faithful frame. It opens at Full width; choose a common size or resize the frame directly, then add another placement to a dashboard when it is ready.
• Data chooses feeds, live banks, tables, queries, fields, and transformations.
• Style changes the canonical widget presentation.
• Share controls visibility and truthful publish/embed capabilities.
• Dependencies shows every upstream source and every dashboard placement.
• Advanced contains diagnostics, identifiers, deletion, and custom-widget studio actions.

Routine edits autosave. The header shows Saving, Saved, or an error state using the same treatment as feeds and enrichments.

Editing from a dashboard works a little differently. A widget used on only one dashboard saves in place. For a widget used on several, the dashboard's inspector shows "Used on 3 dashboards. Changes apply here only." Edits made that way give this dashboard its own copy, named "… (local)", and leave the other dashboards alone. Choose Change everywhere in that notice to edit the shared widget instead.

Reuse a saved widget#

From Preview, choose Add to dashboard, then select one eligible dashboard. BankSync places it in the next available space. Repeat the action to add another placement; every placement remains independently movable, resizable, lockable, and removable.

Inside a dashboard, the compact Add a widget pane remains available. Choose Browse all for the larger catalog, with Create, Saved, and Packages tabs. Both show the same cards, so names, icons, previews, and the Soon, Beta, and Needs data badges stay consistent. See Adding widgets.

Dependencies and deletion#

Dependencies are grouped into:

• Reads from: feeds, banks, tables, queries, derived/static nodes, and custom-widget inputs, including missing or permission-needed states.
• Used in dashboards: each dashboard with its individual placements and title overrides.

A widget that is still in use cannot be moved to trash, even when the only dashboard using it is itself in trash. The refusal names the dashboards you can see ("Used on 2 dashboards: …") and adds "and others you can't see" without a number when some are hidden from you; an admin sees them all. The confirmation dialog offers View dependencies so you can open each dashboard and remove or replace its placements explicitly. Removing a placement never deletes the saved widget. Once no dashboard uses it, Move to trash from Advanced: the widget leaves the library and pickers, its widget tokens and embeds stop working, and you can Restore it for 30 days or Delete forever.

Custom widgets#

Custom widgets use the same cards, Preview, Data, Style, Share, and Dependencies experience. Choose Open studio for source code, Setup, Contract, builds, generated fixtures, and sandbox diagnostics. Closing the studio returns to the widget's Preview-first resource pane.

Custom packages keep their existing version, binding, consent, and grant rules; the Widgets tab does not create a second runtime or permission path.

Related guides#

• Dashboards & Widgets Overview
• Adding widgets
• Binding data
• Custom-widget data and permissions