Granular Snapshot Permissions in GoHighLevel

ClickUp users who migrate to GoHighLevel often ask how to control who can edit, share, or delete key assets inside a snapshot. This guide explains the granular snapshot permissions available so you can safely manage access while still giving your team and sub-accounts the tools they need.

Granular permissions for snapshots give you fine-tuned control over what locations and users can do with the assets that were originally packaged inside a GoHighLevel snapshot. Instead of granting full access to everything, you can specify restrictions at the asset and feature level.

What Are Snapshot Permissions in GoHighLevel?

Snapshots in GoHighLevel are collections of assets such as funnels, websites, workflows, forms, and pipelines that you can deploy into one or more sub-accounts. Granular permissions extend this concept by letting you decide what happens to those imported assets after deployment.

Using these permissions, you can:

• Prevent locations from deleting important snapshot assets.
• Control whether locations can update or edit certain items.
• Restrict who can share assets outside the account.
• Ensure key workflows and templates remain consistent across accounts.

This is especially helpful for agencies that use GoHighLevel to deliver standardized setups to many clients while maintaining control over intellectual property.

Where to Find Snapshot Permissions in GoHighLevel

To use granular permissions, you first need to open a snapshot inside your GoHighLevel agency view.

1. Log in to your agency account.
2. Navigate to the Snapshots section.
3. Select the snapshot whose permissions you want to configure.
4. Open the snapshot settings or management panel where permissions are listed.

From there, you will see a range of switches or options that control whether specific actions are allowed on each asset category.

Key Permission Types Available in GoHighLevel

The granular snapshot permissions in GoHighLevel can typically be grouped into a few major types of controls. While exact labels may vary slightly in the interface, they will fall into the categories below.

Editing Permissions in GoHighLevel Snapshots

Editing permissions manage whether locations or users can change assets that were created from a snapshot. Common settings include:

• Allow editing of funnels and websites – Lets locations modify pages, sections, copy, and design elements.
• Allow editing of workflows – Enables changes to triggers, actions, and automation logic.
• Allow editing of forms and surveys – Permits updates to fields, styling, and submission settings.
• Allow editing of pipelines – Controls whether stages and pipeline structure can be modified.

If you disable editing for a particular asset type, the items imported from the snapshot will either be read-only or locked from certain changes, depending on the feature.

Sharing Permissions for GoHighLevel Assets

Sharing permissions control whether assets that originated from a snapshot can be exported, cloned, or shared as new snapshots or templates. This helps protect your agency assets inside GoHighLevel.

Typical options include:

• Allow sharing of funnels or websites – Determines if a location can share pages to other accounts.
• Allow sharing of workflows – Governs whether automations can be exported or re-packaged.
• Allow sharing of templates – Manages sharing rights for email templates, SMS templates, and similar assets.

Turning off sharing permissions is a common best practice when you want clients to use your frameworks but not redistribute them.

Deletion Permissions in GoHighLevel Snapshots

Deletion permissions decide whether snapshot-generated assets can be removed by locations or users.

• Allow deleting funnels, websites, or pages – When disabled, critical sales funnels remain in place.
• Allow deleting workflows – Prevents users from removing automations that are essential to their campaigns.
• Allow deleting forms, surveys, or pipelines – Protects your structure from accidental or intentional cleanup that would break processes.

Granular deletion controls are vital if you deploy a complete operating system for your clients and want to guarantee that core elements are not lost.

How to Configure Granular Permissions in GoHighLevel

Once you know which actions you want to allow, you can configure the granular settings in a few clear steps.

Step-by-Step: Setting Snapshot Permissions

1. Open the snapshot
   In your agency dashboard, go to Snapshots and select the specific snapshot to manage.
2. Access the permissions panel
   Look for a Permissions, Access Control, or similar tab within the snapshot settings.
3. Review asset categories
   Identify each category covered by the permissions, such as funnels, workflows, templates, calendars, forms, or pipelines.
4. Toggle edit, share, and delete rights
   For each category, switch on or off the ability to edit, share, or delete snapshot-derived assets according to your policy.
5. Apply or save changes
   Save your configuration so that new locations created from this snapshot inherit your updated permissions.

These settings typically apply to new deployments of the snapshot. If you change permissions later, verify how they affect existing locations and assets.

Best Practices for Using GoHighLevel Snapshot Permissions

To get the most from granular permissions, follow these recommended practices when working inside GoHighLevel:

• Lock core frameworks – Disable deletion and often editing on critical funnels, workflows, and pipelines that define your core offer.
• Allow customization where safe – Keep editing enabled on assets like copy, branding, and some templates so clients can personalize without breaking systems.
• Restrict sharing for proprietary systems – Turn off sharing permissions for unique frameworks that differentiate your agency.
• Document your rules – Share clear guidelines with your team so they understand which assets can be modified and why.
• Test a pilot location – Before rolling out widely, deploy the snapshot to a test account to make sure permissions behave as expected.

Troubleshooting Permission Issues in GoHighLevel

If users report that they cannot edit, share, or delete certain items, the cause is often the snapshot permissions themselves.

Common Problems and Fixes

• Asset appears locked or uneditable
  Check the snapshot settings for that asset type and confirm whether editing is disabled.
• Cannot share or export an asset
  Verify that sharing permissions are turned on for the relevant category.
• Unable to delete unwanted items
  Make sure delete permissions are enabled, or consider creating a version of the snapshot with more flexible controls for advanced users.

If configuration seems correct but issues persist, compare the behavior with another location or create a new sub-account from the same snapshot to confirm whether the problem is account-specific.

Additional Resources for GoHighLevel Snapshots

For a deeper dive into the original documentation on granular permissions for snapshots, you can review the official help article from the platform here: Granular permissions for snapshots.

If you need expert implementation, strategy, or help designing scalable snapshot frameworks, you can also explore consulting and implementation services at Consultevo.

By understanding and configuring these granular controls, you can use GoHighLevel snapshots to deploy consistent systems at scale while ensuring that every client account has the right balance between flexibility and protection.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.

Scale GoHighLevel

“`