Who this is for: studio operators (admin panel) · Product: Podyx V2
A slot blocker holds time on your calendar when there is no booking to hold it. Maintenance, a personal commitment, a setup day, or simply time you do not want sold. To your clients it behaves exactly like a booking: the slot is gone from your booking page.
🎥 Watch the walkthrough
🔧 Where to find it
Admin Panel → Block Slots, and directly from your calendar.
🔄 Your synced calendar creates them automatically
When you sync a calendar, every existing event is imported immediately as a slot blocker. Imported items keep the event names from the source calendar. They do not arrive as bookings, but they do block availability on your booking page and they carry their own buffer time, so external commitments protect your schedule without you copying anything across by hand.
➕ Create one yourself
From the calendar you can create a slot blocker, a booking, or a bundle booking. Use a slot blocker whenever you need to hold time and there is no real reservation behind it.
🗂 Manage them on the Block Slots page
Filter by room to see which blockers apply where.
Filter by date range to focus on a period.
Remove blockers you no longer need.
Review what is active in one centralized list.
💡 Do you still need them?
With two-way calendar sync and room-level availability, slot blockers are less essential than they used to be, because a lot of blocking now happens on its own. They are still genuinely useful as a ledger of blocked time: a clear, filterable record of why a slot was unavailable, which a raw calendar does not give you.
⚠️ Blockers and conflicts
Podyx will not allow two slot blockers on the same time at once. If overlapping events appear through your synced calendar, they surface in the Conflicts tab so you can decide which one should win.
✅ Summary
Use slot blockers to hold time that is not a booking. Synced calendar events become blockers automatically, and you can add your own from the calendar. Manage the whole set from Block Slots, filtered by room and date range, and let the Conflicts tab handle any overlaps.
Related: In-app Calendar · Conflicts · Availability · Connect Google Calendar