A Shift Series lets you set up recurring shifts from a single pattern instead of building each shift by hand. This article explains what a Shift Series is, how it differs from a regular shift, how to create and manage one, the Opportunity settings that control it, and how users join and leave a recurring schedule.
A Shift Series is a set of recurring shifts created from one shared template and a repeat pattern (for example, "every Tuesday from 9:00 AM to 12:00 PM").
Instead of creating each shift by hand, you define the pattern once and Vome generates the individual shifts for you automatically.
A helpful way to think about it: the series is the rule, and each shift is a real, dated event created from that rule, much like a recurring event on a calendar.
This is ideal for:
A regular shift exists on a single date (or a few set dates), and users reserve one shift at a time.
A Shift Series works differently:
A note on future shifts: Vome creates shifts roughly six months ahead and keeps extending the schedule automatically. Dates beyond that window appear as read-only "Upcoming recurring shift" rows. There is nothing to do for those. They are scheduled automatically as the date approaches, and the user's spot is already held.
When creating shifts, choose "Recurring shifts" instead of a single or consecutive date.
Then set:
When you create an open-ended series, Vome generates roughly the first six months of shifts right away and continues adding future shifts automatically. Later auto-generated shifts will not re-send the "new shift" notification for the Opportunity.
You can edit a series in two ways.
Editing from the calendar with a scope. When you open a shift that belongs to a series, you choose how widely your change applies:
The same scope choice applies when you cancel a shift, assign users, or remove users.
A few things to know:
Editing the series template directly. Open "Manage recurring series," select a series, and edit the template (title, capacity, and so on). Your changes apply to every active future shift in the series and to new shifts generated later.
This is the most common question, so here is exactly how it works.
When you edit a single shift, Vome remembers which fields you customized on that shift. If you later make a series-wide edit (this and future, or all), Vome respects those customizations and skips any field you changed individually. Your one-off change survives the bulk edit.
If you want the series value to override a customization, the edit screen shows a checkbox: "Force every shift to match the series." This checkbox appears only when an affected shift has a customization, and it lists which fields were customized. Checking it clears those customizations first, so the new value applies everywhere.
Example:
You control this through the cancel scope:
Yes. You can act on a future occurrence even before Vome has generated it. Vome records your change (a skip or an edit) and applies it automatically when it generates that date. Already-created shifts are edited or cancelled directly.
Shift Series behavior is controlled at the Opportunity level, on the Opportunity customize page under "Shift series settings."
By default, series are invisible to users, so existing Opportunities behave exactly as before until you choose to turn this on.
Reservation policy
Cancellation policy
Other settings
In addition, if the Opportunity is set to request to book, series joins are submitted for approval. An administrator must approve the request before the user is added to the shifts.
When the Opportunity allows it, a user selects "Join recurring schedule." Depending on your settings, the join screen may include:
After joining:
Joining a series reserves every upcoming shift in the series, plus every new shift the coordinator adds later.
Users cannot pick only some occurrences when joining a series. They join the whole schedule. If you want to allow single-shift reservations instead, set the reservation policy to Allowed so users can reserve individual shifts one by one.
The leave screen lets a user choose the scope:
If your cancellation policy follows the shift, any shift already inside its cancellation window stays on the user's schedule and they are still expected to attend. If cancellation is disabled, the user is asked to contact their coordinator.
If I add a new recurring shift months from now, does it notify everyone again?
No. Auto-generated shifts past the initial window do not re-send the "new shift" notification. Users already on the recurring schedule are simply added to them.
Can a user reserve just one week of a series?
Only if the reservation policy is Disabled or Allowed. If it is Required, the user must join the whole series. Admin only hides series shifts from users entirely.
A user joined indefinitely. When do they stop being scheduled?
When they leave, or an administrator removes them. Past attendance is always kept.
I customized one shift and it did not change when I edited the whole series. Is that a bug?
No, this is intended. See question 5. Use "Force every shift to match the series" if you want the customization overwritten.
Why do I see greyed-out "Upcoming recurring shift" rows with no buttons?
Those are future shifts beyond the current generation window. They are scheduled automatically as the date approaches, and the spot is already held. There is nothing to do.