Running 50+ GoHighLevel sub-accounts: catching broken automations early

By / Published Nov 17, 2026 / Updated Nov 17, 2026

Heads up: the trial and plan buttons on this page use my affiliate links. If you sign up through one I get a commission. It doesn't cost you more.

To run 50+ GoHighLevel sub-accounts without broken automations slipping through, build every account from one snapshot with the same naming rules, switch on workflow error notifications and a Messaging Error - SMS alert in each one, push a canary test contact through the main lead flow every week, and run a monthly audit with Workflow Maps, Audit Logs and the Agency Trust Center. Then lock down what clients can touch with Feature Permissions on the sub-account and Roles & Permissions on each user (as of Nov 17, 2026).

My agency, Hexona Systems, won HighLevel's Diamond SaaSpreneur award (1,000+ sub-accounts) in 2025 and 2026, so I run 1,000+ client accounts on HighLevel. At that size the problem isn't building automations. It's finding out one stopped before the client does. This page is the operations system across accounts. Fixing one workflow that won't fire is on Workflow not triggering, and failed texts are on SMS not delivering.

Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Short version

  • 01There are no agency-level workflows yet (821 votes on the ideas board). Every alert lives inside each sub-account, so put your monitoring workflows in the snapshot.
  • 02Error notifications are off by default, send at most one email every 24 hours, and only cover webhooks, premium actions and Facebook/Instagram steps. Pair them with a Messaging Error - SMS workflow.
  • 03A weekly canary test (a test contact you own, sent through the client's real form) catches the silent failures logs don't show.
  • 04Agency View > Sub-Accounts > Update features (Oct 14, 2026) changes feature access for many clients at once. Bulk Action History shows which accounts failed.
  • 05Clients can't get more access than the sub-account has. Turn features off at the sub-account, then restrict users. Agency-level granular permissions are still an open request (1,229 votes, in progress).
  • 06Audit Logs keep 60 days. Snapshot versions can't be reverted. Plan around both.

Why automations break quietly at 50+ accounts

Most breaks don't throw an error anyone sees. A client reconnects their Facebook page and the lead form trigger points at nothing. Someone on their team edits a workflow and leaves it in Draft. A number loses its A2P campaign and every text fails. A contact gets put on DND by a carrier. The builder still looks fine, and the first sign is the client telling you the leads dried up two weeks ago.

The other problem is structural. HighLevel has no agency-level workflows. The "Workflows at the Agency level" request has 821 votes and isn't built (ideas board, Nov 17, 2026). So there's no single place that watches every account. Each sub-account has to watch itself and report to you, which is why the monitoring has to ship inside your snapshot.

How I explain the setup to new agency owners: "you're essentially selling sub accounts that's what it is," and "agency is just for you to manage your own business and run your own agency out of." The agency view is where you manage. The sub-accounts are where things break.

Naming conventions that make 50 accounts searchable

Names are the cheapest monitoring tool you have. An error email that says "Workflow 14 failed" in "John Smith's Account" costs you ten minutes. One that says "LEAD | Quote form > SMS + opp" in "Acme Plumbing - Austin" costs you ten seconds.

Sub-accounts: use the business name plus a location if they have several. If you sell through SaaS mode on the $497 plan, set SaaS Configurator > Advanced Settings > Sub-Account Onboarding to Company Name, so new signups are named after the business, not "Jane Smith's Account". It only applies to new signups, so rename older ones by hand.

Workflows: start with the job, then the trigger, then the outcome, for example "LEAD | Quote form > SMS + opp", "BOOK | Appointment > reminders", "OPS | Daily health check". Put the same prefixes in every snapshot so a filter or search finds the same workflow in every client. Name the actions too. HighLevel's own doc suggests names like "Notify Sales Team - Email", and Execution Logs read like sentences when you do.

Folders: HighLevel recommends 2 to 3 levels at most. I'd keep one folder per job (Lead intake, Booking, Follow-up, Reviews, Ops) and one called "Client built" for anything the client makes, so you know what you didn't write.

Snapshots: name them by niche and date, like "Plumber master 2026-11". Version History records each refresh, but it has no revert button, so the date in the name is how you tell versions apart later.

Health-check workflows and alerts to put in every sub-account

Build these once in your master sub-account and they go out with the snapshot. Point every alert at a shared ops inbox or a Slack channel, never at one person.

  • Workflow error notifications. Automation > Workflows > Workflow Settings on the list page. Off by default. Add your ops email as a recipient, because by default it emails the sub-account admins (which may be the client). It sends at most one email every 24 hours and lists failures in the Needs Review tab. Coverage per HighLevel's 2024 doc: webhooks and custom webhooks, Slack, Array, Custom Code, ChatGPT, Google Sheets, and Facebook and Instagram steps.
  • Messaging Error - SMS. A workflow on that trigger with an Internal Notification to your ops inbox for account-level codes like 30034 (no approved A2P campaign). The full code split is on SMS not delivering.
  • A weekly reminder to test. A Scheduler-trigger workflow (say, Mondays at 9 a.m.) with a Create Task action assigned to the account manager: "Run canary test". Scheduler is contactless, so it can't send messages to contacts, but tasks, internal emails, Slack and outbound webhooks all work.
  • An optional heartbeat. The same kind of Scheduler workflow can send an outbound webhook to your own n8n with the account name every morning. If one account stops checking in, it's paused, the workflow got switched off, or someone deleted it. Setup is on GoHighLevel to n8n.

The canary contact test: catch what logs don't show

Error notifications only fire when a step errors. A form that no longer triggers anything, a calendar that isn't connected, or an SMS that never sends because of DND produces no error at all. A canary test is a fake lead you send through the real front door on a schedule and watch come out the other side. HighLevel doesn't have a canary feature, so this is a habit you build from its parts.

Set it up once per account: a contact named "zz Canary" with an email inbox and a phone your team holds, opted in, never on DND, and tagged canary so you can filter it out of the client's reports. Then every week, submit the client's main lead form (or book their calendar) as the canary. Your team can do it by hand from the Scheduler task, or an n8n flow can post the form on a timer.

Within ten minutes you should see: one contact (not a duplicate), the opportunity in the right stage, the confirmation text and email on your devices, and the internal notification to the client's team. If anything is missing, open the workflow, click the Workflow AI icon and ask "Show me the path zz Canary took through this workflow." That's Workflow AI Analytics (Nov 9, 2026), covered with the rest of the debugging tools on Workflow not triggering.

Send the canary through the same channels real leads use. If the client's leads come from Facebook lead ads, a form test won't catch a disconnected page. HighLevel's new Test Workflow (Labs) can listen for the real trigger event for 15 minutes, which helps for those.

Watching every account from one place: the Workflows API

If you have a developer or use n8n a lot, the Workflows API (Oct 28, 2026) is the closest thing to agency-wide monitoring today. It returns execution logs and statistics per step: enrollments, completions and failures, by hour, day or week. HighLevel's own example use case is a failure report: "Every Monday, count failures per step for your key workflows" and send the summary to your team.

It's per sub-account. In each one you create a Private Integration (Settings > Private Integrations) with the View Workflows and View Workflow Logs scopes, then call it with that account's token. Read-only scopes are enough for monitoring, so don't tick Edit, Publish or Delete for a reporting script.

Claude through HighLevel's MCP can do a lighter version. In my Claude Cowork video I showed it can "spot stale deals" and flag "this lead is going colder this person's uncontacted or this message is unread," and "you can set this up on a schedule as well." Setup and what it can read and write are on Connect Claude to GoHighLevel.

The monthly audit checklist

Once a month per account, or a rotating batch per week if you have hundreds. Most of it is reading screens HighLevel already built, which is quick once the naming is clean.

CheckWhereWhat you're looking for
Failed workflowsAutomation > Workflows > Workflow Maps > Review workflows with errorsAny published workflow with failed runs. Fix it in the builder. Mark as read only clears the badge.
Needs ReviewAutomation > Workflows > Needs Review tabErrors flagged by error notifications that nobody acknowledged
ClutterWorkflow Maps > Cleanup (left rail)Default names, workflows with no enrollments in 60 days, empty folders. Check for seasonal ones before deleting.
Drafts that should be liveAutomation > Workflows, filter to DraftLead, booking or follow-up workflows sitting in Draft
Who changed whatSub-account > Settings > Audit LogsFilter by User and Action Type = Delete or Update. Entries are kept 60 days, so export to CSV if you need a record.
Text failuresYour Messaging Error - SMS alerts, and the sub-account's SMS restriction history30034 or 30007 clusters, or a warning on opt-out or filtering rates
A2P statusAgency View > Settings > Phone Integration > Trust Center (A2P)Any sub-account under Rejected or stuck In Review
UsersSub-account > Settings > UsersEx-staff still active, client users with Admin they don't need
Canary resultYour Scheduler task and the canary contactDid the last test pass end to end?
Bulk changesAgency View > Sub-Accounts > Bulk Action History (clock icon)Jobs with failed accounts you never retried

Menu paths from HighLevel's help docs and changelog, read Nov 17, 2026.

When to use Workflow Maps Cleanup

Cleanup shipped Nov 10, 2026: Automation > Workflows > Workflow Maps, then Cleanup in the left rail. It lists workflows with default names, workflows with no enrollments in the last 60 days, and empty folders. You review each one and confirm before anything is deleted, and it follows your access permissions.

Three times I'd use it. When you take over an account someone else built, before anything else. Before you take a new snapshot from a master account, so test workflows and "New Workflow 3" don't get copied into 50 clients. And in the monthly audit, mostly for the default names, because an unnamed workflow is one nobody can debug from an error email.

Don't treat "no enrollments in 60 days" as dead. HighLevel's own note says a workflow with no recent enrollments might be seasonal: a holiday promo, an annual renewal, a birthday sequence. Rename it with what it does and when it runs. While you're in the map, agency admins can rename workflows and folders, change folder colors, add sticky notes and save the layout for everyone in that sub-account. Each sub-account has its own map.

A2P across every sub-account: the Agency Trust Center

Before Oct 28, 2026 you checked A2P status by opening each sub-account. The Agency Trust Center puts it in one place: Agency View > Settings > Phone Integration > Trust Center (A2P). The changelog says to enable the Agency A2P console in Labs first. It's on the $497 Founder plan only, for Agency Owners and Agency Admins.

The Overview tab counts sub-accounts as Fully Approved (Brand and Campaign both approved), In Review or Rejected, and lists the top Brand and Campaign rejection reasons with how many accounts each one hit. Brands and Campaigns tabs filter by status, show attempts left, and offer Fix and Resubmit. You can also click Start registration and register a Brand for a sub-account from agency level.

It also compares registration methods across your accounts: how many used the Chat Widget consent method versus Self-Serve, and the approval rate of each. If one method keeps losing, change how you register the next ones. There's no CSV export in the first version. Registration itself is on A2P 10DLC registration.

Bulk changes across sub-accounts (and checking they landed)

Since Oct 14, 2026 you can change feature access for many clients at once: Agency View > Sub-Accounts, tick the accounts, click Update features, pick the features (search, whole groups, Select all), click Next, set each to Enable or Disable, then Apply changes. Features you didn't pick keep their current setting. HighLevel says changes take 2 to 5 minutes.

The same list has Bulk Actions for Enable SaaS Mode, Pause Sub-Account, Enable Rebilling and Setup Calendars, depending on your plan. The list also has Advanced Filters, including by snapshot, which is how you select every plumber account before a change. Those filters and bulk actions are on the $297 and $497 plans.

Two rules. Check Bulk Action History (the clock icon) after every job, open Show Full Details, and look at the Failed count, because a job can finish with some accounts failed. And be careful with Pause: HighLevel warns that choosing to disconnect phone resources can permanently delete the numbers and A2P campaigns, while leaving them connected keeps usage charges running.

Snapshots, versions and pushing updates safely

The snapshot is your release process. Change the master sub-account, refresh the snapshot, check what changed, then push. How to create, load and push is on GoHighLevel snapshots. The safety part is what you do around it.

Read the version before you push. Agency View > Account Snapshots > My Snapshots, click the snapshot, open Version History, and open the latest version's details. It shows what was Added, Removed and Synced since the last refresh. If something shows up under Removed that you didn't mean to remove, stop.

Push to a few first. Push to two or three accounts, run the canary test on them, then push to the rest. If a refresh deleted a step contacts were waiting on, HighLevel removes them from the workflow (the log says "Removed by - Snapshot Refresh"), so a bad push can drop people out of live follow-ups.

Keep a copy you can go back to. Version History has no revert. Before a big change, take a separate snapshot of the master named with the date, and keep it until the new version has run clean for a couple of weeks.

Limit who can push. Snapshot permissions are split into View, Create, Edit, Share/Import, Push, Refresh and Delete. HighLevel's own advice is to restrict Delete and Push to trusted team members.

User roles and permissions so clients can't break things

Clients break automations by accident: they edit a workflow to change one word, delete a tag a trigger depends on, or turn a feature on that bills per use. HighLevel gives you three layers today (help docs updated Nov 10, 2026), and a user never gets more than the layer above allows.

Layer 1, the sub-account's features. Agency View > Sub-Accounts > three dots > Manage Client > Features and Limits > Features. Since Aug 11, 2026 there are 80+ switchable features grouped as Category > Module > Feature. If the client doesn't need Workflows or AI Studio, turn them off here, and no user in that account can open them.

Layer 2, the client's user. Inside the sub-account: Settings > Users > the user > Roles & Permissions. Give clients the User role, not Admin, and switch off Automation for anyone who doesn't need it. Existing workflows keep running when you take a user's access away. Only Assigned Data limits a sales user to their own contacts and opportunities, and Copy Permissions saves rebuilding the same setup per user (there's no bulk assign).

