Home/HighLevel/Features/Account Snapshots/HighLevel granular snapshot permissions: how admins manage access

Workflows and Automation

HighLevel granular snapshot permissions: how admins manage access

In short

Granular permissions for Snapshots let administrators decide which users can view, create, edit, share, push, refresh, or delete snapshots. By toggling these rights per team member, businesses can tighten security, meet compliance rules, and align access with job responsibilities.

AreaAccount Snapshots · Snapshots
Used forDigital marketing agency, Compliance consulting firm, Software as a service startup
Setup steps7 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners can limit snapshot actions to senior staff, protecting client assets.
  • Compliance officers can restrict Delete Snapshot rights to prevent accidental loss.
  • Product managers can grant Create Snapshot permission to team members building new templates.

02Granular permissions for snapshots, explained

The feature adds permission controls to the Snapshot workflow inside HighLevel. Each snapshot action, view, create, edit, share/import, push, refresh, delete, can be turned on or off for any user. Permissions are managed from the Settings area under the Team section.

When an admin updates a user’s Snapshot Scopes, the platform enforces those choices in real time. A user without the Create Snapshots right cannot generate new snapshots, while a user with only View Snapshots can browse existing ones without making changes.

All changes are saved with a single click, and the new settings apply to every snapshot operation the user attempts thereafter.

03How businesses use granular permissions for snapshots

  • Digital marketing agency. The agency admin enables View and Create permissions for junior account managers while reserving Edit, Push, and Delete rights for senior strategists. This keeps client campaign structures safe while allowing assistants to build new snapshots.
  • Compliance consulting firm. A compliance lead grants only View and Refresh permissions to analysts, preventing them from accidentally deleting or pushing snapshots that contain regulated data.
  • Software as a service startup. The product team assigns Share/Import and Edit permissions to developers who need to move snapshot configurations between staging and production subaccounts, while restricting Push and Delete to the DevOps manager.

04How to set up and use granular permissions for snapshots in HighLevel

Manage snapshot permissions

  1. Open Settings from the main navigation menu.
  2. Select Team to list all team members.
  3. Choose the user whose snapshot rights need adjustment.
  4. Click the Edit User Option button.
  5. Scroll to the Snapshot Scopes section.
  6. Toggle each snapshot permission on or off as required.
  7. Press Save Changes to store the new settings.

05What it looks like in HighLevel

06Settings that matter

  • Snapshot Scopes. Defines which snapshot actions a user can perform, such as view, create, edit, share/import, push, refresh, and delete.

07Things to know before you rely on it

  • The article does not list any specific limits or beta annotations for these permissions.

08How it connects to the rest of HighLevel

Michael's take

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

Granular permissions for snapshots feel like a small but useful convenience. They let you tighten who can touch each part of the snapshot workflow without overhauling anything else. That extra control can keep a team from stepping on each other's toes.

A boutique marketing agency that builds client dashboards for each brand will find it handy. The creative lead can create and edit snapshots, while the account manager only needs to view and share them. The agency can lock down Push and Delete actions to senior staff, keeping the data safe.

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

Common questions

Common questions about granular permissions for snapshots.

Can I give a user only the ability to view snapshots?

Yes. In the Snapshot Scopes section you can enable the View Snapshots permission while leaving all other actions disabled.

What happens if I turn off the Delete Snapshots permission for a user?

That user will no longer see the option to permanently remove snapshots, protecting them from accidental deletions.

Do these permissions apply to both existing and new snapshots?

Permissions are enforced on every snapshot action, regardless of when the snapshot was created.

Is there a way to grant all snapshot permissions at once?

You must toggle each permission individually; the interface does not provide a single ‘grant all’ switch.

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.