> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onset.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Publishing & Scheduling

> Publish now or later, and notify subscribers, Slack, and Discord in one step.

## Publish a release

Click **Publish** in the release editor. The publish dialog is where you decide who gets told:

* **Email notification** sends to your subscribers. Choose which [subscriber lists](/guides/subscribers/lists) to notify.
* **Slack notification** posts to a channel in your connected [Slack](/integrations/slack) workspace.
* **Discord notification** posts to a channel in your connected [Discord](/integrations/discord) server.

Notifications are opt-in per release, so a typo fix doesn't have to email everyone.

## Schedule for later

In the publish dialog, choose **Schedule** and set a date and time. The release stays in **Scheduled** state and publishes automatically, including any notifications you enabled.

<Note>
  Scheduled releases are available on the Team plan and above. See [Billing](/guides/billing).
</Note>

### Timezones

There is no workspace timezone setting. The time you pick is interpreted in **your own browser's timezone** at the moment you set it, then stored as an absolute point in time.

So a release scheduled for 9:00 AM by someone in Berlin goes out at 9:00 AM Berlin time. It will show as 3:00 AM to a teammate in New York looking at the same release. The release goes out at one fixed instant for everyone; only the displayed local time differs.

<Tip>
  If you're coordinating a launch with someone in another region, agree on the absolute moment rather than the wall-clock time. "9:00 Berlin" is unambiguous, "9:00" is not.
</Tip>

### Scheduling window

* The earliest you can schedule is **tomorrow**. You can't schedule a release for later today; publish immediately instead.
* The latest is **two months out**.

### Changing a schedule

You can change or clear the scheduled time at any point before it goes out.

<Warning>
  Clearing the date on an already-scheduled release publishes it immediately. To keep it unpublished, move it back to **Draft** first.
</Warning>

## Customizing notification emails

The sender address and subject line are configured workspace-wide:

* [Custom from address](/email/custom-from-address) sends from your own domain
* [Custom subject](/email/custom-subject) uses dynamic placeholders in the subject line

## Republishing

Editing an already-published release updates it everywhere immediately. It does **not** resend email, Slack, or Discord notifications, so you can fix a typo without a second announcement.