Layer 3, workflow folders. On a folder: Actions > Manage Permissions, and set it to Agency Admin, Agency User, Account Admin or All. Users without access can't see, create or edit workflows in that folder. Put your core automations in a folder set to Agency User so client admins can't touch them. The doc is from 2022 and lists this as an Agency Pro (top plan) feature, so check it shows up on yours. One gap: users can still add or remove a contact from any workflow on the contact page.

It works the same way I've always set clients up: "we go into the settings we go into staff and we actually invite them in we make a user for them," and "a client in this sub account won't be able to see your personal sub account or different clients." Just give that user less than admin.

Your own team: agency users and Audit Logs

For your staff, Agency View > Settings > Users > Edit > Roles & Permissions. Set User Type to Account and assign only the sub-accounts that person manages, so a VA on three clients can't open the other 97. Under the Sub-Accounts module, clear Create Sub-Accounts and Delete for anyone who doesn't need them, and review Login As, Sub-Account Settings and transfer permissions. HighLevel lists those as the sensitive ones.

What you can't do yet is fine-grained control of agency-level users. "Granular Permissions at the Agency Level for Agency Admins/Users" has 1,229 votes and is marked in progress, first posted in April 2022 (ideas board, Nov 17, 2026). So treat Agency Admin as full access and give it to as few people as possible.

