Hey guys,
i wanna build a login page for a photographer so her clients can login and access their own photos as well as download it.
Therefor i have created a a CMS collection with gates membership access. But as of now i can only give access to the entire CMS collection list, and not just one specific page?
As you see, i can’t search directly for a dynamic page.
Any help would be appreciated.
Isak
Correct, item-level gating is not yet a thing in Memberships.
Hopefully at some point, it’s at the top of my request list too.
There’s very little you can do here, because you also don’t have the ability yet to detect who is logged in, and route them to their page.
Hi @Isak_Hejnesen 
welcome to the forum!
You have a few options.
Most of them are not as direct as you were hoping for, unfortunately, but they will indeed work.
1 Password - Entire Site
You can set 1 password for the entire site natively within Webflow. Give the same password out to everyone and they have full access to every page. Not ideal.
1 Password - Per Page
You can set each static page natively within Webflow to have a unique password. Again, not ideal since you’d have to create a static page per customer for those downloads. But if your client doesn’t have a lot of customers, this could work.
Webflow Memberships
As you’ve found out, restricted access is at the CMS Collection level. But you have a couple of creative options.
Option 1:
Each item within a collection has a slug. You get to control the slug name. The slug is how you navigate with the web browser to that specific item in your collection. The pattern is…
https://<site_name>.webflow.io/<collection_name>/<slug>
So you could think of slug as the customer name.
https://photos.webflow.io/downloads/bob_smith
What people often do is replace that slug with a long auto-generated jumble of characters that is not easily guessable.
https://photos.webflow.io/downloads/kji893DfT453D0oiery3YY2wqs5Oiuend
…and make sure nothing is referenced if you auto-generate a sitemap.
With all of this gated behind Memberships, random folks can’t ever try to guess that url, and only your clients existing customers would have the ability to do so. But it’s highly unlikely they would.
Also, this can all be automated.
Options 2:
If your client does not have a lot of customers, then you can get around this by creating 1 CMS Collection per customer.
Again, not ideal, but you then get the control you’re looking for.
If you’d like an overview, here is a tutorial walking through a Webflow Memberships build, it may give you a few ideas:
Memberstack
You could put aside all of the options above and go with a third party solution. This is the one I’ve used a lot and it will exactly meet your needs.
Here are some screencasts walking through various setups that’ll work with what you’ve asked for:
How to create unique member dashboards in Webflow (using MemberStack)
How to create personalized content for logged in members with Webflow and Memberstack
Hope that helps!
Hi Chris
Wow, thanks so much for that detailed answer. It sure helped a lot!
I will be looking in to these solutions.
Again, thanks so much.
Isak
Hey Chris
I just saw that element-level gating for Memberships was released. Do you suppose it would be possible now?
I just played around with it, and it still seems like it’s not possible, only gated as of if the customer is logged in or not.
A link to the article here: Control element visibility based on member login status | Webflow Features
Hi @Isak_Hejnesen, yea… you’re exactly correct. Everyone is hoping they continue to build out user level gating.
Looking very much forward to that day. Hugh potential!
Replying to follow this in case it is ever added – but it seems like it never was, item-level gating is still not yet a thing in Memberships?
There currently isn’t any work being done on Memberships. Webflow is focusing all developer-wattage on the core product, which includes making the platform more extensible with 3rd party solutions.
Look into Memberstack, Wized, Onseta…
It is possible to gate CMS items individually with Webflow user accounts but you need a reverse proxy and some API integration work to do it properly.