Landing draft and publication

Autosave

Block changes are saved automatically. The header indicator shows the current state: saving, saved draft, published version, conflict, or error.

Complete button setup means that the selected action is missing a label, segment, channels, or valid link. Open that button's settings, complete the required fields, and select Apply. Autosave then continues.

Collaborative editing

The collaborative editing indicator shows people with the landing open and recent automated changes. An agent action shows its name and AI badge; applications, API calls, and system actions show their source.

When another member opens a specific block's settings, their avatar appears on the block. Select it to see the name and explanation. If you can access project members, an Open member link is also available. The avatar reports presence but does not lock the block.

Changes to different blocks are merged automatically.

Edit conflict

If two editors change the same block or block order, autosave stops while local changes remain on screen. Open the indicator and compare your version with the server version:

• Keep mine saves the local version of conflicting blocks and order;
• Accept server replaces only conflicting parts with the server version;
• independent changes from both versions remain.

The available recovery action depends on the reason. Retry saving after a lost connection. Use a full data refresh only when you are ready to replace unsaved local edits with the server version. For a permission error, check leads.manage; for invalid data, check required block and button fields.

Publication and history

An autosaved draft is not yet visible to visitors. Select Publish to make the current version public. Visitors continue seeing the previous publication until this succeeds.

Publication history lets you open an earlier version, restore its content to the draft, pin an important version, or unpin it.

If publication fails, the cabinet shows the reason. Retry submits the same draft again.

An agent subscription page has no separate publish button; its changes take effect when the agent is published.