This issue is still not resolved for API-created sub-accounts.

I'm building an integration where sub-accounts are created programmatically via the Location API, then SaaS is enabled via POST /saas/enable-saas/:locationId

with saasPlanId and priceId set.

Expected behavior: The sub-account should only have access to the features defined in the assigned SaaS plan (I've selected roughly half of the available

features).

Actual behavior: The sub-account is created with ALL features enabled. When the SaaS plan is assigned (either via API or manually in the UI afterwards), the

features remain unchanged -- all features stay enabled regardless of the plan configuration.

It appears that feature restrictions are only reliably applied when the sub-account is created through the native SaaS purchase/onboarding flow (customer buys via checkout link). When the sub-account already exists and SaaS is enabled retroactively, the saasPlanId parameter only configures the

billing/subscription -- it does not enforce the feature set defined in the plan.

This is a significant limitation for agencies that need to programmatically provision sub-accounts via the API. We need either:

1. The enable-saas API endpoint to actually enforce feature restrictions from the assigned plan, or

2. A dedicated API endpoint to programmatically enable/disable individual features (products) on a sub-account

Without this, there's no way to automate feature-restricted sub-account provisioning at scale.

I do feel like they missed the mark on this big time, for example like removing payments from the menu, or AI agents.

This doesn't look complete? I still can't remove features from the SAAS configurator

Vote for this similar idea also: https://ideas.gohighlevel.com/saas/p/individual-paid-addons-to-saas-plans

I think they should be combined.

Any updates on when this is expected to ship?

Hello, I would like to see each Item in the menu on the left and on the top of each page able to be toggled off or on per client.

EXAMPLE: Sites Tab-

Funnels

Websites

Analytics

Blogs

Client Portal

Forms

Surveys

Chat Widget

URL Redirects

Say That I Want To Sell The Ability to host blogs and funnels only. Turn all other options off. If they need surveys then it's another charge.

That would be a great way to Itemize the packages I'm charging my clients for. I'd do it on SAAS Mode and on Individuals you sign on to your sub accounts.

Thanks.

Can there be a feature for clients to buy Features as addons themselves?

That way we can sell more flexible plans without trying to create the perfect plan of all of our clients. Also the clients can buy addons later on themselves, without have to talk to us and make custom changes in their plans if they want just one more certain feature, but it's part of bigger plan that they don't really need.

Let say a client just want to start with Funnel, Forms, Email Marketing and Chat widget. They can select these 4 features and the price will adjust accordingly as we have set the prices for each feature ourselves. Or we create one core offer with these features. The first offer doesn't really matter so much in this example.

But later on, the client wants Social Planner, Workflows and Community. They can see these features are possible but locked. And they can decide to unlock them one by one to add them to their plan and the monthly/yearly price is changed accordingly.

Did I explain it well?

With these features, can we make it so we can select only some or none of the templates in the template library based on the niche of our client? This would make make it fully featured from a template library perspective.

Can one of the features be the TEMPLATE LIBRARY. We have a niche industry and the template library is NOT appropriate, meaning because its global we can't turn it on for our mainstream clients