> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-content-administration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-content-administration/workflows/moderation-states.md).
# Moderation states
Content moderation is a GovCMS module that provides a default workflow process. In this model content has four "states":
* **Draft**: In this state the changes are not available to the public.
* **Needs Review**: The changes are still not available, ideally they are reviewed and approved by a second user.
* **Published**: The changes are made live for the public.
* **Archived**: The page is taken **off-line** and not visible to the public, but kept in the CMS for record-keeping.
Content *transitions* as it moves from one state to another.
Different people with different roles have different permissions regarding what actions they can perform in the content workflow. For example, in the default setting, Content Authors cannot publish content. Only a Content Approver can approve content.
This default workflow can be extended by a developer or advanced content editor.
{% hint style="info" %}
In the GovCMS training environments you're given both Content Author and Content Approver roles.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://salsa-digital.gitbook.io/govcms-content-administration/workflows/moderation-states.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.