# A thought: restrict early access forum to those in the program?

**URL:** <https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730>\
**Category:** Roon Community Site\
**Created:** [March 18, 2025, 1:59pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730 "2025-03-18T13:59:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johnny\_Ooooops](https://community.roonlabs.com/user_avatar/community.roonlabs.com/johnny_ooooops/32/121403_2.png) [@Johnny\_Ooooops](https://community.roonlabs.com/u/Johnny_Ooooops)\
**Post date:** [March 18, 2025, 1:59pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730/1 "2025-03-18T13:59:43Z")

</div>

Hi-  
A thought to avoid confusion and chaos. Could we restrict access to the #earlyaccess part of the forum to those who are actively enrolled? It feels like an inordinate amount of confusion arises from those who see features / new releases and say they don’t see it (on their systems), then enroll in the program because they want the features, then get upset because there are bugs. Keep prod for prod!

---

<div class="post-metadata">

**Author:** ![BlackJack](https://community.roonlabs.com/user_avatar/community.roonlabs.com/blackjack/32/39743_2.png) [@BlackJack](https://community.roonlabs.com/u/BlackJack)\
**Post date:** [March 18, 2025, 2:03pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730/2 "2025-03-18T14:03:48Z")

</div>

How to achieve that though? Everyone is free to install early access (without prior registrartion) by just following [the guide](https://help.roonlabs.com/portal/en/kb/articles/roon-early-access-program).

---

<div class="post-metadata">

**Author:** ![Johnny\_Ooooops](https://community.roonlabs.com/user_avatar/community.roonlabs.com/johnny_ooooops/32/121403_2.png) [@Johnny\_Ooooops](https://community.roonlabs.com/u/Johnny_Ooooops)\
**Post date:** [March 18, 2025, 2:06pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730/3 "2025-03-18T14:06:03Z")

</div>

> [@BlackJack](#):
>
> How to achieve that though?

Dunno about the complexity of implementation, but I’d say “if the Roon servers see that you’ve had a Roon core on early access active in the last `[x]` days, then you can see the forum, else not”. X could be 7 or 30 or whatever.

---

<div class="post-metadata">

**Author:** ![mjw](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mjw/32/382057_2.png) [@mjw](https://community.roonlabs.com/u/mjw)\
**Post date:** [March 18, 2025, 2:13pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730/4 "2025-03-18T14:13:30Z")

</div>

This used to happen for #Alpha, which was a closed group, so it’s certainly doable, but, no doubt, requires some administration.

However, if anyone may join, this wouldn’t completely eliminate what you have described. But it could prevent casual posting in the wrong category and visibility of upcoming features passing through EA.

Something for Roon staff to consider.

---

<div class="post-metadata">

**Author:** ![Johnny\_Ooooops](https://community.roonlabs.com/user_avatar/community.roonlabs.com/johnny_ooooops/32/121403_2.png) [@Johnny\_Ooooops](https://community.roonlabs.com/u/Johnny_Ooooops)\
**Post date:** [March 18, 2025, 2:21pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730/5 "2025-03-18T14:21:12Z")

</div>

And yes, I know some people who are trying to join #Early Access program get help in that section of the forum, so there’d need to be some manual way in. But that part of the forum has a high noise-to-signal ratio at times.

---

<div class="post-metadata">

**Author:** ![Suedkiez](https://community.roonlabs.com/user_avatar/community.roonlabs.com/suedkiez/32/107321_2.png) [@Suedkiez](https://community.roonlabs.com/u/Suedkiez)\
**Post date:** [March 18, 2025, 2:38pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730/6 "2025-03-18T14:38:05Z")

</div>

Maybe just making it a bit more explicit might help

> [@Rename the "Early Access" section to "Early Access Testing" or something?](https://community.roonlabs.com/t/rename-the-early-access-section-to-early-access-testing-or-something/290780):
>
> And maybe add something to the blurb, like “This category is for discussing the latest Early Access testing releases, or Roon’s Early Access program” This is an attempt to prevent Production users constantly going to #Early Access and wondering why they don’t have feature X. I can’t understand why calling it #Early Access is not enough, but apparently it isn’t.

---

<div class="post-metadata">

**Author:** ![Johnny\_Ooooops](https://community.roonlabs.com/user_avatar/community.roonlabs.com/johnny_ooooops/32/121403_2.png) [@Johnny\_Ooooops](https://community.roonlabs.com/u/Johnny_Ooooops)\
**Post date:** [March 18, 2025, 2:50pm UTC](https://community.roonlabs.com/t/a-thought-restrict-early-access-forum-to-those-in-the-program/295730/7 "2025-03-18T14:50:55Z")

</div>

> [@Suedkiez](#):
>
> Maybe just making it a bit more explicit

You sir are an optimist! I’ve seen a lot of people fall down well-marked holes in the ground.
