Pass Series

Sell a season ticket — one payment that covers a whole slate of dated passes drawn from your other pass plans.

A time-limited pass sells one dated window. A Pass Series sells many of them at once: you assemble a slate from the passes your other plans already produce, put a single price on it, and the buyer gets every one of them from that one payment.

It is a season ticket. Ten match days, an eight-week course, a Q1 cohort — bought once, attended over weeks, with each date opening and closing on its own exactly as it would if it had been bought individually.

Available on every plan — bundled on Growth, an addon elsewhere

Pass Series is unlocked by the same capability as passes. It is included in Growth; on Free and Starter you can unlock it with the Passes Addon, billed on your plan's cycle — $19 USD per month, or $190 USD per year on an annual Starter plan.

If you already sell passes, you already have this. There is no extra transaction fee on a series sale — it is billed at your usual rate, exactly like any other plan.

The three kinds of plan

Every plan you create now starts with one choice, and it is the choice that decides which half of the form you see next.

KindWhat it sellsRenews
Recurring SubscriptionThe traditional subscription. Nothing is scheduled — members pay each cycle and keep access for as long as they keep paying.Yes, on a cycle
Time-Limited PassA ticket to one dated session — workshops, match days, one-off events. Access opens and closes on its own and never renews.No
Pass SeriesA season ticket over many passes — seasons, courses, cohorts. One payment covers every pass you bundle from your pass plans.No

The distinction that matters between the last two: a pass plan owns its own dates and generates them from a schedule. A series owns none — it points at dates that already exist on your pass plans. That is why you must have at least one pass plan with upcoming windows before a series has anything to sell.

A series never creates a date, and never destroys one

Everything a series holds belongs to a pass plan. Removing a pass from a series does not cancel it — it stays on its own plan, on sale to individual buyers. Cancelling it on its own plan removes it from every series that holds it.

This is worth internalising before you build one, because it is the rule behind almost every behaviour further down this page.

When to use one

A series is right when the same audience should attend a known set of dates and you want to sell them together rather than one at a time:

  • A club selling a season ticket across a fixture list
  • A tutor selling an eight-week course rather than eight lessons
  • An analyst running a quarterly cohort with a fixed calendar
  • A festival selling a weekend wristband across several sessions

Use a plain Time-Limited Pass when each date genuinely stands alone and buyers pick and choose. Use a Recurring Subscription when nothing is scheduled at all.

Creating one

Choose Pass Series

Open Create New Subscription Plan and pick Pass Series from the three cards at the top. Fill in the name and description as usual.

Switching the card at any point discards the shape you moved away from — a series you had half-composed is not saved if you save the plan as a subscription, and pass schedule slots are not saved if you switch to a series. Only the shape the plan is saved as is persisted.

Pick Pass Series under Plan Type first and the field below it renames itself to Season Lounge Resources, because on a series it is not the thing being sold.

On every other kind of plan at least one linked resource is required, because otherwise a purchase buys nothing. A series is the exception and may link none.

What each date grants comes from the pass plan that date belongs to, not from the series. So a Thursday drawn from your Weeknight Room plan admits the buyer to that room's channels, and a Sunday drawn from Match Day admits them to that one — automatically, without you mapping anything.

Anything you do link on the series itself is a lounge: a channel the holder keeps for the whole span, between dates as well as during them. A season-ticket-holders' chat is the usual case. Leave it empty if you do not want one.

Its invite link arrives with the purchase confirmation, not on the 24-hour schedule the dated rooms follow — there is nothing to wait for, because the lounge is not tied to any one date. It survives every date opening and closing, and is only taken away when the last pass in the season closes.

Never link the channels your slate passes open

This is the one mistake here that costs you money, and nothing about it looks wrong on the screen. A lounge is granted at purchase and kept all season. So if you link a channel one of your slate passes was scheduled to open, every holder is handed it permanently the moment they pay — that pass's date stops gating anything, and your season ticket becomes a permanent key to the channel.

A creator who linked their four match-night channels here had their first buyer receive four invite links at checkout, for four rooms meant to open one night each.

What belongs here: a holders-only discussion room nothing on the slate opens — or nothing at all.

What does not: any channel a slate pass opens. Those are already granted by their own pass plans, on their own dates, without you mapping anything.

If the two overlap, the field turns red and names the offending channels. Take them out of this field; you are not removing them from the season, only from the lounge.

Set the price

Plan Pricing carries two controls.

