Allow setting visibility of Event attendees

AI-generated summary

The discussion centers around the possibility of controlling the visibility of event attendees (“Going”, “Interested”, and “Not Going”) in the Discourse Events plugin. Roi initiated the topic, expressing a need to hide attendee lists from unregistered users and search engines, ideally allowing event creators to choose between “everybody” or “logged in” visibility Roi. opcourdis suggested several workarounds using other plugins like Discourse Category Lockdown, the publish feature, and landing pages, which Roi found complex. tobiaseigen inquired about the specific use case and noted that implementing this as a core feature or plugin would depend on broader demand. Roi clarified the motivation was also to encourage user registration and address user privacy concerns regarding who can see their event responses. tobiaseigen then confirmed that a simple plugin setting controlling visibility for all events would satisfy Roi’s requirements.

Hi,

is it possible to set who can see the participants (“Going”, “Interested” and “Not Going”) of an event?

We use this great addon but now have second thoughts that it might be good to hide these details for unregistered users / guests / search engines and only show to registered users or even TL1 and up.

2 Likes

1° install Discourse Category Lockdown and lock down the event category so it shows only the titles of the event
2° Use the publish feature from discourse to have anonymous user to see the event topic with its /pub/ url and they will see a published page with only the description and pictures.
3° Use the landing page fr plugin to create a page listing all the topics from 1 category(check the bottom of this page Rendering data from a specific topic - Discourse Landing Pages - Pavilion)
4° Set on the category>security option its redirection to the landing page you have created for the event category that you use
5° optional :disable searches for anonymous so that they cannot find anything via the search feature; to do so : add this to your app.yml in the env section and restart the app(without rebuild)

env:
  DISCOURSE_RATE_LIMIT_SEARCH_ANON_GLOBAL_PER_MINUTE: 0
2 Likes

Thank you, but that is very complicated. But at least a way to reach the goal. :slight_smile:

1 Like

Hi Roi! Your scubadiving forum looks really neat! Can you tell us some more about what you are seeking to do? You want to show events in public topics (to not logged in visitors) but limit who can see who has RSVP’ed to those events? Who should be allowed to see who has RVSP’ed?

We do have precedent for limiting privileges and access to things by group. I’m not sure if or when this feature could be implemented for the events plugin, unless more people ask for it and we are able to fit in the work.

Thank you very much for the compliment. I really appreciate it. :slight_smile:

Yeah, exactly. Not everybody should see how will participate, maybe participate or cannot participate. Especially not the search bots. Also, like with other features as well, we want to motivate anonymous readers to create an account or login with their existing account. In this case some of our users also already asked by themselves about who is able to see when they click Yes, No, Maybe.

Something really simple would do for my use case. Like selecting “everybody” or “logged in” in every new event I create. I feel this is more a plugin than a core thing.

1 Like

So a plugin setting covering all events would suffice for you?

Yeah, even that would fully suit my needs. :slight_smile: