I would like to add a section to a collection page which has access/visibility privileges. Historically I’d have used MEMBERS and allocated the privilage to view to the relevant member, however with native members falling away, the 3rd-party apps are not affordable to an NPO.
SOOOO, as I see it these are my options
create a static page that acts like a collection page, and password-protect it. TMK, not a possibility
Find an alternative method to restrict visibility on a collection page
Can one password-protect a section?
Create a static page
with a dropdown field linked to the relevant collection, to select the item
create a section which populates the restricted content based off of the input from the dropdown (this is currently my sticking point)
I believe you can explore password-protected pages along with some custom code / filter as an add-on to gate the restricted content’s access, but it would also depend on the number of static pages you aim to create and distribute for each member, if you want to scale your site to large number of members, it might get cumbersome to handle all the static pages. If you only aim to have handful number of members, it might be worthwhile to start exploring those options to see what works for your project.
Just to add-on, if you find yourself aiming to scale your site for many members, you can also checkout this to see if you would want to opt for 50% off on Memberstack plan, as a Non-Profit organization.
Hope you do find a solution that best fits for your project.
Have you tried any of the methods you listed or are you facing any blockers while setting it up?
Honestly I’d go with Memberstack in most cases, it’s worth it for the role and auth management. However, if they only thing you’re trying to do is hand out a “key” that gives a specific subset of users certain visibility, than your 3rd option is easiest.
Your collection page would not contain the content.
Instead your password-protected static page would contain a collection list that does include that content.
From there, your UX could possibly be built with Finsweet List Filter or just a bit of manual JS if you want to go with the dropdown approach and only show one item.
If you have > 100 items, you can use multiple collection lists on the same page or you can possibly use FS List Load. Make certain to test that since your paginated collection list is on a password-protected page, but it’s a client-side fetch and should have your auth cookie.