SaaS Mode

SaaS Mode V2
Here are a few ideas for upgrades to the current SaaS mode:1. More than 3 SaaS plans (preferably unlimited).2. Have a way for SaaS users to change their plan or cancel in their billing settings and let us make our own description of what is included in each plan to show here in billing.2a. Give us the ability to control what SaaS plans they can switch to in the billing settings.2b. Let us create a required form for SaaS users to submit if they are trying to cancel that includes the ability to downgrade to a cheaper plan. 2c. Agencies should be able to choose if users have the ability to change plans or cancel in settings, it should not be a required feature.3. Let us "impersonate" any SaaS user and see the app as they see it.4. Give us the ability to turn off some features completely so that no SaaS plan has them.5. Let us create our own banner popups that show for SaaS users.6. Give us the ability to disable certain settings in the settings menu for SaaS plans if we don't need our users to be able to access them. Also, I'd love to be able to add custom menu items to the settings menu, not just the main menu.7. There needs to be a way to fully disable features that SaaS accounts lose access to. For example, if a user cancels their subscription or downgrades to a plan that doesn't have workflows, they will not be able to view workflows anymore but the workflows will still actually work. This is not okay.8. We need some sort of system for managing and sorting our sub accounts. Filtering by SaaS plan would be a good start. Also, would love the ability to be able to select multiple SaaS accounts and bulk edit them (like adding or removing feature permissions). HIGHLVL-I-5285
33
·

planned

Implement SaaS Actions for Automated Subaccount Management
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.
0
Load More