ControlWhat it does
CurrencyAny currency an active payment method on the project supports. The badge beside each option tells you which methods accept it.
ChargeWhat the whole series costs. The suffix reads once for the whole series for exactly this reason — it is not per pass, and there is no cycle, trial or renewal here.

The buyer pays this figure once and receives every pass on the slate, however many there are. Adding a date later does not charge anyone again.

There is no billing cycle, and no trial

Both sections disappear on a series. Access comes from the dates, not from a period, so there is nothing to renew and nothing to trial. If you need a trial, you want a recurring subscription.

Compose the slate

Series Passes is the heart of it. The summary here shows what the series currently holds — a count and a date span — and two controls:

ControlWhat it does
Prevent Overlapping PassesRefuses to save a slate holding two passes that run at the same time. Turn it off when a customer is genuinely meant to be able to attend both at once. On by default.
Pick Passes / Manage PassesOpens the Pass Series Passes Picker, where the slate is actually built. The button reads Pick Passes while the series is empty and Manage Passes after.

Everything about the picker is in its own section below — it is the most involved screen in the product and deserves the room.

Until you open it, the summary says No passes in this series yet. Open the picker to choose them. A series needs at least two passes before it can be saved — but a rule counts towards that, so a season composed entirely by rules with nothing ticked by hand is perfectly valid.

Set a seat limit, if you want one

Seat Limit caps how many people may hold the series at once. Leave it empty for Unlimited.

The cap counts holders who actually hold the series — a purchase that was refused, or one whose payment never completed, does not consume a seat. On the portal the card shows N seats left, and Sold out once the cap is reached. The moment the last seat is taken, the plan is also switched off automatically and shows Seats Full in your plan list, so the pause is never mistaken for someone on the team unpublishing it; raise the seat cap before switching it back on.

A cap of zero is refused

"A seat cap of zero would put the series on sale with nothing to sell." Leave the field empty to mean unlimited; zero is not the way to take something off sale. Deactivate the plan for that.

Decide when sales close

Late Entry is a pair of controls that work like the sales cutoff on a pass plan, but measured against the whole season rather than one window. There are four anchors, and they form a progression from the earliest deadline to the latest.

AnchorThe season comes off sale…
minutes before the first pass opens (default)…before it has begun, so nobody buys a season they have already started missing. Leave at 0 to sell right up to the first pass.
minutes before the first pass ends…during its opening pass. Latecomers can still join on the night, but once that first session is over the season is closed.
minutes before the last pass opens…as its closing pass begins. The season sells for weeks, but a buyer always gets at least one whole pass.
minutes before the last pass ends…only at the very end. The season stays on sale throughout, and someone can join with a single date left — or part of one.

A mid-season buyer pays the full price for the remainder. Nothing is prorated, and passes that have already run are never issued to them. If that feels wrong for your season, use the first anchor.

minutes before the first pass ends is the one to reach for when you are selling a course or a league rather than a drop-in. Someone who hears about it on opening night can still buy in and be let straight into that session — they are admitted automatically within a minute — but nobody turns up in week four having missed three quarters of it.

minutes before the last pass opens is the middle path if you would rather keep selling all season without ever taking money for a fragment. It is the only anchor that guarantees the buyer a complete pass: the deadline lands as the closing session begins, so there is always one whole date still ahead of them. Compare it with before the last pass ends, which will happily sell a season with ten minutes of its final pass remaining.

This anchor has a five-minute floor

A buyer who arrives after a pass has opened is admitted by a background sweep that runs once a minute, and a busy minute can run long. Closing sales fewer than 5 minutes before the first pass ends is refused on save, because inside that margin someone can pay and never be let in.

The other three have no floor, because none of their deadlines falls inside a pass the buyer still needs letting into: before the first pass opens closes before anyone is admitted at all, before the last pass opens closes as a pass begins rather than during one, and before the last pass ends leaves the whole season behind the deadline.

Next Series points at another Pass Series in the same project — the one this season's holders should buy when this one finishes. Leave it on No follow-on series if there is no next season.

Holders buy first for N hours then sets how long your existing holders get that next season to themselves before it opens to everyone else. See When the season ends for exactly what happens.

Who gets invited is decided when the season ends, not when they paid

This is the single most useful property of the successor link, and it is worth stating plainly: you can link a next season months after the current one sold out, and every buyer still gets the invitation. Nothing is stamped onto a purchase at checkout.

So there is no penalty for not having planned the follow-on in advance. Add it whenever you know what it is.

Save, then activate

New plans are created switched off. Check the slate reads the way you expect on the plan row, then activate it.

