At first glance, Discord events don’t support private events. They’re seemingly available to anyone on the server, regardless of their permissions.
You can however create a private event by setting the “location” field to a private voice channel, restricted to only the users you want to be able to see the event. Only users who have access to the voice channel will see the event.
This is sufficient for many use cases, but there are some limitations.
- You need a private voice channel for each type of restricted access event you run
- Events without a voice channel (such as in person events) cannot be made private
- Changing voice channel permissions can inadvertently alter event visibility
Apollo events
We’ve built Apollo with these limitations in mind, recognising that flexibility is critical when running an online community.
Apollo events exist in text or forum channels; a private event is simply an event in a restricted channel. The /event command kicks off the event creation flow, where Apollo asks a few questions to get the event setup (including which channel the event should be created in). Apollo respects Discord permissions, so users can only create events in channels they can access.
Apollo also supports restricted events. If a server has an active Premium membership, events can be restricted to users with specific Discord roles. This allows for “private” events that only certain users can attend, but are otherwise visible to other users in the channel. Restrictions can be applied to the entire event or to specific signup options.
For example, an event could require all users have the @Raider role to attend, while the raid leader role requires the @Raid Leader role in addition to the @Raider role.
Discord events offer many niceties, but they are limited in application. Apollo events are flexible, and can be tweaked to suit most use cases. To give Apollo a try, click the button below. For help getting started, check out our documentation and guides.