How to create private events on Discord

If you’ve tried to set up a private event on Discord, you’ve probably noticed the feature doesn’t exist as an explicit option. There’s no “make this event private” toggle — the event you just created is, by default, visible to everyone on your server.

The short answer is that you can fake a private event by setting the event’s location to a voice channel that only certain members can access. That works for simple cases. But if you’re running events at any real scale — multiple event types, role-gated signups, recurring weekly programming, events that don’t live in a voice channel — the workaround falls apart pretty quickly. I’ll cover both below, and then what to use when the workaround isn’t enough.

Quick context: I’m the creator of Apollo, an event scheduling bot trusted by over 300,000 Discord servers. A lot of those communities found their way to Apollo after running into exactly this limitation.

The quick answer: the voice-channel workaround

Discord doesn’t expose a “private” toggle on events, but you can approximate one by setting the event’s location to a voice channel that only some members can access. Anyone who can’t see the voice channel can’t see the event.

Set up a private voice channel, restrict it to the role(s) you want, and point your event at it. That’s it.

For a single recurring event type — one weekly officers’ meeting, for example — this is fine.

Why this breaks down once you’re running events at scale

The voice-channel approach hits its limits fast. If your community runs events with any real complexity, here’s where it falls apart:

You need a dedicated voice channel for every type of restricted event. One private VC for officers, another for your raid team, another for paid-tier members, another for moderators. Each with its own carefully-managed permissions. Your channel list balloons, your server gets harder to navigate, and every new event type becomes a permissions project.

In-person and external events can’t be made private. Running an IRL meetup? A Zoom call? A Twitch stream? None of those have a Discord voice channel, which means there’s nothing to restrict. Your only option is to hope the right people see the event and the wrong people don’t — which isn’t a strategy.

Permissions are brittle. The moment someone edits the voice channel’s permissions — adding a new role, removing one, tweaking overrides — event visibility changes with it. A routine permissions cleanup can silently expose events that were meant to be private, or hide ones that were meant to be visible.

There’s no way to restrict signups within an event. Imagine a raid night where anyone on the raid team can RSVP, but the tank spot should only be fillable by tanks, and the raid lead slot should only be fillable by officers. Native events have no concept of per-slot restrictions. Either everyone who can see the event can sign up for any role, or nobody can.

No capacity caps, no waitlists. If your private event has limited spots and fills up, Discord doesn’t help you manage overflow. You’re watching the RSVP list by hand and messaging the next person in line.

No history. Once a Discord event ends, it’s gone. If you need to know who attended your officers’ meetings for the past three months, or track signup patterns across your members-only workshops, Discord doesn’t have that data.

For a community running events occasionally, none of these are dealbreakers. For a community running events at scale, each one of them is a recurring headache.

A better approach: Apollo events

Apollo takes the problem from a different angle. Instead of making event visibility a side-effect of channel permissions, Apollo events live in normal text or forum channels, and privacy comes from two places: the channel the event lives in, and the role-based restrictions Apollo lets you apply on top.

The basics:

• Events live in whatever channel you choose. An event in a private members-only channel is private by virtue of the channel. Apollo respects Discord’s permissions natively — users can only create events in channels they have access to, and only see events in channels they can see.
• Events work for any location. Voice, text, in-person, external link — Apollo doesn’t care. The privacy model isn’t tied to a voice channel, so it works just as well for a coffee meetup as it does for a raid.
• Events have real structure. Capacity caps, automatic waitlists, custom signup options, recurring series, full history — all built in.

That handles most private-event scenarios on the free tier. But the story gets considerably stronger with Apollo Premium, because the features that make “private” actually useful at scale — role gating, slot-level access, automatic role grants on RSVP — live there.

What Apollo Premium unlocks for private events

The free tier covers most basics. Premium is where private events get powerful.

Role-restricted events. Require a specific Discord role to sign up — @Officer, @Raider, @Patron, whatever your community uses. Events can be visible to more people than can actually RSVP, which is often what you want: the broader team sees the event, but only the right members can sign up.

