Snapshots

Be able to view an account and see what snapshots are active with the ability to pause or delete them from the account.Be able to refresh a snapshot while pausing the refresh on certain accounts.See what actions were initiated in the account from a snapshot refresh with the ability to undo or delete certain actions. HIGHLVL-I-1444

should go non-stop adding folders & sub-folders anywhere that could get more than 8 items I just started and already have 16 snapshots and it doesn't even organize alphabetically so nearly impossible to figure out what I have and just got a list of over 30 snapshots for dif niches and would be ridiculous waste of time to add even 1/4th of them ... when could be SO SIMPLE WITH FOLDERS

Today agencies have to simulate “sandboxes” by creating extra sub-accounts and manually juggling snapshots just to test changes safely before touching a client’s live environment. This works, but it’s fragile and time‑consuming, and a single mistake (editing the wrong sub-account or pushing the wrong snapshot) can break critical workflows or trigger unwanted emails/SMS to real contacts. ~ https://4spotconsulting.com/highlevel-sandbox-setup-for-agencies-a-step-by-step-development-guide I’m proposing a native sandbox feature for sub-accounts, similar in spirit to how other platforms handle staging vs production, and similar to the existing developer sandbox concept HighLevel already uses for Marketplace apps. ~ https://marketplace.gohighlevel.com/docs/oauth/SandboxAccount CORE IDEA: A first‑class “Sandbox” mode for any sub-account that lets agencies: Create Sandbox from Live - One‑click create a sandbox from an existing sub-account. - Clone configuration and assets (workflows, funnels, forms, pipelines, custom fields, triggers, settings), but not sensitive data like contacts, conversations, payments, and real messages. - Clearly label this environment as a sandbox in the UI to avoid confusion. Configure & Test Safely - Build and modify workflows, funnels, and automations in the sandbox without any risk to production. - Run structured tests with dummy contacts and test data, including integrations and webhooks, to validate end‑to‑end flows. - Optionally enable Labs / new features in the sandbox first, before enabling them on the live account. Compare & Deploy Changes to Live - See a clear difference between sandbox and production: new assets, changed assets, deleted assets. - Choose what to promote (e.g. specific workflows, pipelines, email templates) with conflict handling options: overwrite, keep both (rename), or skip. - Run deployment as a guided process with a final confirmation summary to reduce “fat‑finger” mistakes. Archive or Destroy Sandbox - After successful deployment, easily archive or delete the sandbox environment with one click. - Optionally keep a limited history of sandbox snapshots for rollback. WHY THIS MATTERS Reduces support load and emergencies Fewer accidental broadcasts, broken workflows, and “something just stopped working” tickets caused by tweaking live systems directly. 4spotconsulting Encourages best practices Agencies that care about quality are already building their own sandbox processes with extra sub-accounts and snapshots. A native feature would standardize this and make it accessible to more users, not just power users. 4spotconsulting Safer experimentation and faster iteration Agencies could confidently adopt new features, try new offers, and refactor complex automations without risking revenue‑critical client accounts. Aligns with existing direction HighLevel already recognizes the need for isolated environments via developer sandboxes for Marketplace apps. Extending this concept to agency sub‑accounts would be a natural next step and a big differentiation vs competitors. ideas.gohighlevel Nice-to-haves (future enhancements) API access to create/destroy sandboxes and trigger deployments, so advanced agencies can bake this into CI/CD‑style workflows. Permissions so only certain roles can create / deploy from sandboxes. Ability to schedule deployments during low‑traffic windows. This feature would make HighLevel significantly safer and more “enterprise‑ready” for agencies running complex, high‑volume automations, while also making life easier for smaller agencies that want guardrails without having to invent their own sandbox process.

A snapshot for musicians, to catch some of that solopreneur artist/record-label bread they're not catching

Give the ability on the sub-account manager level to see which snapshots have been installed and with a click, remove all assets connected to that snapshot. This would allow for easier account cleanup one accounts become cluttered. Additionally, it would protect agencies from intellectual property/asset leakage when accounts want to sub-account transfer to another agency. An additional connected feature would be the ability to see in the snapshot manager, which sub accounts have that snapshot, and remove from there as well.

We need a "button" that allows us to back up an entire account - contacts, triggers, forms, campaigns, websites, etc.... and a way to restore in case of a major mistake or accidental delete of account. Had a potential client ask about it, kind of felt I was caught flat footed. HIGHLVL-I-1619

Create an option here where you can Duplicate the sub-account, maybe it pops up the same box that it does when you load a snapshot so you can select what to do duplicate and what not...

Include smart lists in snapshots so customers have the ease of pre-customized lists to see their leads in different segments. HIGHLVL-I-2111

So instead of loading in a flow and having to select and found out all the things that are associated with the flow. Have it automatically check off all the custom fields, tags, other workflows etc that are associated with it.

Include Communities and all courses listed on a community in Snapshots so we can sell a premade community that has courses already listed, so the new owner of the community can sell the courses to his member.