The Pass Series Passes Picker

The picker has two sections, and understanding the difference between them is the whole skill of authoring a series.

SectionWhat it doesKeeps working after you save?
Automatic Passes Selection with Rule SetsDescribes passes by a rule — "every pass on this plan between these dates". Matching passes are taken in on their own.Yes. New matching passes are added later, including to holders.
Manually Handpick Passes from PlansYou tick individual passes. Exactly those, and nothing else.No. The list never grows on its own.

They are not alternatives — a series can use both at once, and most good ones do. Rules carry the regular slate; handpicking adds the one-off that does not fit the pattern.

Automatic Passes Selection with Rule Sets

The section header carries a Configure Rules button that reveals the rule rows, and each rule row has its own Remove. Add a Rule appends another.

While there are none, the section reads: "No rules yet. Add one and every matching pass is taken in automatically from now on."

Each rule row has four or five fields depending on its type.

FieldWhat it does
Source Pass PlanWhich pass plan the rule watches. Only Time-Limited Pass plans in this project are offered. One rule watches one plan — add a second rule for a second plan.
Rule TypeEvery Pass Starting in a Period or The Next Few Passes. See below.
Watch FromThe earliest pass start the rule will accept. Leave empty for no lower bound.
Watch UntilThe latest pass start the rule will accept. Leave empty for no upper bound.
Number of Passes to TakeOnly on The Next Few Passes. How many to take, counting forward from the earliest match.

Every Pass Starting in a Period

A window rule. Every pass on that plan whose start falls inside Watch From → Watch Until joins the series — including ones that do not exist yet.

This is the rule you want for a season: set the plan, set the two dates to the season's bounds, and every fixture generated between them lands on the slate as it is created.

The Next Few Passes

A count rule. It takes the first N matching passes and then it is finished.

The distinction that catches people out: a count rule never tops itself back up. Once it has taken its five, it has taken its five — a pass being cancelled afterwards does not make the rule reach for a sixth. If you want the count maintained, you want a period rule with an end date instead.

Say how many, or the rule is refused

"Say how many passes this rule should take in." A count rule with an empty Number of Passes to Take is incomplete and blocks the save — it is not quietly treated as "all of them".

Manually Handpick Passes from Plans

Showing Passes From chooses which pass plan's upcoming windows to display. Switching plans does not clear what you have already ticked — the note under the field says so, because the tiles disappearing when you switch is otherwise alarming.

The passes appear as a grid of tiles. Tick one to add it, untick to remove it. Select all and Clear these act on the plan currently shown, not on the whole series.

If the chosen plan has nothing upcoming: "This plan has no upcoming access windows. Add some to it, or pick a different plan."

The three tile states

A tile is not simply on or off, because a pass can be on the slate for two different reasons and the difference decides what unticking it means.

StateWhat it meansUnticking it
Plain tickedYou picked it by hand.Removes it. Nothing else happens.
By ruleA rule brought it in. You did not pick it.Excludes it permanently — the rule will not put it back.
ExcludedA rule matches it, but you have excluded it.Ticking it again lifts the exclusion and the rule keeps it from then on.

The picker states this outright above the grid: "Passes marked "By rule" were added automatically. Unticking one excludes it for good — the rule will not put it back — and ticking it again lifts that exclusion."

A rule ticks its passes straight away

You do not have to save to see what a rule will do. The moment a rule is complete, every existing pass it matches appears ticked and badged By rule in the grid, and the count and date span above update to match. What you see is what the series will hold.

Passes the source plan has not generated yet are not shown, for the obvious reason — but they are taken in on their own when they appear, and handed to everyone already holding the series.

This is what makes rules usable in practice. "Every fixture this season, except the one we are playing behind closed doors" is a rule plus one exclusion — not a hand-typed list of nineteen dates.

Picking a pass takes a moment to register; the tile shows a spinner over itself while it does, so a slow click is never mistaken for a click that missed.

Passes in this Series

Below the grid, everything currently on the slate is listed in date order, whichever plan each came from and however it got there. While it is empty: "Nothing picked yet. Tick a pass above and it appears here in order."

A badge beside the heading counts the slate, and a summary strip above it gives the date span, how many days it covers, the timezone every time is shown in, and — when the whole slate comes from a single plan — that plan's name.

The slate itself is a table, one row per pass in running order. The subheading states the thing most worth internalising about it: "Everything one payment buys, in the order it runs. Each pass still opens and closes on its own — this is only the running order, not one long window."

