> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/content-designers/content-workflow.md).

# Content Workflow

Varbase moves blog posts and utility pages through a publishing workflow, so nothing reaches visitors before it is ready. This page explains the states, who can change them, revisions, scheduling, the Trash, and the two safety features that protect your work while you edit: content locking and autosave. The workflow is where a website meets an organisation's way of working.

Watch the lesson: [Editorial Workflow](https://docs.varbase.vardot.com/content-designers/varbase-content-designers-course/lesson-06-editorial-workflow.md) in the [Varbase: Content Designers Course](https://docs.varbase.vardot.com/content-designers/varbase-content-designers-course.md).

## Why It Matters

* **Separation of duties** when the client needs it: one permission decides whether editors publish themselves or send to a reviewer.
* **Campaign timing** without someone online at midnight: publish and unpublish on a date.
* **Recoverable mistakes**: revert a revision, restore from the Trash.
* **A record**: every save, note and state change is kept, which public-sector clients often require.

## Moderation States

**Blog post** and **Utility page** use the **Editorial** workflow, which has four states:

| State                      | Visible to visitors | Use it for                                         |
| -------------------------- | ------------------- | -------------------------------------------------- |
| **Draft**                  | No                  | Content you are still writing.                     |
| **In review**              | No                  | Content waiting for someone to check it.           |
| **Published**              | Yes                 | Live content.                                      |
| **Archived / Unpublished** | No                  | Content taken off the site but kept for reference. |

A published item can have a newer draft. Visitors keep seeing the published version until you publish the draft. New content starts as a **Draft**, so nothing goes live because someone clicked **Save** too early.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-57ce1394b006e262f6a31066708802124cc1b096%2Flearn-06-editorial-workflow-states.png?alt=media" alt="The Edit Editorial workflow page listing the states Draft, In review, Published and Archived / Unpublished, with the Transitions section below"><figcaption><p>The Editorial Workflow and Its Four States</p></figcaption></figure>

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-e5fcc6a587067a45c6c6abbbff036689de756de3%2Fworkflow-overview-01-states.png?alt=media" alt="The moderation block in the sidebar of a blog post edit form, showing Current state Draft and the Change to list"><figcaption><p>The Moderation Block in the Edit Form</p></figcaption></figure>

## State Transitions

| Transition               | From                                                | To                     |
| ------------------------ | --------------------------------------------------- | ---------------------- |
| **Create new draft**     | Draft, In review, Published, Archived / Unpublished | Draft                  |
| **Send to review**       | Draft, In review                                    | In review              |
| **Publish**              | Draft, In review, Published                         | Published              |
| **Archive / Unpublish**  | Published                                           | Archived / Unpublished |
| **Restore from archive** | Archived / Unpublished                              | Published              |

The **Change to** list in the edit form shows only the states the item can move to. For the steps, see [Publish Content](https://docs.varbase.vardot.com/content-designers/content-workflow/publish-content.md).

To review or change the workflow, go to **Administration** \ **Configuration** \ **Workflow** \ ***Workflows*** (`/admin/config/workflow/workflows`) and edit **Editorial**. Its page lists the **States**, the **Transitions**, the content types under **This workflow applies to:** and, in **Workflow Settings**, the **Default moderation state** (**Draft**).

{% hint style="warning" %}
On some sites the **Workflows** page also lists **Basic page** under the **Basic** workflow. Blog posts and utility pages use **Editorial**; read the **Editorial** workflow for how they move.
{% endhint %}

## Editorial Roles and Permissions

On a new Varbase site, the **Content editor**, **SEO Admin**, **Content Admin** and **Site Admin** roles can use every **Editorial** transition, including **Publish**. **Super Admin** has unrestricted access.

If your team needs a review step before content goes live, remove the **Editorial workflow: Use Publish transition** permission from the roles that should only send content to review. Set this at **Administration** \ **People** \ ***Permissions*** (`/admin/people/permissions`), in the **Content Moderation** group; type `Editorial workflow` in **Filter by permission name** to see each transition's row.

See [Default Roles and Site Personas](https://docs.varbase.vardot.com/content-designers/user-management/default-roles-and-site-persons.md) for details on each role.

## Content Locking and Autosave

### Content Locking

When you open a blog post or utility page for editing, Varbase locks it so no one else can edit it at the same time.

* Another editor who opens it sees a message naming you, and cannot save changes.
* Opening the form shows the message "This content is now locked against simultaneous editing." On a new site it appears on every edit form, for your own lock; it is not an error.
* The lock is released when you click **Save**, or **Unlock** at the top of the form.
* A lock left behind ends by itself after 30 minutes.
* A **Content Admin** or **Super Admin** can release someone else's lock with **Break the lock.** in that message, or **Break lock** in the item's **Operations** on the content list.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-1495e61ef4ff649b06e2384cf4204fa4d9552f31%2Fworkflow-overview-02-locked.png?alt=media" alt="A blog post edit form showing the message that the content is being edited by another user and is locked, with the Break the lock link"><figcaption><p>An Item Locked by Another Editor</p></figcaption></figure>

### Autosave

While a content form is open, Varbase saves a copy of your changes every minute and shows **Saving draft...** for a moment. The copy is private to you; it is not a revision and nobody else sees it.

If you leave the form without saving, the next time you open the item Varbase asks whether to **Resume editing** with that copy or **Discard** it.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-320ccb85f5266fa231ae02f74708fa519fdcd040%2Fworkflow-overview-03-autosave-resume.png?alt=media" alt="The autosave message on a blog post edit form, asking whether to resume editing or discard the saved draft, with the Resume editing and Discard buttons"><figcaption><p>Resuming an Autosaved Draft</p></figcaption></figure>

## Revisions

Every save creates a revision. The **Revisions** tab lists them, newest first, with who saved each one, when, and the note they left. Compare two revisions to read only what changed. **Revert** restores an older version as a new revision, so nothing is lost. See [Modify Content](https://docs.varbase.vardot.com/content-designers/content-management/modify-content.md#revisions).

To start a new post from an old one, such as this year's event from last year's, use the **Duplicate** tab. See [Duplicate a Post](https://docs.varbase.vardot.com/content-designers/content-workflow/duplicate-a-post.md).

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-3d10fe6af50142b884d261064f7d28f877e94f6f%2Flearn-06-revisions-with-revert.png?alt=media" alt="The Revisions tab of a blog post with one revision, its date, author and log message, and a Revert button"><figcaption><p>Revision History With Revert</p></figcaption></figure>

## Scheduling, Archiving and the Trash

* **Schedule** a publish date and an unpublish date in **Scheduling options**. Scheduled times follow the site's time zone, so state it in every instruction to editors in other countries. See [Scheduling Content](https://docs.varbase.vardot.com/content-designers/content-workflow/scheduling-content.md).
* **Archive** takes content off the site but keeps it and its revisions, and **Restore from archive** brings it back. A visitor following an old link gets a page not found response. Archive rather than delete content that was real.
* **Delete** sends the item to the **Trash**, with tabs for content, files, media, taxonomy terms and pages. Restore it as it was, or delete it for good if your role allows. See [Trash](https://docs.varbase.vardot.com/content-designers/content-workflow/trash.md).
* **Bulk actions** on the content list apply one action to many items. See [Bulk Edit Content](https://docs.varbase.vardot.com/content-designers/content-workflow/bulk-edit-content.md).

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-66faea4fc117d0d229b6d9a0a20026c2a0eac5d9%2Flearn-06-change-to-and-scheduling.png?alt=media" alt="The edit form of a published blog post with Change to marked in the sidebar and the Scheduling options group open, showing Publish on, Publish state and Unpublish on"><figcaption><p>Change To and the Scheduling Options in the Sidebar</p></figcaption></figure>

## Who Did What

Beyond revisions, Varbase keeps an **audit trail** of admin actions, such as content being created, edited, published or deleted, with who did it and when. Its settings, which list the events that are logged, are at `/admin/config/development/audit-trail/settings`. Agree with the client how long these records are kept: that is a policy decision, not a technical one.

{% hint style="warning" %}
On some sites the audit trail report (`/admin/reports/audit-trail/legacy`) is marked **Deprecated**, and no newer report replaces it yet. Ask your development team how to read the audit trail on your site.
{% endhint %}

## Drupal Canvas Pages Are Different

Drupal Canvas pages do not use the Editorial workflow. Every change in the Canvas editor is a private draft until someone opens **Review changes** and publishes it, and only **Content Admin**, **Site Admin** and **Super Admin** can publish pages. See [Preview and Publish](https://docs.varbase.vardot.com/content-designers/building-pages-with-drupal-canvas/preview-and-publish.md).

## In This Section

* [Publish Content](https://docs.varbase.vardot.com/content-designers/content-workflow/publish-content.md)
* [Scheduling Content](https://docs.varbase.vardot.com/content-designers/content-workflow/scheduling-content.md)
* [Bulk Edit Content](https://docs.varbase.vardot.com/content-designers/content-workflow/bulk-edit-content.md)
* [Trash](https://docs.varbase.vardot.com/content-designers/content-workflow/trash.md)
* [Duplicate a Post](https://docs.varbase.vardot.com/content-designers/content-workflow/duplicate-a-post.md): start a new post from an old one.
* [Take a Post Through Review](https://docs.varbase.vardot.com/content-designers/content-workflow/take-a-post-through-review.md): the author sends a post to review, a reviewer publishes it or sends it back.
* [Design the Workflow With a Client](https://docs.varbase.vardot.com/content-designers/content-workflow/design-the-workflow-with-a-client.md): match the client's way of working to the lightest setup that meets their rules.

## Best Practices

1. **Start with Draft.** Use **Send to review** when someone else should approve the content.
2. **Write revision log messages** that say why the state changed, for example "Approved by editor".
3. **Archive rather than delete** content you may need again.
4. **Save or unlock when you finish**, so colleagues are not locked out.
5. **Review permissions regularly**, so each role has the access your process needs.
