Since October 14, 2026 you can bulk update sub-account features in GoHighLevel: an agency can turn features on or off for many sub-accounts in one action: select the sub-accounts on the Sub-Accounts page, click Update features, choose Enable or Disable for each feature, and apply. HighLevel says changes take effect in about 2 to 5 minutes and every request is tracked in Bulk Actions History. It removes a lot of repetitive admin for agencies with many clients, and it deserves one rule: check which live workflows depend on a feature before you disable it for a group.
How do you bulk update sub-account features in GoHighLevel?
To bulk update sub-account features in GoHighLevel, follow the steps HighLevel's changelog gives:
- Select the sub-accounts on the Sub-Accounts listing page.
- Click Update features.
- Choose the features you want to change, then click Next.
- For each feature, choose Enable or Disable.
- Click Apply changes.
You can search for features, select whole groups at once, and use Enable all or Disable all. You can also remove a feature from the list before applying. Requests are queued and processed, and you can follow the status of each one in Bulk Actions History.
- SelectChoose sub-accounts on the Sub-Accounts page
- Update featuresPick features, then Enable or Disable each
- ApplyThe request is queued
- 2 to 5 minutesThe change takes effect
- AfterwardsStatus shows in Bulk Actions History
Source: HighLevel changelog, October 14, 2026
What does the bulk feature update change for agencies?
The bulk feature update lets agencies select many sub-accounts and change a feature in one action, instead of opening each sub-account and changing its settings by hand.
| Job | Before | Now |
|---|---|---|
| Roll out a new feature to every client | Open each sub-account and change its settings | Select the accounts, one action |
| Restrict access to a feature for a tier | Per sub-account, by hand | Select the tier's accounts, disable once |
| Standardise setups across clients | Repeat the same clicks per client | Apply the same feature set in bulk |
| Prove what was changed | Memory and notes | Bulk Actions History |
The changelog describes the benefit as spending less time on repetitive admin; the table is our summary of the before and after.
What should you check before you disable a feature in bulk?
Before you disable a feature in bulk, check which workflows use it; this is our advice, not HighLevel's. We have not tested what happens to active workflows when a feature is switched off.
- List dependencies. Which workflows, forms, calendars and reports use the feature? If one does, test in a staging sub-account first.
- Start with a small group. Apply to two or three accounts, wait the 2 to 5 minutes, then look at the result before applying to the rest.
- Write down the change. Note the date, the accounts and the feature in your account map, even though Bulk Actions History records it.
- Tell the client. A feature that disappears from their menu is a support ticket waiting to happen.
- Match it to your plans. If you sell tiers through SaaS mode, decide whether feature access should follow the plan. See GoHighLevel SaaS mode setup.
Agencies who manage many accounts will also want a standard structure for each one; see GoHighLevel for digital agencies and how we organise an account.
Related updates: the full October 14 to 17 digest, number pool call tracking and WhatsApp templates. Agencies running many accounts may also want the SaaS mode setup.
Frequently asked questions about bulk feature updates
Can I enable or disable GoHighLevel features for multiple sub-accounts at once?
Yes, since October 14, 2026 you can enable or disable GoHighLevel features for multiple sub-accounts at once. Use the Sub-Accounts page, select the accounts, click Update features, and choose Enable or Disable for each feature.
How long do bulk feature changes take to apply?
HighLevel says changes take effect in about 2 to 5 minutes after you apply them.
Where can I see whether the bulk change worked?
In Bulk Actions History, which shows the status of every request, according to the changelog.
Can I change only some features, not all?
Yes, you choose the features, can search for them, select whole groups, and remove any feature from the list before applying.
Will disabling a feature break workflows?
HighLevel's changelog does not say whether disabling a feature breaks workflows. Check which workflows depend on the feature and test on a small group first.
Does this work for white label and SaaS accounts?
The entry refers to sub-accounts on the Sub-Accounts page and does not mention SaaS mode specifically, so check on a test account before you rely on it for SaaS plans.
Do I need a particular plan to use it?
The changelog entry does not state a plan requirement. Check your agency account for the Update features option. See the pricing guide for what each plan covers.