ColumnWhat it holds
#Position in the running order, counting from 1.
DateThe day the pass opens, as Wed 9 Sep 2026.
TimeStart and end in the slate's timezone. A pass running past midnight carries an ends 11 Sep badge, so an overnight session is never read as a short one.
LengthHow long the pass runs, in short human form — 3h, 1d 9h.
From planThe pass plan the date belongs to, which is also what decides the rooms it opens.
SoldA purple count of how many holders it already has. Blank when none — worth a look before removing a row.
Added byPicked when you ticked it by hand, or a lime Rule badge when an automatic inclusion rule took it in.
StatusThe window's own status — Scheduled, Open, Closed or Canceled — plus an amber Clashes badge when it runs at the same time as another row.
(last)An × that drops the pass from the series. It removes it from the slate only; the pass itself stays on its own plan.

Below the table, a warning callout counts the clashes when there are any: "N passes run at the same time as another, flagged with a warning icon above." The plan summary repeats it as Some passes run at the same time, with the reminder that you can turn the toggle off if attending both is genuinely intended.

With the toggle on, a clashing slate will not save

Prevent Overlapping Passes is a guard, not a hint. With it on, saving a series whose passes run at the same time fails with an error naming the first offending pair — in the dashboard, over the REST API and through MCP alike. It also stops a rule absorbing a date that clashes with what is already on the slate.

Turn it off when holders are genuinely meant to attend both at once; overlapping dates are then a legitimate thing to sell and nothing is refused.

Save Changes

What the picker's own Save Changes does depends on where you opened it from.

  • From the plan editor (the Pick Passes / Manage Passes button while creating or editing the series), it stores your picks against the form. The footnote says the rest: "Your picks are kept here — save the plan itself to publish them." Nothing is live until the plan is saved.
  • From the plan row (the Manage Passes action on the list), there is no editor behind the picker, so Save Changes writes the slate to the series straight away — the footnote reads "Save to publish your picks to this series straight away." The series is re-synced and its rules re-run in the background exactly as after saving the plan.

What the buyer sees

On the portal

A series card carries a banner the ordinary plan card does not: N passes included, the full date span, and — when you set one — a N seats left pill that reads Sold out at the cap.

Beneath it, the opening days are previewed — each day on its own line with that day's session times beside it, rather than one row per pass. A season running three sessions a day reads as three days rather than as nine near-identical lines, which is what tells a buyer the shape of it. A running countdown to the first pass sits in the banner, and +N more passes across M more days closes the preview.

A pass that runs past midnight carries its closing date beside the times — 16:00–01:00 → Fri 11 Sep — because the day heading above it only says when the pass opens. Without it a 33-hour pass under a Wed 9 Sep heading reads as a nine-hour evening that ended before it began, and a buyer prices three nights as one. Same-day passes stay as bare times, which is the common case and the one the extra date would only clutter.

The source plan is named on a pass only when the season actually draws from more than one.

At checkout every date is listed, grouped by day. Where every pass opens the same rooms — the common case — those are hoisted into a single Every pass opens panel instead of being repeated under all twenty-eight.

At checkout the whole slate is listed under What you get, so nobody pays without having seen every date.

After they pay

Their entitlements are written immediately — one per pass — and the timeline appears on the portal under Your passes, with running N attended and N missed counts.

Each entry reads Pass N of M with its window, and carries a state: Live now, Up next, You attended, or Missed. A pass they already held before buying the series is marked "You already held this pass before buying the series, so it was not issued twice." — they are not charged twice for it and it is not issued twice.

Each entry also carries that date's own join buttons once its invite links exist. Until then it says when they arrive — "Your invite link arrives Tue 1 Sep, 10:30." — so a slate that is mostly buttonless in its first week reads as a schedule rather than as something missing.

A season has two kinds of room, and their links arrive at different times.

RoomLink arrivesTaken away
A dated room — from the pass plan each date belongs to24 hours before that date opensWhen that date closes
The lounge — linked on the series itselfWith the purchase confirmationWhen the last date of the season closes

Dated rooms wait on purpose. A season can open six weeks out. A link minted at purchase would be dead long before the date arrived, so each one is issued a day ahead — the same moment the first reminder goes out, so that reminder is the message carrying the button.

The lounge does not wait, because it is not tied to any date. There is no window whose end could make it stale, so the holder gets it immediately and keeps it all season.

Two dated links arrive sooner than the day-ahead rule alone would manage:

  • The next date's link is sent as the current one ends. The holder is already looking at the message telling them the session is over, which is the cheapest moment they will ever have to tap one more button.
  • A holder who buys inside the last 24 hours gets theirs on the next sweep, within a minute, rather than waiting for a deadline that has already passed.

