I want to put a password on a portfolio project that has an NDA but it seems that I’m only able to place it on the entire page. From what I researched it seems like this there isn’t an option to do this. Is that correct? If so is there a work around or do I have to use another platform which I really don’t want to.
You can only password protect pages and collection templates not individual items. You could create another collection just for that project or move it to a static page.
What Jeff says. However this solution is super manual as you have to update the filter for each page. You can’t change filters for a symbol either. I tried this for 50 such pages and it was a bad experience.
Also consider memberstack or memberspace. Overkill for non member driven sites, but may be the go until Webflow punch this out.
appreciate the insight. I’ll explore going the memberstack route with the template I have before I decide if it’s best to just cut my loss and use another platform. this is super frustrating. thank you for your help.
Any chance this will be implemented? We need to password protect some select items within a collection and I’m disappointed to see that there are no updates on this in the last 2+ years.
I am also trying to create password to separate Project and not a new page, really bizarre if there is no option for that staple option ! Would appreciate you help.
Thanks
If you’re not especially concerned about achieving 100% content security, and can deal with some nested collection list constraints, here’s a solution that can be setup in Webflow natively ( no 3rd party services, and no external infrastructure such as reverse proxies ).
Below the solution is a discussion of other more robust, and more complex, approaches.
thanks a lot Michael for response, the first option already looks extremely complex…
Strange that webflow, that advertises itself as a platform friendly for designers, not to include one of the most important option that designers need…
Overall, it’s more common to need content gating for an area of your site, than for a specific CMS item. Someday Webflow might implement that, but to meet the needs of all users, it would be quite complex;
Resource sets for gating content, ranging from one single CMS item, to a specific set of items
Security settings for each resource set, either password, or user-login and access-groups
Gating CMS items at the page level
Gating CMS items within collection lists ( filter them out when the user’s not logged in? )
New users already struggle to make sense of basic things like class and breakpoint mechanics. This would just implode brains.
But, you can probably find an item in the webflow wishlist to upvote, or create one. This is how Webflow’s dev team prioritizes what’s important to the community.