Reuse Protected Snapshot Assets Within Your Agency

TL;DR

Agencies can now reuse protected assets from snapshots across their own sub-accounts without restriction. HighLevel has not indicated any action required by agency owners.

Who this affects

This update affects GoHighLevel agency owners who use protected assets in their snapshots, or who import protected assets from other creators. Agencies that create or use protected snapshot assets for their own client sub-accounts will find this relevant.

What changed

HighLevel has rolled out changes to how protected assets within snapshots are handled.

Key changes include:

• Protected assets that have been imported into an agency can now be used across any sub-account within that agency.
• New snapshots can be built using these imported protected assets without any restrictions on their internal reuse.
• It is not possible to share or resell protected assets to another agency.
• When sharing a snapshot that contains both protected and non-protected assets, only the eligible non-protected assets are shared.
• The protected assets in such a mixed snapshot are excluded from the external share.
• It is possible to identify which assets within a snapshot are protected before proceeding with sharing.
• The protection status of an asset is preserved, whether it is imported, reused in another snapshot, or loaded into a different sub-account.

HighLevel has not confirmed any limits or plan gating associated with this feature. HighLevel has not confirmed the rollout status for this feature.

Where to find it

HighLevel has not published the exact location for this feature. Based on the description, the functionality will likely be visible when managing snapshots, specifically during the creation, import, or sharing processes of snapshots. Users might find indicators of asset protection status and options for internal reuse within the snapshot editing or sharing interfaces.

How agencies will use this

An agency owner might subscribe to a protected snapshot from a HighLevel expert for a specific niche, for example, a dental office workflow. This protected snapshot could contain custom forms, specific funnels, or specialized workflow automations that the expert wishes to protect from being resold by agencies. Under the previous system, the agency owner might have had difficulty replicating or adapting these protected elements for different sub-accounts within their own agency. Now, if the agency owner takes this protected snapshot, they can internally duplicate its protected forms or funnels to deploy them across multiple dental office sub-accounts they manage. For instance, the agency can import the 'Dental Patient Onboarding' workflow. They can then create a new sub-account for 'Dr. Smith's Dental Practice' and load this workflow directly. Later, when onboarding 'Sunshine Dental Clinic,' they can reuse the exact same protected 'Dental Patient Onboarding' workflow without having to re-import or rebuild it, ensuring consistency and efficiency across their client base. The underlying protection by the original creator still prevents the agency from exporting or selling this 'Dental Patient Onboarding' workflow to another agency.

Our take

This is a major update for agencies that rely on protected content from third-party snapshot providers or create their own. It addresses a significant friction point for internal agency operations: the inability to easily leverage protected assets across multiple client sub-accounts. Agencies can now scale the deployment of protected IP within their own structure without compromising the creator's protection. This is a practical improvement for operational efficiency, removing a previous restriction that complicated internal asset management.