Skip to main content

​
Overview

A Publishing Window is a named, reusable time range (start_at → end_at) that drives scheduled publication of content. Instead of entering publish/unpublish dates by hand each time, point a Content Version’s schedule at a window: the version is published at the window’s start and unpublished at its end. One window can schedule many versions at once — and editing it re-syncs all of them. For the bigger picture, see the Content overview.

​
Where to find it

Publishing windows live under Content → Utilities → Publishing Windows. You apply one from a Content Instance’s schedule, where “use a publishing window” is offered alongside manual dates.

​
Properties

PropertyTypeRequiredDescription
titlestringYesDisplay name.
slugstringYesIdentifier, unique (a–z, 0–9, -).
descriptionstringNoOptional description.
start_atdatetimeYesThe publish time for bound schedules.
end_atdatetimeYesThe unpublish time — must be after start_at.
enabledbooleanNoWhether the window’s schedules are active.

​
Behaviour & rules

  • Window-driven dates — start_at becomes the publish time and end_at the unpublish time for every schedule bound to the window.
  • Live re-sync — changing a window’s start_at / end_at updates every schedule that uses it. (Editing other fields doesn’t move schedules.)
  • Past dates act immediately — moving start_at or end_at into the past publishes or unpublishes the pending content right away.
  • Enable / disable — disabling a window cancels its pending schedules; re-enabling reactivates them. Already-executed actions aren’t reversed.
  • Also drives orchestration schedules — scheduled Events & Automation can reference a window too, and stay aligned when the window changes.
A window stores absolute start_at / end_at. Manual schedule dates are interpreted in the user’s timezone and stored in UTC — so send a timezone when scheduling manually.

​
Seeds

Publishing windows travel between environments as structural Seeds: 
[
  {
    "object_type": "publishing_windows",
    "data": {
      "title": "test",
      "slug": "test",
      "start_at": "2026-06-03T06:00:00.000000Z",
      "end_at": "2026-06-07T18:00:00.000000Z"
    }
  }
]

​
Governance & permissions

Only a super admin or Master can create, edit, enable/disable, and delete publishing windows.

​
API access

Publishing windows have full CRUD, and a version’s schedule is created, updated, cancelled, and listed through the instance’s schedule-publish operations. See the API reference.

Content Versions

The versions a window publishes and unpublishes.

Content Instances

Where you apply a window to a version’s schedule.

Events & Automation

Scheduled automations can reference a window too.