What it does
Improves how Draft Events work by introducing stronger access control and clearer pre-launch protection. Events are created in a draft state designed for setup and testing, while public access stays locked until the organizer is ready to launch.
Participants who are not part of the organizer team cannot enter or view the event while it remains in draft, ensuring that unfinished content, navigation, and configuration stay private.
Why it matters
🚧 Confident pre-launch setup
Organizers gain a safe space to build and test events without worrying that attendees will see incomplete pages, placeholder content, or unfinished configurations.
🔒 Controlled visibility
Draft events remain hidden from public participants, helping organizers manage launch timing and avoid confusion (especially important for Engagement Hub workflows where events may be created well before go-live).
🧪 Safe internal testing
Dashboard users and authorized team members can still access the event for quality assurance, testing, and configuration checks, ensuring everything is ready before launch.
✨ Cleaner launch experience
Attendees only see the event once it’s fully prepared, creating a stronger first impression and a more polished experience from day one.
The result
A clearer separation between building and launching, giving event organizers full control over when their event becomes visible, and ensuring participants only arrive when everything is ready.
