SaaS Mode

Pretty big new feature request, but having a workflow builder at the agency level that can connect with the agency sub account would be very helpful for managing subscriptions and account access.

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.

Would be great to separate my personal/demo/agency accounts from paying clients

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 .

We want to customize ALL the emails known as "Default" or "Standard". ➕ Add a System Emails tab in the Agency Settings (or find a suitable placement). ➕ Add folders for every Category eg. "Invoice", "Estimates", "Communities", "Calendar", etc. ➕ Add the ability to edit every single "Default" and "Standard" email. This would be very helpful! Bonus: ➕ Let us create the system default emails with custom color values. ➕ Add a pallet under the Brand Board named "Default Email Colors". This would make it easy for each sub-account to brand the default system emails.

Possibility to create a whitelabelable knowledge base inside of GHL connected with a ticketing support system.

Currently the pause account doesn't stop workflows so if someone cancels or has a billing issue there messages will still be auto sent thus incurring more charges to the sub-account user and the agency. Seems the workflows all need to pause when there is a billing issue or cancellation. Same with domains, why would there funnel/website still work when they haven't paid or cancelled? This should be part of the pause of a sub-account, just like any other web/funnel builder has

We would like to see some options for optionally branding sub-accounts, such as the ability to override the agency logo in the top-left corner of HighLevel.Many of our clients don't mind having our branding but some of them would like to use their own logos so their team members don't have to know about how our company helps their business. HIGHLVL-I-1431

HIGHLVL-I-3692

Can we rather bill the client on their preferred billing date for subscriptions instead of when they've joined? I find the billing side of GHL very stiff and inflexible. Thank you.