When something changes and nobody admits to it, Audit Logs answer it. Agency > Settings > Audit Logs covers agency-wide activity, mainly user changes. Sub-account > Settings > Audit Logs covers changes inside a client account, filterable by User, Module, Action Type and time. Entries are kept 60 days and then purged, so export a CSV if you need it for a client dispute. Filter Action to Deleted to find, and for some modules like opportunities restore, what someone removed.

Start the 30-day trial and build your master sub-account →

Set up a new sub-account so you'll hear when it breaks

  1. 01

    Create it from your master snapshot

    Business name (plus location) as the account name. The snapshot brings your named folders, workflows and the ops workflows below.

  2. 02

    Turn on error notifications

    Automation > Workflows > Workflow Settings. Add your ops inbox as a recipient. It's off by default.

  3. 03

    Check the alert workflows are published

    Messaging Error - SMS alert and the Scheduler workflow that creates the weekly canary task.

  4. 04

    Create the canary contact

    "zz Canary" with an inbox and phone your team holds, tagged canary, not on DND. Run the first test before the client goes live.

  5. 05

    Set features and users

    Manage Client > Features and Limits > Features for the account, then User role and no Automation access for client users.

  6. 06

    Lock your core folders

    Folder > Actions > Manage Permissions set to Agency User for the workflows you maintain.

Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Other ways to start

