Home/HighLevel/Features/Account Snapshots/HighLevel protected assets: reuse and sharing in snapshots

Workflows and Automation

HighLevel protected assets: reuse and sharing in snapshots

In short

Protected assets imported into an agency can now be used in any subaccount or snapshot without restriction. The assets remain locked only when a snapshot is shared outside the agency, ensuring the original creator's rights are preserved while giving internal teams full flexibility.

AreaAccount Snapshots · Snapshots
Used forInternal template library, Workflow reuse, Automation refresh
Setup steps12 steps in 3 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners, can reuse imported protected assets across all client subaccounts without extra steps.
  • Marketing teams, can build new client accounts using existing protected assets while staying compliant.
  • Product managers, can refresh snapshots with protected assets to keep internal templates up to date.

02Protected assets snapshots, explained

The feature lets you include assets that were previously marked as IP protected in any snapshot you create or refresh inside your agency. When you start a snapshot creation or refresh, those assets appear in the asset list with a green shield icon, indicating they are usable internally.

If you attempt to share a snapshot that mixes protected and regular assets, HighLevel shows a review screen titled “Some assets can’t be shared.” The screen lists how many assets are protected and will be excluded, and lets you expand each group to see individual asset labels. Only the shareable assets are transmitted to another agency.

In the Snapshots overview, any snapshot containing protected assets displays a shield indicator. Hovering over the shield reveals a tooltip that the snapshot’s assets cannot be redistributed, giving a quick visual cue.

03How businesses use protected assets snapshots

  • Internal template library. A team imports a protected email template, builds a snapshot that includes the template, and then uses that snapshot to set up subaccounts for multiple clients. The template stays usable within the agency but is not shared outside.
  • Workflow reuse. Agents create a snapshot containing a protected workflow, share the snapshot with other agents in the same agency, and the system automatically excludes the protected workflow while sharing the rest of the snapshot.
  • Automation refresh. A consultancy refreshes an existing snapshot that has a protected onboarding automation. The refreshed snapshot shows the protected assets with a shield, allowing the team to reuse the automation in new client subaccounts.

04How to set up and use protected assets snapshots in HighLevel

Building or refreshing a snapshot with protected assets

  1. Start the creation or refresh process for a snapshot.
  2. View the asset list where protected items appear with a green shield icon.
  3. Hover over the shield to see the tooltip that the asset is usable in your agency but excluded from sharing.
  4. Select the protected assets you want to include and finish building the snapshot.

Sharing a snapshot that contains protected assets

  1. Initiate the share action for the chosen snapshot.
  2. Review the “Some assets can’t be shared” screen that shows counts of protected and shareable assets.
  3. Expand each asset group to see individual items labeled Shareable or Restricted.
  4. Confirm the share, knowing only the shareable assets will be sent.
  5. Complete the sharing process.

Identifying protected (non redistributable) snapshots

  1. Open the Snapshots list in HighLevel.
  2. Look for the shield indicator on snapshots that contain protected assets.
  3. Hover over the shield to read the tooltip confirming the assets cannot be redistributed.

05What it looks like in HighLevel

06Things to know before you rely on it

  • Protected assets can be reused only inside the agency; sharing or reselling them to another agency remains blocked.
  • When a snapshot mixes protected and non protected assets, only the protected items are excluded from the share.
  • The shield icon and tooltip provide visual indication of protection status on assets and snapshots.

07How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Wondering if you can finally get value out of those protected assets without worrying about being blocked? The good news is you can now pull those assets into any subaccount or new snapshot inside your agency and use them as you see fit.

The only thing you still can’t do is pass them outside your agency, which keeps the original creator’s rights intact.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about protected assets snapshots.

Can I reuse protected assets in other subaccounts within my agency?

Yes. Once imported, protected assets can be used across any of your subaccounts and snapshots as long as they stay inside the agency.

Is sharing a snapshot with protected assets allowed?

You can share the snapshot, but any protected assets are automatically removed from the share. Only the shareable assets are transmitted.

How do I know which assets are protected before sharing?

During the share process HighLevel shows a “Some assets can’t be shared” review screen that lists each asset as Shareable or Restricted.

Does the protection follow assets when I move them between subaccounts?

Yes. Protection travels with the assets wherever they move inside the agency, ensuring the system always knows which items are protected.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.