This update adds a safeguard when you enable SaaS for a sub-account and attach a snapshot.

What changed

If the snapshot would overwrite anything you have already customized in the sub-account, you will see a warning before changes are made. You can then choose to keep your existing assets or overwrite them with the snapshot’s version. If there is no conflict, the snapshot applies as usual.

Why this matters

Previously, attaching a snapshot could overwrite funnels, websites, or other assets you had already updated in a sub-account without warning. This change makes conflicts visible and lets you decide what happens to your work.

Notes

• This applies to both SaaS V1 and V2 accounts.
• For bulk SaaS enablement, attaching a snapshot is not available yet, so your existing assets are protected by default in that flow.

Coming next

• The same conflict warning and choice used in individual SaaS enablement will be added to bulk SaaS enablement once snapshot attachment is available.