What is the Changes workspace?

The Changes workspace is where you keep your Help Center in step with your product. It collects everything that has landed in your connected repositories, describes each change in plain language, checks it against your documentation, and holds the docs proposals until someone decides on them. You'll find it as Changes under Maintain in the sidebar. It used to be called Handoff.

The views

The views list on the left sorts your changes into shelves, so you can pick the slice you care about right now.

"What's new": Shows a count of unread changes. When no change is selected, the detail pane shows a brief addressed to you, such as "You're all caught up." or "N changes since you were here on Tuesday.", with changes grouped by day ("Today", "Yesterday", weekday names). A "N need you" link leads to "Needs review".

"Needs review": Always shows its count, zero included. If it says "Nothing needs you.", there's nothing waiting on you.

"All changes": The full history of changes.

"In the docs" and "Not for the docs": Group changes by their documentation outcome. "Not for the docs" holds the changes someone has explicitly marked that way.

The change list

The middle column lists the changes in the view you've opened, with the view name and row count at the top. A filter strip lets you search and filter by Help Center.

Each row shows the change's headline plus a line with a "new" marker for unread items, Help Center dots, the time, audience tags, and a status pill. Rows are grouped under week headings. When a view is empty, it tells you so plainly, for example "Nothing in the docs yet."

The change detail

Open a change and the detail pane shows what it is and where its documentation stands.

A change is one product change as you'd describe it to a person, and it can be made up of several related parts. The individual deltas sit together under a collapsible "Parts (N)" section, so you review them as one change instead of hunting through separate commits.

The main card carries the change's title and a plain-language description, followed by a "Who notices:" row and a "For support:" row. If the change sits behind a feature flag, a note says so. Chips under the title show the change type, intent, surface, audiences, span, a "flagged" chip for gated releases, a "major" chip where it applies, and the Help Center badge.

The Documentation section comes last and starts collapsed. Its header carries a state chip that tells you where the change's docs work stands. Opened, it explains that state, offers an "Add article" sheet with "Existing article" and "New article" modes, and shows the changeset below.

Documentation proposals and the changeset

A changeset is the set of documentation proposals for one change: the article updates the workspace suggests based on what shipped. You can edit a proposal in its card, then accept or discard it. Accepted proposals can be applied to a Help Center.

All of this happens through the action bar at the bottom of the detail pane. Its left side states what the change is waiting for. The primary button changes with the state, reading "Create proposals", "Accept all (N)", "Apply all (N)", "Close changeset", or "Try again" after a failure. Quieter buttons such as "Re-plan", "Check again", "Discard all", and "Add article" sit next to it. The Documentation section is for reading. Every change you make goes through the bar.

When a change affects several Help Centers, a row of Help Center tabs appears in the detail pane. Picking one switches which Help Center the Documentation section and its proposals refer to.

For the full review-and-apply workflow, see "How to update your help articles after every product release".

Hiding a change vs. "Not for the docs"

Both live in the action bar's overflow menu, and they mean different things.

"Not for the docs" is a verdict. It records that a change needs no documentation. It asks you for a reason and, when the change affects several Help Centers, whether the verdict applies everywhere or only to the current Help Center. These changes then appear in the "Not for the docs" view.

"Hide" removes a change from the shelves without recording a documentation decision. A hidden change offers "Unhide" to bring it back.

Availability

Anyone with access can read changes, their descriptions, and their documentation state. Creating, editing, accepting, applying, hiding, and marking changes is limited to admins. In read-only mode, the action bar doesn't appear. Changes only show up once Git sources are connected and analyzed under Settings → Git sources.