Member area accessed by email

I am looking to create a page with resources on it for users of my site. I want the resources only downloadable if they have signed up for access with their email.

Is there an easy solution for this? One idea I had was to do an automatic email from mail chimp that points them to a ‘hidden’ url with all of the downloads but it feels more like a work around than a solution.

I also am currently on the CMS and I dont want to upgrade plans just for this feature as it gets to expensive. Any ideas, links or tutorials to different ways to achieve this is appreciated.

Cheers


Here is my public share link: LINK
(how to access public share link)

1 Like

Hi there,

While Webflow offers password protection for specific pages when hosting with Webflow, file uploads to Webflow’s hosting service are technically public assets. Here are your options for protecting downloadable content:

  1. Password protect the pages containing download links using Webflow’s page password protection feature
  2. Store sensitive files on a third-party service that offers secure file sharing
  3. Use Webflow’s CMS gating feature to restrict page access to logged-in users (requires Business plan or higher)
  4. Implement a third-party membership solution like MemberStack or Outseta to manage user access

For maximum security of downloadable files, we recommend using a dedicated file hosting service that offers granular access controls, combined with Webflow’s page protection features.

Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.

Hey Tom, usually I’d suggest MemberStack, for sign-up and specific member emails. But you’re looking for free, and that’s tough, since you’d need a membership system to make this work.

Maybe look into something like Auth0?

I have prototyped specialized solutions before that use Webflow’s page-level login feature with custom code to tie it to a form… you fill in the form, and you get temporary access to the download page. That’s a bit different from what you’ve described, since they aren’t user-specific logins and cannot return later easily.

But it’s a build direction you could pursue if you’re familiar with custom code.

Thanks Michael, ill check out Auth0. that looks pretty good, cheers for the heads up