Approving and publishing are two steps. A draft you have not approved does not go out. A draft you have approved is still not live until it is published and the build finishes.

Approve and publish

When a draft is ready, the action is "Approve and publish." If you do not have permission to publish, a publisher has to confirm it. You can ask someone else who can publish.

The Work label moves to Approved, then to Shipped when it has gone out. Ready for review is the moment you still have the draft in front of you.

In Studio, publishing has two choices. Publish to staging only updates the private staging site so your team can check it. Publish to staging and production makes it live. Only people with production permission see the second choice. The site shows which version it is on. An owner can roll back a production publish, then fix and publish again.

Header, footer, and the closing band are shared by every page. Those are a request, not a field you edit on one page.

If publishing is paused

Someone who manages the site can pause publishing. A reason is required. While publishing is paused, nothing is published. Resume is the same control. Editing in Studio still works when the Console cannot be reached. Publishing still has to succeed before the live URL is the new page.

Saving is a draft. Publishing is not proof the live page has updated until the deploy finishes. On a static site that is usually a minute or two. If a deploy sticks, tell Everbase. Do not force a second publish until the live page has been checked.