A document can be offline, live, or changed (pending review and re-publication). The publication state of the document is expressed through an icon in the "State" column of the [Content Application](🔗):
**Document States**
Offline This document is currently not published, so it cannot be accessed through the website.
Live This document is currently published and you can access it through the website.
Changed A published (previous) version of the document is accessible on the website, but the document has been changed and a newer version is waiting to be published. This is a useful feature for when you have new content that is set to replace the existing content at a later point in time.
When a new document is created, it enters the _Offline_ state. Authors can request publication from users that have editor privileges.
**Tip:**
A publication request can also be submitted for a document from within the Experience manager. See [Manage Content in a Channel](🔗) to learn more.
If an author submits a request, a message is shown to editors and admins within the document editor:
They can then choose to either accept or reject the request.
On accepting the request, the document is published and is now _live_.
On rejecting the request, the editor or admin can leave a message for the author explaining the reasons why they have rejected the changes:
The author can view this message by clicking on _Requests > Show rejected requests_ in the document view:
Editors and admins can also create and publish documents directly from the document view.
When a published document is adjusted, it enters the _Changed_ state. In this state, the old, published, and unchanged version of the document is still visible on the website, while the new, changed version is visible in the _Document Viewer_ and the _Experience manager's_ preview. In this state, the Document Viewer highlights the changes compared to the previous live version. The changes get published to the website when the editor (re-)publishes the document.
**Tip:**
A document can also be published from within the Experience manager. See [Manage Content in a Channel](🔗).