# Password Protected Pages **URL:** \ **Category:** Roles and Permissions\ **Tags:** course-materials\ **Created:** [February 5, 2020, 3:55pm UTC](https://community.ethosce.com/t/password-protected-pages/844 "2020-02-05T15:55:18Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![gmartinez](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@gmartinez](https://community.ethosce.com/u/gmartinez)\ **Post date:** [February 5, 2020, 3:55pm UTC](https://community.ethosce.com/t/password-protected-pages/844/1 "2020-02-05T15:55:18Z")
I’d like to request the ability to set password protect pages within Ethos. We’ve been asked more than once to create pages for hosting course materials, which include recordings, power-points, and other materials. Most faculty don’t want just anyone to access their work and access isn’t always just based on attending the course. We’ve had faculty want to make exceptions for people who didn’t attend their course, for attendees who on top of paying registration paid a fee for access, or didn’t attend but want to pay for access to materials, etc. There are too many access variables and no workaround in Ethos covers them all, or at all. Current workarounds are also too time consuming (I’m not creating a course just for access code usage for some pdfs and power-points). I’m sure there would be other uses for this too. I’d be happy with basic pages having this option for the course material reason, but password protected course pages…would make the course test/edit phase soooo much easier. Would anyone else like this or have thoughts? Please vote if you’d like to see this feature added to Ethos! ---
**Author:** ![gina.buon](https://sea1.discourse-cdn.com/flex015/user_avatar/community.ethosce.com/gina.buon/32/363_2.png) [@gina.buon](https://community.ethosce.com/u/gina.buon)\ **Post date:** [April 24, 2025, 4:37pm UTC](https://community.ethosce.com/t/password-protected-pages/844/3 "2025-04-24T16:37:06Z")
Hi @rizzoa, Thanks so much for resurfacing this idea! This feature was originally brought up in early 2020, but it didn’t gain enough traction across the community to move forward as a prioritized enhancement. That said, we _always_ welcome new ideas and community input—especially when use cases evolve or become more common over time. If this is something you’d find valuable, we’d love to hear more about how you’d envision using password-protected pages in your EthosCE site. We encourage you (and others who may support the idea) to give the post an upvote and add any additional context or examples that might help our team better understand the need. In the meantime, if you have a specific workflow in mind, please open a support ticket so our team may investigate if there’s a current workaround or existing feature that might help meet this need. ---
**Author:** ![maguirre](https://avatars.discourse-cdn.com/v4/letter/m/838e76/32.png) [@maguirre](https://community.ethosce.com/u/maguirre)\ **Post date:** [April 24, 2025, 5:20pm UTC](https://community.ethosce.com/t/password-protected-pages/844/4 "2025-04-24T17:20:10Z")
Hi there! I vote for this idea. We create the conference e-syllabus on a Basic Page, and it would be great if we could password protect it so that only registrants can view it after entering the password that we share with them. Thank you ---
**Author:** ![gmartinez](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@gmartinez](https://community.ethosce.com/u/gmartinez)\ **Post date:** [April 24, 2025, 5:20pm UTC](https://community.ethosce.com/t/password-protected-pages/844/5 "2025-04-24T17:20:51Z")
Thank you for providing this update! I would appreciate it if you could clarify what constitutes “enough traction” for feature requests. I’ve noticed that there are threads in this community that have garnered 10 or more votes yet have not seen any subsequent development activity. I’ve seen requests come around more than once; some have been around for years. Understanding Cadmium’s criteria for prioritizing feature requests at this point would be incredibly helpful! ---
**Author:** ![gina.buon](https://sea1.discourse-cdn.com/flex015/user_avatar/community.ethosce.com/gina.buon/32/363_2.png) [@gina.buon](https://community.ethosce.com/u/gina.buon)\ **Post date:** [April 24, 2025, 5:34pm UTC](https://community.ethosce.com/t/password-protected-pages/844/6 "2025-04-24T17:34:47Z")
Hi @gmartinez, Totally fair question—and I appreciate you bringing it up. You’re right to ask for clarity here. While community votes _do_ help us gauge interest, they’re just one part of the equation when it comes to prioritizing new features. In addition to vote counts, we also look at: - **Feasibility** from a technical perspective - **Alignment with broader platform goals and roadmap** - **Urgency or business impact** across the wider client base - **Redundancy or overlap** with other planned work - And of course, **feedback from support tickets, training sessions, and direct client conversations** That said, we absolutely recognize that some long-standing requests have remained open, and we’re actively working on better ways to surface, assess, and revisit these community-driven ideas. Your input here helps move that forward. If you have specific requests you feel are particularly urgent or still highly relevant, please don’t hesitate to highlight them (here or via a ticket)—it really does help us keep it on the radar. ---
**Author:** ![dikim](https://avatars.discourse-cdn.com/v4/letter/d/53a042/32.png) [@dikim](https://community.ethosce.com/u/dikim)\ **Post date:** [April 24, 2025, 6:06pm UTC](https://community.ethosce.com/t/password-protected-pages/844/7 "2025-04-24T18:06:01Z")
I agree! It would be great if we could do that. ---
**Author:** ![ldjackson](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@ldjackson](https://community.ethosce.com/u/ldjackson)\ **Post date:** [April 24, 2025, 6:37pm UTC](https://community.ethosce.com/t/password-protected-pages/844/8 "2025-04-24T18:37:08Z")
It also would be useful if there was a users group hosted by Cadmium that takes place on a regular frequency. I am part of external groups that address EthosCE tips & tricks, but it would be awesome if we had Cadmium lead something. It would help us all to understand site development and to give input to future needs. Just a thought. ---
**Author:** ![gmartinez](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@gmartinez](https://community.ethosce.com/u/gmartinez)\ **Post date:** [April 24, 2025, 7:19pm UTC](https://community.ethosce.com/t/password-protected-pages/844/9 "2025-04-24T19:19:55Z")
Thanks for providing that information. It’s helpful to know what the Cadmium team considers when considering our feature requests. In general, though, I think the missing piece is a response from Ethos/Cadmium. There are many threads in this community, but the number of them with a solution or feedback on the potential for a solution from the platform is low. So it can start to feel like feedback might be going into a void! Especially if it’s now the third thread, for example, on the same topic. I think getting the platform’s thoughts more often would go a long way. But in terms of highlighting something… Off the top of my head, I know this feature request has been around for at least a decade. And to this day, it’s still a feature request that people would like to see. I have an old thread that includes this, but [I’m pointing to a newer one](https://community.ethosce.com/t/store-enhancements-support-for-preferred-pricing-early-bird-templating-attributes/1929) that has alot of support. Lastly… I also second Laura’s point. It would be beneficial to have a space where Cadmium can take the lead and provide answers to questions on Ethos. It can even be a space where updates are provided on feature requests, helping bridge the gap between the platform and its users! ---
**Author:** ![lauren](https://avatars.discourse-cdn.com/v4/letter/l/b4bc9f/32.png) [@lauren](https://community.ethosce.com/u/lauren)\ **Post date:** [April 24, 2025, 7:39pm UTC](https://community.ethosce.com/t/password-protected-pages/844/10 "2025-04-24T19:39:24Z")
I agree–we’ve had many, many requests the seemed to drop into a void. ---
**Author:** ![EthosCE2014](https://avatars.discourse-cdn.com/v4/letter/e/e495f1/32.png) [@EthosCE2014](https://community.ethosce.com/u/EthosCE2014)\ **Post date:** [April 25, 2025, 2:29pm UTC](https://community.ethosce.com/t/password-protected-pages/844/11 "2025-04-25T14:29:05Z")
Hi, Curious why using a basic page and not use the course page or book object that sits behind the Start button so only enrolled learners can access. Thanks Karen ---
**Author:** ![SMraz](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@SMraz](https://community.ethosce.com/u/SMraz)\ **Post date:** [May 7, 2025, 5:05pm UTC](https://community.ethosce.com/t/password-protected-pages/844/12 "2025-05-07T17:05:10Z")
Hi @gmartinez, When we share conference materials with our learners, we create a separate course page within the course outline titled **“Presentation PDFs”** or **“Presentation Materials.”** This page is used to upload resources such as PDF versions of PowerPoint slides, outlines, presenter handouts, and any other relevant documents the presenter might want to share. We place this course page _after_ the course object “ **payment** ”. This ensures that only learners who have paid for the course can access the materials. Once uploaded, these learners can view and download the content even before the conference begins, allowing them to follow along during the actual presentation. I’m not sure how you would provide access to someone who is not enrolled in the course and only wants to view materials from a single presentation. I hope this information is helpful. Let me know if you have any questions. Susan ---
**Author:** ![gmartinez](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@gmartinez](https://community.ethosce.com/u/gmartinez)\ **Post date:** [May 8, 2025, 5:04pm UTC](https://community.ethosce.com/t/password-protected-pages/844/13 "2025-05-08T17:04:19Z")
Thanks, Susan! Yeah, our request stemmed from needing to have flexibility, as the requests we came across were not dependent on being a paid attendee for a course. And my team and I though this ability might have other uses outside of setting up course materials. Can never have too many ways to do something!