Paid users to view other user accounts

Hi team!

Looking to have paid users on my site.

Hoping for a functionality where these paid users can view other paid users profile information such as:

  • some of their profile characteristics
  • cms items they have saved

Is this possible?

Yes but it’s a lot of work programming and automation work. Webflow isn’t designed to show any user info publicly, and doesn’t have any inbuilt connections between user accounts and CMS items, so you’d have a lot of infrastructure to setup.

I do this for some clients when it makes sense, you before you go down the road of hiring a dev of digging into code you should probably explore other options like Bubble.

On Webflow, the most supported 3rd party approaches are Memberstack and Wized+Xano.

Hey Julie!

Just to add on to @memetican 's response, you can do it pretty easily with Memberstack! We actually have a free template for public member profiles which you can use as a starting point.

The only thing about this you would need to change is you would need to create a gated content group and a plan so that this content is indeed gated.

You can do this with just Webflow, Memberstack, and Make (to create the profiles), as is done in this free template - but, depending on your requirements, you may need something like Wized instead of Make.

Pros to using Make instead of Wized for this;

  1. SEO - Using the Webflow CMS for your profile pages means your pages are rendered server-side and show up in your sitemap, so if you want your member pages to be discoverable with search engines, this is a bonus.
  2. Easy setup - This is definitely easier to set up, especially if you use the free template.

Pros to using Wized > Make

  1. More powerful - with Wized, you can implement a whole bunch of custom conditions and everything for your data. It’s a stack that makes building new features the right way soooo much better.
  2. More secure - If you use Wized to actually make the requests for the member data, you can make it server-side gated instead of just client-side. If the member data is sensitive in any way, this is very important.

Overall, both approaches are good, it just depends on your needs. If you’re building a serious product which you can foresee growing in the future, I’d highly recommend Wized + Memberstack.

On the other hand, if this is just a one-off need which you’re incorporating into your existing product, it may not be worth the extra time needed to set it up with Wized.

Hope this sheds some light!!

1 Like