Purpose: This article explains how to publish or unpublish an Event in Administrate and how those status changes affect visibility, enrollment, communications, and operational delivery.
Publishing is the point where an Event moves from internal preparation into active operational use. Because learners, communications, and financial activity may depend on the Event after publication, publishing should happen only after structural review is complete.
Before you begin: Create an Event | Understanding the Event Screen
What publishing means
Publishing an Event changes it from a preparation-stage delivery record into an operationally available Event.
Depending on your configuration, publishing may:
- expose the Event in your learner portal or catalog
- allow learners or administrators to enroll participants
- enable operational workflows tied to the Event lifecycle
- trigger communications depending on your automation setup
Caution
Publishing should not be treated as a minor visibility toggle. Once learners begin enrolling or communications begin firing, later structural changes can affect attendance tracking, reminders, financial records, instructor scheduling, and learner expectations.
Publish an Event
- Open the Event.
- Navigate to the Setup tab.
- Change the Status to Published (or the equivalent operational status used by your organization).
- Save changes.
After publishing, review learner-facing visibility and confirm the Event appears as expected in any relevant enrollment workflows or portals.
Pre-publication review
Pre-publication checklist:
- Confirm all session dates and times.
- Verify instructor assignments and availability.
- Review capacity limits and registration controls.
- Confirm pricing and financial configuration.
- Ensure visibility settings match the intended audience.
- Review any communication triggers tied to registration or publication activity.
Publishing before review can create operational issues such as incorrect learner exposure, scheduling conflicts, communication failures, or inaccurate enrollment availability.
Unpublish an Event
Unpublishing removes operational visibility from an Event and prevents future enrollment activity, but it does not reverse operational history that already exists.
- Open the Event.
- Navigate to the Setup tab.
- Change the Status from Published to the appropriate alternative status (for example Draft).
- Save changes.
What unpublishing does
- removes the Event from learner-facing visibility where applicable
- prevents new enrollments
- preserves existing learner participation, attendance, communications, and financial records
Note
Unpublishing does not automatically cancel learners, void invoices, reverse attendance, or remove communications that were already sent.
Publishing versus canceling
Unpublishing and canceling are different operational actions:
- Unpublishing removes visibility and enrollment availability
- Canceling changes the operational status of the delivery itself
An unpublished Event may still exist as a planned or paused delivery record, while a canceled Event represents a delivery that is no longer expected to occur.
Important considerations
- Publishing does not override capacity limits or registration rules.
- Unpublishing does not automatically cancel the Event.
- Status changes may trigger communications depending on your configuration.
- Structural edits become riskier after enrollment begins because learners, instructors, finances, and communications may already depend on the Event.
Best practices
- Keep Events in Draft until Setup and Outline review is complete.
- Publish only after dates, instructors, pricing, and visibility are verified.
- Review communication triggers before exposing learner-facing enrollment.
- Treat post-enrollment structural changes as operationally high impact.