SaaS Mode

Granular Feature Control & Smarter Permissions for SaaS Mode Plan Builder
As a white-label agency building custom SaaS plans for clients, the current SaaS Mode configuration is too limited and creates unnecessary complexity. Here's what we're dealing with: Problem 1: Not enough granularity in the Plan Builder Right now, the Features tab only lets you toggle broad top-level categories (e.g. "Funnels", "Websites", "Workflows"). But within each of those categories, there are many sub-features — and we have no control over which specific sub-features are included or excluded in a plan. This makes it impossible to build truly tailored packages for different client tiers. What I'd love to see: A hierarchical feature control system in the Plan Builder: Level 1: Main categories (as they exist today) Level 2: Sub-categories per main category that can be toggled independently Level 3 (bonus): Specific actions or views within sub-categories (e.g. "view only" vs "edit") This would allow agencies to build precise packages — for example, giving a client access to Funnels but only the basic builder, without A/B testing or advanced settings. Problem 2: Unintended side effects at the User Permissions level When configuring permissions at the individual user level, disabling one permission often unintentionally disables other features that the agency wants the client to see and use. These hidden dependencies are not documented or visible anywhere, making it very frustrating to configure correctly. What I'd love to see: A clear dependency map or warning system: "Turning this off will also affect X and Y" The ability to override individual dependencies, so disabling one thing doesn't silently break something else Better alignment between SaaS plan-level settings and user permission-level settings, so there are no unexpected conflicts The bigger picture: Right now, configuring SaaS plans requires working across two separate layers (plan builder + user permissions) that don't always talk to each other logically. A unified, simplified configuration flow — with full granular control — would make GoHighLevel significantly more powerful for serious white-label agencies.
0
·
Enhancement
SaaS Subscription Billing Should Continue Invoicing/Attempting Payment for All Future Cycles After a Single Failed/Missed Payment
The current billing behavior for Agency SaaS subscriptions halts all subsequent invoicing and payment attempts immediately following a single failed or missed monthly payment. When a client resolves the single outstanding missed invoice (e.g., paying November's invoice on December 9th), the system recognizes the account as "current" but fails to generate or process invoices for any intervening missed months (e.g., December's payment, which was already due). Example: * November 1: Payment failed (Card expired). * December 1: The system DID NOT generate an invoice or attempt payment for the December subscription fee. * December 9: The user paid the outstanding November invoice. * Result: The system marks November as paid, but December's invoice is permanently skipped. The system then reverts to the original schedule, sending the next invoice on January 1st. This behavior results in immediate revenue loss for the Agency and requires manual reconciliation and invoicing for every missed month, undermining the core function of automated SaaS billing. Intended Behavior: The system must operate with a cumulative billing logic standard for all subscription platforms: Maintain Schedule: All future scheduled subscription invoices must continue to be generated and added to the client's ledger, regardless of the status of previous invoices. Cumulative Payment Attempts: Once the client resolves any single past-due invoice, the system should immediately generate and/or process all subsequently due, but unpaid, monthly invoices. Correct Status: If a client is one month behind, the system should show two invoices due: the immediate past month (e.g., November) and the current month (e.g., December).
0
·
Bug
Load More