Per-signup-option restrictions. Restrict individual signup options to specific roles, not just the event as a whole — so you can reserve specific slots (a healer spot, a caster seat, a raid lead role) for the members who should fill them.

Native Discord events can’t do any of this. The voice-channel workaround can’t either.

Automatic role assignment on RSVP. When a member signs up, Apollo automatically grants them a Discord role. Use it to gate a private prep thread, unlock a voice channel for the duration of the event, or group attendees for quick mentions — without touching role management by hand.

Unlimited recurring series. Private events are often recurring — weekly officers’ meetings, monthly patron Q&As, daily training blocks. The free tier caps you at five active recurring series; Premium removes the cap.

Up to five reminders per event, with custom messages. Private events tend to be the ones where attendance matters most. Premium lets you schedule up to five reminders per event — a week out, a day before, an hour before — and write your own message for each.

Custom signup options. Go beyond Apollo’s built-in templates. Define options that match how your community actually runs events — character classes, team names, session tracks, support staff — with custom labels and emoji.

Managing private events at scale

If you’re running private events at volume — multiple weekly series, programming planned a month out, events across different channels — most of the day-to-day work happens in Apollo’s web dashboard rather than in Discord directly.

The dashboard shows every upcoming event in one view, including unposted occurrences of recurring series. You can build events as drafts over multiple sittings and refine the details before anything goes live in Discord — which matters more for private events than public ones, since a half-finished officers’ meeting or members-only workshop isn’t something you want anyone seeing prematurely. You can edit a single future occurrence of a recurring series without touching the rest — a one-off time change, a cancelled week, a swapped description — and review attendance history across all your private events in one place.

Real-world scenarios

A few concrete examples of what this looks like in practice:

A weekly officers’ meeting. Recurring event in an officers-only text channel, restricted to @Officer. Automatic role grant on RSVP unlocks access to the meeting’s prep thread. Three reminders — a day out, an hour out, at start time. Attendance history stays in Apollo’s dashboard.

A raid with role-gated slots. Single event posted in the raid team’s channel. Visible to all raiders. Tank slot restricted to @Tank, healer slots to @Healer, DPS slots to @DPS, raid lead slot to @Raid Leader. Capacity caps per role, automatic waitlists when a role fills up.

A members-only in-person meetup. Event with an external/physical location — no voice channel involved. Restricted to @Member so only paying members can RSVP. Capped at 30 spots with a waitlist. Automatic role grant adds attendees to an event-specific planning thread.

A patron-only workshop series. Recurring series restricted to @Patron. Custom signup options for different session tracks. Unlimited recurring series means you can run as many parallel workshop tracks as your programming calls for.

None of these are buildable with the voice-channel workaround. All of them are straightforward on Apollo Premium.

Native Discord vs Apollo at a glance

_{*In Apollo’s dashboard. Events posted to Discord remain in their channels indefinitely — the two-month limit only applies to the dashboard view.}

FAQ

Can I make an Apollo event private without creating a voice channel?

Yes. Apollo events inherit their visibility from the Discord channel they’re posted in. Put an event in a private text channel and it’s private — no voice channel required.

Can I restrict who can RSVP without hiding the event?

Yes, on Apollo Premium. Role restrictions apply to signups, not visibility, so you can run an event that’s visible to a broader audience but only RSVPable by a specific role.

Does this work for in-person events?

Yes. Apollo events aren’t tied to a Discord voice channel, so you can run private in-person, Zoom, Twitch, or external-link events using the same role-restriction model.

Does Apollo keep a record of past private events?

Yes. Apollo’s dashboard shows full event history including attendees and signup patterns. Discord itself doesn’t — once a native event ends, the data is gone.

Do I need Premium to run private events?

For simple channel-based privacy, no — the free tier works if “private” means “only people with access to this channel can see it.” If you need role-based restrictions, per-slot gating, or automatic role grants on RSVP, those live in Premium.

How much is Premium?

$7.99/month or $69.99/year per server. See all Premium features.

---

If your events have outgrown what a single voice channel can enforce, Apollo picks up from there. Start free.