Configure content workflows | Doghouse SaaS Knowledge Base [Skip to content](#main) [ ![Doghouse SaaS Knowledge Base](/storage/branding/01M3N8PQ7PSDNQBBKKJM6XGW03.svg) ](https://nginx.deploy-lagoon-production.districtcms-docs.dh1.amazee.io) [Product documentation](/articles) [Roadmap](/roadmap) Toggle navigation [Product documentation](/articles) [Roadmap](/roadmap) 1. [Home](/) › 2. [Product documentation](/articles) › 3. [Content workflow](/articles?category=9) › 4. Configure content workflows Configure content workflows =========================== Updated 5 days ago · 4 min read Search Search Overview -------- A workflow is how you stop content going live before somebody has checked it. Without one, a content type has a single **Published** tick on its editing form, so saving and publishing are the same decision, taken by whoever happens to be typing. With one, that tick is replaced by a state, and the moves between states are handed out role by role. An author can write something and leave it as a draft; only the people you nominate can move it to published. Two rules shape everything on these screens. The first is that a workflow is set per content type, not per item, so a change here lands on every page of that type at once. The second is that a content type belongs to one workflow only, which is why an approval step wanted for news alone usually means a second workflow rather than a new state on the one you already have. > **⚠️ Important:** This is administrator work. Content editors cannot reach these screens. --- Finding the workflow -------------------- Go to **Configuration**, then **Workflow**, then **Workflows**. The list holds two workflows. Workflow States In use Basic Draft, Published, Unpublished Yes. It covers Article, Event and Landing page. Editorial Draft, Published, Archived No. It covers no content types, so it does nothing until a type is put under it. Content editors already hold permission to use its transitions. ![The Workflows list, outlined in red, showing Basic with Draft, Published and Unpublished, and Editorial with Draft, Published and Archived.](/storage/8BHtRzn2Qkd8JuayD0EA2fsmLJ0RyX0jOdH0Yb16.png) Press **Edit** beside the workflow you want to change. The screen that opens has four parts. Part What it sets States The states content can be in. Here they are Draft, Published and Unpublished. Transitions Which moves are allowed, and from which states. Here they are Create new draft, Publish and Unpublish. This workflow applies to Which content types the workflow governs. Workflow Settings The **Default moderation state**: the state new content starts in. --- Putting another content type under the workflow ----------------------------------------------- All three content types are already under **Basic**, so you need this when a new content type is added, or to bring another kind of item under a workflow. The list covers more than content: content block types, media types and taxonomy term types can be put under a workflow too. 1. Open the workflow for editing. 2. Under **This workflow applies to**, press **Select** beside **Content types**. 3. Tick the content types you want covered. 4. Press **Save**. ![The This workflow applies to section of the Basic workflow, with the Content types row outlined in red, listing Article, Landing page and Event beside its Select button.](/storage/p2wOWrUO7kAwFnBqRWQL6Dgok0dKCFzX3lMC3L2r.png) > **⚠️ Important:** Do this on a type that already has content and every existing item is brought into the workflow. Nothing is lost, but the editing form changes for everybody working on that type, so tell them first rather than after. --- Adding a state or a transition ------------------------------ A review step is the usual reason. It takes two pieces: a state for content to wait in, and a transition allowing content to reach it. Open the workflow for editing and work down the screen. **States** and **Transitions** are the first two of its four parts, and each button sits beneath the list it adds to. - Under **States**, press **Add a new state**. Give it a name, and say whether content in it is published. - Under **Transitions**, press **Add a new transition**. Name it, tick the states it can start from, and choose the state it ends in. > **💡 Note:** A state with no transition leading to it is unreachable, and content can never enter it. Adding the state is only half the job. Each transition also carries its own permission, so after adding one, decide which roles may use it. See [**Roles and what they let you do**](/articles/roles-and-what-they-let-you-do). --- When one workflow is not enough ------------------------------- A kind of content can sit in one workflow and no more. So if news articles need an approval step but other pages should keep the simple three states, you cannot get there by adding a state to the workflow they share, because every type that workflow covers would get it too. The answer is a second workflow. Check **Editorial** first: it already exists, and its **Archived** state may be what you need. 1. Go to **Configuration**, then **Workflow**, then **Workflows**. 2. Press **Add workflow**. 3. Give it a **Label**, and choose **Content moderation** as the **Workflow type**. It is the only kind offered. 4. Press **Save**. You then build its states and transitions, and choose the content types it applies to, exactly as described above. > **💡 Note:** Putting a content type into a new workflow takes it out of the old one, since it can only be in one. Existing content comes across, and from then on the states it can be in are whatever the new workflow defines. A workflow that is no longer wanted can be removed from the list: press the arrow beside **Edit** and choose **Delete**. Any content type it covered stops being governed by a workflow and goes back to the plain **Published** tick. Related articles ------------------ - [ Roles and what they let you do → ](/articles/roles-and-what-they-let-you-do) - [ Scheduling content to publish later → ](/articles/scheduling-content-to-publish-later) - [ Content workflow and statuses → ](/articles/content-workflow-and-statuses) Was this article helpful? ------------------------- Your feedback helps us prioritise what to rewrite. Yes No [ Back to Content workflow ](/articles?category=9) On this page **Need additional help?** Submit a support request through the [**support portal** ](https://doghouse.atlassian.net/servicedesk/customer/portals)or email © 2026 [Doghouse SaaS](https://doghouse.agency) [Glossary](/articles/glossary)