Can you turn features on or off for many GoHighLevel sub-accounts at once?
Yes, since October 14, 2026. On the agency's Sub-Accounts page you select the sub-accounts, click Update features, pick the features and set each one to Enable or Disable. HighLevel queues the change, and it takes effect in about 2 to 5 minutes.
The source is the HighLevel changelog entry Enable or Disable Features for Multiple Sub-Accounts at Once, first published October 14, 2026. Before this, an agency had to open each sub-account to change what it could use. For an agency with 30 or 300 clients, that was the slow part of rolling out a new feature or locking one down.
How do I update features for multiple sub-accounts?
Select the sub-accounts on the Sub-Accounts listing page, click Update features, choose the features, click Next, set Enable or Disable for each, then click Apply changes. Track progress in Bulk Actions History.
Bulk feature update, step by step
- In the agency view, open the Sub-Accounts listing page.
- Tick the sub-accounts you want to change.
- Click Update features.
- Choose the features. You can search, select a whole group, or remove a feature from the list before applying.
- Click Next, then set each feature to Enable or Disable. Enable all and Disable all are there to speed this up.
- Click Apply changes.
- Open Bulk Actions History to follow the status of the request.
HighLevel says changes take effect in about 2 to 5 minutes. To confirm, log in to one of the changed sub-accounts after that window and check the menu shows or hides the feature as expected.
When is a bulk feature change useful for an agency?
It helps whenever many clients should get the same setup: rolling out a feature you have tested, hiding tools a client tier does not pay for, or cleaning up menus so client staff only see what they use. HighLevel names rollout, restriction and standardizing setups.
| Situation | What to do with bulk update | Check afterwards |
|---|---|---|
| A new feature tested in your own sub-account | Enable it for one client group first | Ask one client user to confirm it appears and works |
| Clients on a lower service tier | Disable the features that tier does not include | That no live workflow depended on a disabled feature |
| Client staff confused by a crowded menu | Disable tools that group never uses | That support requests drop, not rise |
| New clients onboarded from a snapshot | Apply the standard feature set in one pass | Snapshot assets still show where expected |
The table is our guidance for agencies, built on the actions the changelog describes. For how agency and sub-account permissions differ in general, see GoHighLevel agency account vs sub-account.
What should I check before disabling features in bulk?
Check whether any workflow, funnel or client process in those sub-accounts uses the feature you are turning off, and change a small group first. A bulk change reaches every selected client in minutes, so a mistake spreads just as fast.
- Start small. Apply the change to two or three sub-accounts, wait the 2 to 5 minutes, and check them.
- Look for dependencies. A feature you hide may still be used by a client's automations or forms. Ask the client or check their workflows before you disable it.
- Tell clients. If a menu item disappears without warning, the client's team will think something broke. A clear support arrangement after a build helps here.
- Keep a record. Bulk Actions History shows each request. Note why you made the change, so the next person on your team understands it. If a client later moves to another agency, that record helps too; see transferring a sub-account.
How does this fit with SaaS mode and snapshots?
HighLevel's entry does not mention SaaS mode plans or snapshots at all. If you run white-label SaaS, test on one SaaS sub-account first and check whether its plan settings and the bulk change agree, before applying it to every client.
This matters because SaaS mode already controls access through plan settings, which we explain in the SaaS configurator setup guide. The changelog does not say which setting wins when the two disagree, and we have not tested it, so we will not guess. If you are setting up a SaaS offer from scratch, our GoHighLevel SaaS setup service covers plans, features and onboarding together.
For agencies managing many accounts, the GoHighLevel automations for agencies page lists the other repetitive admin jobs worth automating. Snapshot rollouts are a related job; see are GoHighLevel snapshots worth buying.
Frequently asked questions
How long does a bulk feature update take in GoHighLevel?
HighLevel says changes take effect in about 2 to 5 minutes after you click Apply changes. The request is queued and processed for you, and you can follow its status in Bulk Actions History. If a sub-account still shows the old menu after that, refresh the page or log out and back in.
Where do I see the status of a bulk feature change?
In Bulk Actions History. HighLevel says you can follow the status of every request there. It is the place to check whether a change finished for all the sub-accounts you selected, and a useful record of what your team changed and when, if a client later asks why a feature disappeared.
Can I enable all features for a sub-account at once?
Yes. After you choose the features and click Next, HighLevel offers Enable all and Disable all, so you do not have to set each feature one by one. You can also select whole groups of features at the first step and remove any single feature from the list before you apply the change.
Does disabling a feature delete the data in that sub-account?
The changelog entry does not say. It describes enabling and disabling access, not deleting records. To be safe, export anything important first and test the change on a sub-account you control, then turn the feature back on to confirm the data is still there before you change client accounts.
Sources
- HighLevel changelog, Enable or Disable Features for Multiple Sub-Accounts at Once, first published October 14, 2026, checked 2026-10-16.