My bonuses come with every one of these.

Best if you're new and want live help setting up

30-day trial + a free live setup bootcamp

Best if you're not sure which plan you need

Compare all 3 plans first

Best if you'll resell HighLevel as your own software

Go straight to the $497 Founder plan

FAQ

How do I manage multiple sub-accounts in GoHighLevel?

From Agency View > Sub-Accounts. Use Advanced Filters to group accounts (for example by snapshot), Bulk Actions and Update features to change many at once, and Bulk Action History to check each job. Build every account from one snapshot so fixes can be pushed to all of them.

How do I know when a workflow breaks in a client's sub-account?

Turn on workflow error notifications in each sub-account and add your own email, since they're off by default. Add a Messaging Error - SMS workflow for failed texts, and run a weekly canary test contact through the main lead flow to catch failures that don't throw an error.

Can I stop clients editing workflows in GoHighLevel?

Yes. Give client users the User role and switch off Automation in their Roles & Permissions, or turn Workflows off for the whole sub-account in Manage Client > Features and Limits. Workflow folder permissions can also hide a folder from everyone below Agency User.

Are there agency-level workflows in GoHighLevel?

No. As of Nov 17, 2026 the request has 821 votes and isn't built. Workflows run inside each sub-account, so monitoring workflows go in your snapshot. The Workflows API (Oct 28, 2026) can pull failure stats from every account into one report.

