Migrating from Webflow User Accounts with a very specific set up Answered
Hi there,
Following Webflow's notice that they will be deprecating User Accounts, we urgently need to find an alternative solution and would like to confirm if Memberstack can help.
Here's a brief summary of the project:
* We've created a membership website using Webflow with the following features:
* Users can create accounts and log in (using Webflow's User Accounts). Access is granted via an annual subscription (for which we use Webflow's Ecommerce tools). We also use Webflow Ecommerce discounts, which our clients can offer to their users.
* Each user enters a membership ID (the ID is manually provided to members by our client and isn't generated at our end) upon registration. Based on that ID, specific content is revealed using Webflow's 'Access Groups.' and our own custom logic handles via some middleware.
* Users also have the option to make some of the information they enter during registration publicly available so that their profile may be searchable on the site. This is done via creating a CMS item for that user in the CMS.
* Users can create events via Webflow forms, which are added to the CMS for these users through the API. Both CMS users and events are created as drafts and require manual approval from our clients, performed via the CMS editor.
* We have some custom middleware that handles specific logic our client needs regarding how subscriptions are managed: subscriptions are annual and run between 1 April and 31 March. At the end of the year, users must renew their subscriptions. We send an email with a product link specific to each user, allowing them to renew between 1 and 31 March. On 1 April, our system checks whether the payment has been made. Those who don't renew lose access to gated content and their events as drafts in the CMS. This logic can be manually overridden if our clients tick a specific checkbox in the CMS for a user. When this option is selected, the script at the end of the year does not disable the access groups or set CMS items to draft for that user. This allows the creation of free accounts.
Based on the above, we either need:
1. As a minimum, a replacement for User Accounts and the ability to manage gated content, etc.; or
2. If our specific logic can be migrated to Memberstack, we could completely eliminate Webflow User Accounts, Webflow Ecommerce, and our third-party subscription engine.
I wonder whether this is possible and which of the options can be addressed.
Comments
2 comments
Hi Evgeniy,
Memberstack can indeed serve as a replacement for Webflow's User Accounts and provide the necessary functionality for managing gated content and subscriptions. Here's how Memberstack can address your needs based on the project summary you provided:
1. Replacement for User Accounts and Gated Content Management
- User Accounts: Memberstack allows users to create accounts and log in, which can replace Webflow's User Accounts. You can manage user authentication seamlessly.
-Gated Content: Memberstack provides access control features that enable you to restrict content based on membership status. You can use Memberstack to manage which users can see specific content.
2. Subscription Management
- Annual Subscriptions: Memberstack supports subscription plans, allowing you to set up annual billing cycles. You can manage subscriptions directly through Memberstack, eliminating the need for Webflow Ecommerce.
- Custom Logic: While Memberstack has built-in subscription management, you may need to implement some custom logic for your specific requirements (like the renewal process and manual overrides). Memberstack's API can be utilized to create custom workflows that fit your needs.
3. User Profile Management
- Membership ID: You can collect additional user information during registration, such as the membership ID, and store it in Memberstack's custom fields. This can be used to control access to content based on the ID.
- Public Profiles: You can create a public profile feature by integrating Memberstack with Webflow's CMS. This would allow you to manage user profiles and make certain information searchable.
4. Event Management
-Event Creation: You can continue using Webflow forms for event creation, and with Memberstack, you can manage user permissions and access to these events. The integration with your existing middleware may require some adjustments, but it is feasible.
If you have any specific questions about implementation or need further details on any of these features, feel free to ask! 😊
Thanks for the update Chukwudi, all sounds positive and we will give it a try. Let me post any questions that may occur during the migration process, which I think would be useful for the community.
Please sign in to leave a comment.