SaaS Mode

It would be awesome to create Customized Launchpads. ➕ Add a "Customize Launchpad" tab in the Agency settings. ✅ Let us create several launchpads. ✅ Let us add a launchpad to a SaaS plan like we can with a snapshot. ✅ Let us select the steps / features in the launchpad. If you wanna go crazy with this (which would be awesome), create a High Level version of userflow.com .

Will you guys be adding a 'Favicon' option to customise for the app? Or even just the highlevel 3 bars. Would of course be awesome if we could link our own favicon for the browser tab. HIGHLVL-I-286

Would like to be able to configure SaaS products based upon the number of users, with equal feature configuration otherwise.For extra credit, it would be spectacular to have 2 types of users. One which counts toward the user limitation for billing purposes, and another which does not count toward the user limitation for billing purposes.Use case: pricing based upon the number of lawyers in a law firm using the SaaS, but allow non-lawyers (e.g. client support staff, administrators, front desk staff, etc.) to use the platform without counting toward the user limitation, since they are not directly contributing to client revenues that are used to establish the ROI of the SaaS, yet are valuable to operations and proper use of the SaaS. HIGHLVL-I-4097

Currently, we lack high-level actions to manage subaccounts in an automated way, similar to how it's done through the API. This limitation becomes evident in several critical scenarios: when a user doesn't pay their subscription and needs their account automatically deactivated (created with the same email that paid), or when PayPal doesn't automatically generate subaccounts like other payment methods do, requiring manual intervention. Core Problem The current system lacks automation for the complete subaccount lifecycle. With PayPal, for example, subaccounts aren't created automatically after successful payment, creating a gap between payment and service activation. Additionally, there's no automated mechanism to manage account states based on user payment behavior. Proposed Solution Develop a set of SaaS actions in workflows that operate at high level, integrating with the existing API but providing intelligent automation for subaccount management. These actions would include: Lifecycle management: Automatically create, activate, deactivate, and suspend subaccounts Payment method integration: Solve the PayPal issue by automatically creating subaccounts after payment confirmation Infrastructure management: Install snapshots, configure resources, and prepare environments automatically Payment monitoring: Detect payment failures and apply suspension/reactivation policies Bulk actions: Manage multiple subaccounts simultaneously Critical Use Cases PayPal Scenario: A user successfully pays via PayPal, but their subaccount isn't created automatically. This automation would detect the confirmed payment and create the subaccount, install necessary snapshots, and activate all corresponding services. Payment failure management: A user with email " user@example.com " fails their monthly payment. This automation would initiate a grace period, send automatic notifications, and if unresolved, deactivate the account while maintaining data for a determined period. Automatic provisioning: After successful subaccount creation, this automation would automatically install base snapshots, configure necessary resources, and establish default settings according to the contracted plan. Immediate Benefits This implementation would resolve the current friction with PayPal, eliminate manual subaccount management, and provide a seamless user experience from payment to complete service activation. Additionally, it would enable more sophisticated business policies like configurable grace periods, automatic downgrades for payment issues, and intelligent reactivations. The actions would operate as an abstraction layer over the current API, maintaining existing compatibility while adding the necessary intelligence to fully automate the SaaS subaccount lifecycle.

I would like to request a feature in GoHighLevel that allows clients to resell sub-accounts under our SaaS brand, with options for whitelabel customization. By enabling clients to purchase a sub-account at a high monthly fee (e.g., $497) and resell it privately at their own determined price, we can simplify payment management and avoid the complexities associated with affiliate marketing. This model allows clients to retain all profits from the sub-accounts they sell, while we retain control over recurring service charges. Key Features and Benefits: 1. Simplified Revenue Model: By charging clients a flat, high monthly fee for resale rights, we eliminate the need to manage payments through affiliate marketing. Clients retain profits from their sub-account sales, allowing them to set prices (e.g., $297 per month or less) and expand their offerings, without needing us to handle split payments. 2. Revenue Control for Service Rebilling: All expenses incurred for services like email marketing, SMS, etc., would be billed to the client’s wallet and passed on to their clients, but the direct revenue from these services would go to our main account, not to the reseller. This ensures a clear revenue stream for us while providing value-added services for resellers. 3. Branding Flexibility with Whitelabeling: Clients can resell under our SaaS brand or opt for whitelabeling that we control via the admin panel. This keeps the brand consistent while giving resellers flexibility to market the platform as part of their own offerings. This feature would provide a streamlined approach to managing payments, while maximizing revenue from ancillary services. Clients benefit from a simple and profitable resale model, and we retain direct control over all service-related revenue. Thank you for considering this enhancement. I believe it would provide significant value, expanding the platform’s flexibility and appeal. Best regards, Homer

I would like to request the addition of Turkish and Arabic to the platform's supported languages. Adding these languages would improve accessibility and user experience for a broader audience, allowing more users to navigate and interact with the platform in their preferred language. Thank you for considering this enhancement.

When HL systems go down we can sometimes find a mention on a status page like Better Uptime, other times we need to go through the FB Group to find a post that might mention what is happening. The last few days with Cloudflare outages is a good example...also when updates are pushed and things break. Our customers would like to be able to know what's wrong when things don't work, and an Uptime or Status page mentioning various core services and systems with their status and uptime would be very helpful for them to reference. (a page we can link to from our own sites or embed or host on a subdomain)

HIGHLVL-I-3692

Currently the only deletion option for sub-accounts is to delete in 24 hours. I'd like to be able to set a sub-account to delete on a future date. Use case: When a SaaS client cancels their subscription, I'd like to trigger a workflow that automatically deletes their entire subaccount in 30 days. This would also allow us to create "win-back" campaigns that urge them to reactivate their account before it officially deletes and they lose all of their work.

This is a recurring issue, often raised during Town Halls, especially for agencies offering white-labeled SaaS. The core problem isn’t whether GHL is technically white-labeled. The issue is the lack of agency-level control when new features are pushed live to clients without our knowledge or consent. As white-label providers, we are the face of the platform. We are responsible for client experience, communication, and support. Yet when new features suddenly appear in sub-accounts, without warning, we’re forced into a reactive position, answering for changes we didn’t approve or even know about. What we’re asking for: ✅ 1. Centralised Feature Release Control ➕ Preview upcoming features ➕ Test in a demo account or sandbox ➕ Approve or reject feature rollout and the ability to select SaaS Plan ➕ Ability to delay/hold back features until we’re ready ✅ 2. More Granular Permissions / Packaging ➕ Let us define exactly which features and "sub-features" are included in our SaaS packages ➕ Keep the existing sub-account override system, but allow global-level defaults ➕ Much more granularity. So we can build clean, focused offers without feature bloat ✅ 3. International White Label ➕ Once the translation system is improved (a separate request), we want to control when new features go live based on language readiness ➕ This way, we can avoid launching untranslated features to clients, which breaks UX and looks unprofessional ➕ Even if it means delaying rollout until the translations are available We 100% respect that this is your platform, and you have full freedom to innovate and grow. But if the intention is to support true white-label SaaS resellers, then agencies must be able to control the product our clients see. This is a critical request for serious SaaS agencies who rely on GHL to deliver a stable, branded, and trusted platform experience. 👉🏼 Please add your opinion if you are a white labeled Saas Agency