You got it. Here is the feedback item with all Markdown formatting (headings, bolding, bullet points, horizontal rules) removed, leaving only plain text and standard line breaks. Title: Allow Sub-Accounts to Opt-Out of Specific Snapshot Updates (Funnel/Element-Level Control) Detailed Explanation This feature request is critical for agencies and users who deploy Snapshots to multiple sub-accounts and need to manage subsequent updates without overriding client customizations. The core need is a mechanism to control the distribution of updates from the original Snapshot, allowing sub-accounts to "opt-out" of receiving specific, element-level updates. Current Problem/Use Case: An agency deploys a Snapshot to dozens of sub-accounts. Later, the agency makes an improvement to one specific element within that original Snapshot (e.g., a performance optimization to a Funnel, an update to a Workflow, or a compliance change to a Form). The agency needs to push this improved element to accounts that haven't modified it. However, some sub-accounts have already edited, modified, or customized their version of that element. Pushing the global update would override their custom work, leading to frustration and lost effort. Other sub-accounts have not touched the element and would benefit greatly from receiving the new, improved version. Without an opt-out or tracking mechanism, the agency must choose between manual, non-scalable updates or risking customer dissatisfaction by overriding valuable custom content. Proposed Solution Details: The system's default behavior should be that sub-accounts are connected to receive updates. They would only need to opt out if they desired. Opt-Out Functionality: Provide a simple toggle or setting within the sub-account that allows them to opt out of receiving updates from the parent Snapshot for specific elements. Granularity: The opt-out should be granular, ideally at the: Element Level: Allowing the account to opt out of updates for a specific Funnel, Workflow, Form, etc., while still receiving updates for all other unedited components. Optionally: An Account-Wide opt-out could exist for a complete severance from all future Snapshot updates. Agency Visibility/Control: The platform should track which elements have been modified by the sub-account since the last update/install. When the agency initiates a Snapshot Update Push, the system should allow us to select which accounts to exclude based on those who have edited the specific component or those who have manually opted out. Implementing this would allow agencies to confidently maintain and upgrade their Snapshot elements for new or non-customized users, while safely protecting the custom work of their established clients.