Tapping a link early costs nothing. The join request sits pending until that window opens, however many days away, and is approved automatically the moment it does.

On the bot

A holder gets My Timetable on the project bot, listing the whole slate with the same states. Each date's invite link is sent ahead of that date opening, on the schedule above — a series holder does not have to do anything different.

After it finishes

A finished season does not disappear. My Memberships carries a Past section below the active ones, listing every pass and series that has run with its attended and missed counts. Opening one shows the full timeline exactly as it looked on the day.

That section is deliberately limited to the scheduled kinds. A lapsed monthly subscription is lapsed billing and belongs in nobody's history; a dated purchase is an event somebody either turned up to or did not, and that answer is the only thing left once the dates have run.

In their calendar

The portal offers Add to your calendar: a subscription URL that puts every pass into Apple Calendar, Google Calendar or Outlook, with a reminder an hour before each one opens.

This is offered to single-pass holders too, not only to series buyers — anyone holding a dated window benefits from it being in the calendar they actually look at.

The link is secret and durable, so it also carries Shared this by mistake? Get a new link — rotating it stops the old URL working for anyone it was shared with, and the holder resubscribes.

The block disappears once nothing on the slate is still ahead. Subscribing a calendar client to a feed of things that have already happened is not a feature, and the timeline is where a finished season is read.

Running the season

Rules keep working, and holders are told

When a new pass appears on a plan a rule watches, it is added to the series and granted to everyone currently holding it. They are messaged about the new date and it joins their timeline. Nothing is charged.

This is the behaviour that separates rules from handpicking, and it is why the picker describes it in those words. If you do not want the slate growing under people who have already bought, use handpicking.

The pass_series.leg_added webhook fires so an external calendar or CRM can be re-synced.

Buyers are told the season can still grow

A season built with rules is not a fixed list, and the portal and the bot both say so before anyone pays — "Any new pass added before 30 Sep is yours too, at no extra cost." The checkout repeats it under This season is still growing.

That line appears only while a rule can genuinely still match something: a rule whose Watch Until has passed, or a count rule that has taken its full count, can bring nothing else in, so nothing is promised. A season composed entirely by hand never shows it.

It is worth understanding as a selling point rather than a disclaimer. A buyer choosing between one dated pass and the season is being told the season may be worth more by the end than the slate they can see today.

Absorption respects Prevent Overlapping Passes

With the toggle on, a new pass that clashes with something already on the slate is not absorbed — the series refuses it rather than handing holders two things at the same time. With the toggle off it is absorbed like any other.

A series holds at most 120 passes

One slate holds at most 120 passes. A rule that would take it past the ceiling stops there rather than partially applying, and the save is refused with "A series can carry up to 120 passes."

Finding a season holder in Subscriptions

A season appears in Subscriptions like any other purchase, but its status column is read per-season rather than per-date. Instead of the single-window pair a pass shows, the row carries how far through the slate the holder is — "6 passes left of 10" — plus N missed once dates start going by without them.

That is deliberate. A season has many dates and one row, so "Awaiting Window / Not Queued" would describe whichever date happens to be next and read as the state of the whole purchase.

View Details opens the same split: a Season block with the span, the progress, the timezone and running attended / missed counts, then a Next pass block naming that date, its countdown, and whether the holder has joined its queue yet.

Cancelling a season

Cancel Subscription is on the row's menu, the same as any other purchase. Cancelling withdraws every remaining date at once — the window sweep admits only holders who have not cancelled — and the row then reads Cancelled with no lifecycle badge beside it. Like cancelling a pass, it sends the holder no message; issue a refund instead if you want them told.

Cancelling a pass that a series holds

Cancel it from Manage Access Windows on its own plan, exactly as you would any window. What happens to series holders depends on whether a substitute exists.

OutcomeWhat happens
SubstitutedHolders are moved to a replacement they do not already hold. Their season continues at the same length. pass_series.leg_substituted fires.
DroppedNo substitute exists, so that date leaves their season. The rest is untouched. pass_series.leg_dropped fires with the pro-rata figure.

A dropped date tells the holder plainly: which pass was cancelled, where they now stand, and about what it was worth as a share of what they paid — "That pass was worth about $9.90 of what you paid."

The pro-rata figure is a number, not a refund

Subscriby computes it and shows it. It does not move any money. The message says nothing is charged or refunded automatically and asks them to contact you, and the webhook carries the same figure so you can act on it — but the refund is yours to issue from your payment provider.

