> ## 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.

# Overview

> How release notes work in Onset, from draft to published.

A **release** is a single update you publish to your customers. Each one has a title, a body, and optional extras like a version number, labels, contributors, and a change list.

## Release states

| State         | What it means                                                       |
| ------------- | ------------------------------------------------------------------- |
| **Draft**     | Only visible to your team. Not on the public page, not in feeds.    |
| **Scheduled** | Written and queued to publish automatically at a set date and time. |
| **Released**  | Live on your public page, in your feeds, and in the widget.         |

## Where a published release shows up

* Your **public page** (`yourslug.onset.io` or your [custom domain](/page/custom-domains))
* Your **RSS, Atom, and JSON [feeds](/guides/page/feeds)**
* The in-app **[widget](/developers/widget/overview)**, if installed
* **Email**, **Slack**, and **Discord**, if you enable those notifications when publishing

## Anatomy of a release

<AccordionGroup>
  <Accordion title="Title and permalink">
    The title is what customers see first. Onset generates a permalink from it,
    which you can edit under **Permalink**. Worth setting deliberately if you
    plan to link to the release from elsewhere.
  </Accordion>

  <Accordion title="Body">
    The main content. Supports rich text, Markdown, images, and media embeds.
    See [Writing releases](/guides/releases/writing).
  </Accordion>

  <Accordion title="Change list">
    A structured list of individual changes, each tagged with a change type like
    **New**, **Fixed**, or **Security**. Good for long releases where the body
    is a summary and the change list carries the detail. Change types are
    customizable; see [Writing releases](/guides/releases/writing).
  </Accordion>

  <Accordion title="Version">
    An optional version number and pre-release flag. See
    [Versioning](/guides/releases/versioning).
  </Accordion>

  <Accordion title="Contributors">
    Workspace members to credit on the release. See
    [Contributors](/guides/releases/contributors).
  </Accordion>

  <Accordion title="Projects and labels">
    Used to organize and filter releases. See [Projects](/guides/projects) and
    [Labels](/guides/labels).
  </Accordion>

  <Accordion title="Attachments and related items">
    Files, links, and connections to roadmap milestones this release delivers.
  </Accordion>
</AccordionGroup>

## Publishing settings for the whole page

Some options are page-wide rather than per-release. Under **Settings → Page → Releases** you can turn the releases section on or off, choose the default view, and toggle whether contributors, reactions, and AI summaries are shown.