# Publish updates

After a month is published, later edits stay on Assign shifts until you publish updates. Staff still see the last published version. Publishing updates does not create pay.

![Publish updates](/files/help/manager-publish-schedule-2.mp4 "The month is already published. Discard changes is opened, then closed.")

1. Open **Assign shifts** for a month that is already live. The chip reads Updates waiting when edits are not live yet.
2. Choose **Publish updates**.
3. Read the summary. The dialog says staff still see the last published version, and publishing replaces that with the assignments on this page.
4. Leave **Email assigned staff** on unless this update should not send email. Leave **Also send a text** off unless you mean to text.
5. Choose **Publish updates** in the dialog when you mean for staff to see the new month. The clip does not press it.

## What you should see

The confirmation says the updates are now live for staff. The chip changes to Published, and the subtitle says staff see this month.

While the chip is Updates waiting, the tooltip says edits on this page are not live until you publish updates.

## If something looks wrong

**Publish** is the first-time button. **Publish updates** is the button after a published version already exists. Use the one that is on the toolbar.

**Publish updates** in the dialog stays unavailable while blocking conflicts remain. The dialog says to resolve them before publishing. Warnings can stay on the record if you continue after you have reviewed them.