User Alert Notification

User alerts notify collaborators when changes are made to a shared dashboard, preventing simultaneous edits from overwriting each other's work.

The User Alert Notification helps avoid conflicting edits when multiple users work on the same dashboard. When one user saves, others currently editing are prompted to accept or deny the new changes.

No additional setup is required—alerts appear automatically during concurrent editing.

How it works (at a glance)

  1. User-A saves the dashboard.

  2. The system saves User-A’s updates.

  3. All other active editors (e.g., User-B, User-C) see an Alert Notification.

  4. Each editor must choose:

    • Accept (Yes) — acknowledge the new version.

    • Deny (Cancel) — keep editing their current copy.

Respond to an alert

Option 1: Accept (Yes)

  • Your editing session closes.

  • When you reopen the dashboard, it includes User-A’s saved changes.

Option 2: Deny (Cancel)

  • You continue editing your current session.

Example scenario

  • A dashboard is shared with User-A, User-B, and User-C.

  • User-A saves changes → system commits User-A’s updates.

  • User-B gets an alert and acceptsUser-B’s session closes; reopening shows User-A’s changes.

  • User-C denies the alert → continues editing. If User-C later saves, those changes overwrite User-A’s version.

Best practices

  • Prefer “Accept” if you are unsure—this prevents accidental overwrites.

  • Use Save As to branch your work (e.g., Copy_of_<name>When you need to keep both versions.

  • Coordinate with collaborators (chat or comments) before saving large or breaking changes.

  • Save frequently to minimize loss during conflict resolution.

Notes:

  • When navigating via the tour or menus to a dashboard, the Dashboard Canvas opens for the selected item, and standard alert behavior applies.

  • Overwrites follow a last-writer-wins behavior if users deny the alert and then save.