Pass Windows as Events
A window of access on a place becomes a Discord scheduled event, kept in step with the window: the server default, each place's own choice, the 30-day horizon and the events you made yourself.
A pass grants a place for a window of time, and a pass series grants a run of them. On Discord those windows can appear where members already look for what is happening: the server's Events calendar. The app creates a scheduled event for each window, marks it active when the window opens and completed when it closes, and keeps it in step when the window moves.
What becomes an event
| The place | The event | Who sees it |
|---|---|---|
| A voice or stage channel | A voice or stage event on that channel. | The members who can see the channel. |
| A text or forum channel, a role, or the server | A server-wide event whose location is the portal's link to the plan. | The whole server. |
The event names the place for pass holders; a server-wide one carries the portal link, so a member who sees it can buy the pass.
The server default and each place's own choice
Not every creator wants every window on the calendar, so there are two levels:
- The server default, under Edit settings → Pass windows as server events on the Connectors page: No events, Voice and stage channels only (the default, where the event is visible to the members who see the channel) or Every place on sale (where a window on any other place becomes a server-wide event with the portal link as its location).
- One place's own choice, when the default is not what that place needs: the Pass windows as
server events, per place action on the Connectors page, or
/subscriby-admin events set <place> <choice>in the server. The resource editor says in one sentence what applies to the place;/subscriby-admin events showlists the default and every place.
A text channel with a daily pass series would put a server-wide event on the calendar every day. Leave the default at voice and stage channels, and switch one place on when its windows are worth announcing.
Timing
- An event is created the moment a window is scheduled, when the window starts within 30 days. Windows further out wait, and a daily sweep adds each one as it enters the horizon, so a long daily series never holds more than a month of events: Discord caps a server at a hundred.
- A window already under way gets no event, since Discord refuses a start in the past.
- When the window opens, the event goes active; when it closes, completed. An event for a window that was cancelled before it started is deleted; a running one is completed.
- When the window's times change, the event follows.
- Switching a place off, or the default to No events, deletes the app's own events for it.
Events you made yourself
If you already created an event on the same channel (or, for a server-wide event, with the same name) starting within fifteen minutes of the window, the app adopts it instead of making a second one: only its times and status are kept in step with the window, and its description and cover image are never overwritten. A cancelled window leaves an adopted event alone.
For members
A holder sees the window on the server's calendar like any event, with Discord's own reminders.
/subscriby passes lists what they hold, and the portal shows every window with its countdown.
Related
- Integration — how a pass grants its place at the window's start.
- Plans — passes and pass series on the dashboard.
- Connect a Discord server — the settings and actions on the Connectors page.
How is this guide?
Last updated on
Linked Roles
Put a verified-membership requirement on any Discord role: active member, member for at least so many days, so many live plans, written by the app from the membership ledger.
Running Your Server
The members area in one click, the announcement channel and broadcasts that mention roles, support in your direct messages or a forum of threads, alerts on Discord and the Copilot in your reply.