How long does GoHighLevel keep audit logs?

60 days, then entries are purged. Agency logs are at Agency > Settings > Audit Logs and sub-account logs at Settings > Audit Logs inside the account. You can export filtered logs to CSV.

Can I see A2P status for all sub-accounts at once?

Yes, in the Agency Trust Center (Oct 28, 2026): Agency View > Settings > Phone Integration > Trust Center (A2P). It's on the $497 Founder plan for Agency Owners and Admins, and the changelog says to enable it in Labs first.

Can I enable a feature for many sub-accounts at once?

Yes. Since Oct 14, 2026: Agency View > Sub-Accounts, select the accounts, click Update features, choose the features and set each to Enable or Disable. Changes take 2 to 5 minutes and show in Bulk Action History.

Sources / last checked Nov 17, 2026

  • My videos. What do GoHighLevel Clients Actually See? (Jan 2024) and Claude Cowork Runs GoHighLevel Better Than My Team Did (Jun 10, 2026), quoted only. I don't have a video on monitoring many accounts, so there's no video on this page.
  • HighLevel help docs: sub-accounts and bulk actions. How to Bulk Enable or Disable Features for Sub-Accounts (updated Oct 19, 2026), Sub-Account Bulk Actions & History (Nov 15, 2026), Sub-Accounts List UI (Oct 28, 2026) and Customize Default Naming Conventions for New SaaS Accounts (Oct 27, 2026), read Nov 17, 2026.
  • HighLevel help docs: permissions. Manage Feature Permissions for Subaccounts (Sep 2, 2026), SaaS User Level vs Sub-Account Level Permissions (Sep 17, 2026), Sub-account and Agency User Roles and Permissions (both Nov 10, 2026), Admin vs User Roles and Permission Scopes (May 6, 2026), Workflow Folder Permission (2022) and Granular Permissions for Snapshots (2025), read Nov 17, 2026.
  • HighLevel help docs: workflows and monitoring. Error Notifications in workflows (Sep 11, 2024), Workflow Trigger - Scheduler, Internal Notification (Mar 31, 2026), Workflows Nested Folders, Workflows Bulk Actions, Introduction to Workflow Maps, Review workflows with errors and Organize folders and save the map layout (Oct 27, 2026), read Nov 17, 2026.
  • HighLevel help docs: Audit Logs, A2P and snapshots. Audit Logs (Oct 12, 2026), User Audit Logs (Aug 28, 2026), How to Manage A2P Registrations Across Sub-Accounts Using the Agency Trust Center (Oct 27, 2026) and Snapshot Version Management (2025), read Nov 17, 2026.
  • HighLevel changelog and ideas board. ideas.gohighlevel.com, read Nov 17, 2026: More control over what your sub-accounts can see (Aug 11, 2026), Enable or disable features for multiple sub-accounts at once (Oct 14, 2026), Agency Trust Center (Oct 28, 2026), Workflows API (Oct 28, 2026), Workflow Maps Cleanup (Nov 10, 2026). Ideas: Granular Permissions at the Agency Level (1,229 votes, in progress) and Workflows at the Agency level (821 votes).
  • HighLevel pricing. gohighlevel.com/pricing, read Nov 17, 2026: Starter $97 (3 sub-accounts), Unlimited $297, Founder $497 per month.
Hamza Baig (Hamza Automates)

Author

Hamza Baig / Hamza Automates

Founder, Hexona Systems

I run Hexona Systems on GoHighLevel. HighLevel gave it the SaaSpreneur Platinum award in 2024 and Diamond in 2025 and 2026, and I spoke at their LevelUp event in 2026. Hexona powers 1,000+ agencies, we've served 1,500+ businesses, and I've taught 45,000+ students. Everything on this hub is something I use myself or have shown on camera.

Platinum SaaSpreneur
2024
Diamond SaaSpreneur
2025, 2026
LevelUp speaker
2026
YouTube subscribers, Oct 2026
34,200

Keep reading

Start your 30-day free trial →

30 days free + 1:1 setup call + my bonus / affiliate link