If the cancelled pass was the last one in someone's season, they are told so: "That was the last pass in your series, so the series has now ended."

When the season ends

The plan takes itself off sale

Once the last pass has closed, the series is deactivated automatically and you are messaged about it. Its sales cutoff had already hidden it from buyers; this stops it reading Active in your plan list while selling nothing.

Nothing is deleted. A season is a record of what was sold and who turned up, so the plan, the slate and every holder's attendance stay exactly where they are. Add new passes to it and switch it back on to run another season, or duplicate it for a fresh one.

plan.deactivated fires with reason: series_exhausted.

Holders get first refusal on the next one

If you linked a Next Series, the presale opens at the same moment. Every holder of the finished season is messaged — naming the next season, how long they have, and a link straight to it.

For the length of the window you set, only those holders can buy it. Anyone else who tries is turned away, in the portal and on the bot alike, and told when it goes on general sale. When the window elapses the plan sells to everyone with no further action from you.

pass_series.presale_opened fires when the window opens.

Starting the next season

Start Next Season on the finished plan's row menu does the whole setup in one step. It creates a new Pass Series carrying everything except the slate, and — the part that is actually easy to forget — links it as this season's successor, which is what decides whether the presale above reaches anybody at all.

Carried overLeft behind
Price, currency, description and eligibility flagsThe slate — every pass on it belongs to a season that has run
Prevent Overlapping Passes, Seat Limit and both Late Entry controlsExclusions, which named specific passes that no longer matter
Lounge resourcesHolders — a new season is a new purchase
Every rule, with its source plan, type and count

The new season arrives inactive with an empty slate, and the picker opens straight away so you can compose it. That is deliberate: a duplicate that went on sale immediately would be selling a season with nothing in it.

It is named after the one it follows — Champions Room (Season 2), then (Season 3) — because plan names must be unique within a project and a bare copy would be refused for something you did not type.

Copied rules have their dates moved on a season

A rule copied verbatim would carry last season's Watch From and Watch Until, match nothing at all, and leave you with an empty slate and no clue why. So each rule's window is shifted forward by the length of the season that just ended — a Sept–Dec season produces a rule watching the equivalent block immediately after it.

That is a sensible guess, not a certainty. The dates are in the picker; check them before the season goes on sale.

If the finished season had no presale window set, the new link gets a default of 48 hours. An existing value is left exactly as you set it.

Who is invited, precisely

Everyone who bought the finished season and did not cancel it — whether or not their subscription has expired, which by this point most have. Someone who cancelled partway through is not invited: they said they did not want the season, so a promise made to its holders is not one they are owed.

What Subscriby refuses, and why

Every one of these blocks the save and names itself, so nothing here is discovered after the fact.

RefusalWhy
"A series needs at least two passes. Tick some in the picker, or add a rule that will bring them in."One date sold as a series gives the buyer a worse version of a product that already exists. Passes a rule will take in count towards the two, so this only appears when the series would genuinely be empty.
"A series can carry up to 120 passes."The ceiling on one slate.
"Two passes in this series run at the same time…"Prevent Overlapping Passes is on and the slate holds a clash. The message names the first offending pair. Remove one, or turn the guard off if holders are meant to attend both.
"Say how many passes this rule should take in."A count rule with no count is incomplete, not "all of them".
"A series cannot lead to itself."A successor loop would invite holders to buy the season they just finished.
"The next series must be another Pass Series in this project."A successor is a season, not a subscription, and not another project's plan.
"A seat cap of zero would put the series on sale with nothing to sell."Empty means unlimited; zero means nothing. Deactivate the plan instead.
"A holders-only presale can run from 1 hour up to a year."Below an hour nobody sees it; above a year it is not a presale.

Mixing pass plans whose timezones differ is refused too, naming both zones. A series has no timezone of its own — it renders its timetable in its source plans' — so two disagreeing zones leave nothing to render in.

Automating around a series

EventFires
pass_series.leg_addedA rule absorbed a new pass into a live series — the one to re-sync a calendar on
pass_series.leg_substitutedA cancelled pass was replaced, carrying both windows
pass_series.leg_droppedA cancelled pass was dropped, carrying the pro-rata figure
pass_series.completedA holder's last pass closed, with final attendance
pass_series.presale_openedThe holders-only window on the next season opened

The ordinary pass.* events still fire for each individual window, because each date is a real window on a real plan — a series does not replace them.

Questions

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request