Skip to content
  • There are no suggestions because the search field is empty.

Edit‑Locking & Version Conflict Prevention in the Visual Editor

Keep your team productive—and your experiments safe from accidental overwrites.

THIS ARTICLE WILL HELP YOU

Overview

The Visual Editor enables multiple teammates to collaborate on the same experience simultaneously. When another teammate makes recent changes, the editor automatically detects them and prompts you to Reload or Overwrite & Save to prevent overwriting or losing work. 

To review detailed edit history, including what changed and who made the changes, use Change History at the experiment level.


Source: Track User Changes with Change History

How version safety works

The 30-second conflict window

  • When User A saves (or makes a change), there’s a ~30-second window during which a conflicting edit by User B will trigger an overwrite/reload dialog.

  • If User B doesn’t edit during those ~30 seconds, they’ll see a “Changes detected—Reload” popup (informational). If they later edit and try to save against the older state, they’ll then get the Overwrite & Save dialog.

What you’ll see and when

Scenario What you see What happens now
You make a change and someone else also changes within ~30s Conflict dialog Overwrite & Save (your changes replace the latest) or Reload (pull in teammate’s changes)
Someone else changed ~30s ago, you haven’t edited yet “Changes detected—Reload” popup Reload (recommended) or continue browsing
You ignored the popup, then edit and try to save Conflict dialog Overwrite & Save or Reload
Background updates detected while you edit Prompt to sync Reload now, or proceed and decide at save time with the conflict dialog

‼️ IMPORTANT:

Overwrite & Save replaces the most recent server version with your current draft. Coordinate with teammates and review Change History when in doubt.

Typical collaboration flows

  1. Both editing at once (near-simultaneous)
    1. A saves → within ~30s, B edits and saves → B gets conflict dialog → B chooses:
      1. Reload to pick up A’s latest, or
      2. Overwrite & Save to keep B’s version.
  2. You’ve been idle; teammate updated
    1. You return to the editor and see a Reload popup.
    2. Click Reload before making big changes to avoid conflicts at save time.
  3. You’re mid-edit; teammate updated
    1. You may see a prompt to Reload. If you continue, the conflict dialog will appear when you try to save.

Best practices for teams

  • Sync before long sessions: Click Reload when you come back from a break.

  • Announce big edits: A quick chat note helps reduce conflict prompts.

  • Name variations clearly: e.g., Hero-CTA-Alice clarifies ownership during active work.

  • Clone for major redesigns: Keep production drafts stable and iterate in a safe copy.

  • Use Change History to audit: Verify who changed what and when before deciding to overwrite.


FAQ

Does collaboration mode affect live traffic?
No. Prompts and dialogs only affect the editor. Visitors continue to see the currently published version.

When exactly will I see a dialog vs. a popup?

  • Dialog (Overwrite & Save / Reload): You edited within ~30s of another user’s change, or you’re saving against an older version.

  • Popup (Reload): Another user changed the experience ~30s ago and you haven’t edited yet.

What does “Overwrite & Save” do?
It saves your current draft and replaces the most recent server version. Coordinate with your teammate and review Change History if you’re unsure.

Can I disable this behavior?
No. Version-safety prompts are part of the editor and protect team workflows by preventing silent overwrites.

Where can I review past edits?
Open Change History at the project or experiment level to see who changed what and when.