TYPO3 Workspaces: Edit, Review, and Publish Content Securely

TYPO3 Workspaces let you prepare changes to a website without them immediately appearing on the live, publicly visible site. Editors can work on content over an extended period, prepare changes together, or establish a binding approval process.

With the growing use of AI in content maintenance, workspaces take on added importance: an AI can prepare and modify content, while the final decision about publishing stays with a human.

1. General Overview

By default, editors in TYPO3 work in the so-called live workspace. Changes to published content become visible on the website immediately.

A dedicated workspace introduces an additional layer between editing and publishing. Changes are first saved within the workspace and aren't yet visible to regular website visitors.

Within a workspace, you can, for example:

• modify existing content,
• prepare new pages and content elements,
• delete or move content,
• bundle several related changes together,
• review changes via the preview,
• have changes checked by other people before publishing.

Only once the changes are published does TYPO3 apply them to the live workspace.

The major advantage is that extensive changes can be prepared calmly, while the website's current version stays unchanged and online.

2. Installation and Setup

Workspace functionality is part of the TYPO3 core. The prerequisite is that the workspaces system extension is installed and activated.

A new workspace can then be created in the TYPO3 backend.

To do this, switch to the top level of the page tree (root, ID 0) and create a new record of type Workspace there.

For a workspace, you can define users and user groups, among other things, along with their respective permissions and approval stages.

Once set up, authorized backend users can switch between the normal live workspace and the created workspace.

What a user can do there depends on the respective configuration and their TYPO3 permissions.

3. Typical Use Cases for TYPO3 Workspaces

Workspaces can be used in very different ways. Scenarios range from a single editor's personal working environment to multi-stage approval processes.

3.1 Standalone Workspace

A very simple use case is a personal workspace for a single editor.

Suppose an editor wants to revise a larger section of a website. The work takes several days and involves changes to various pages and content elements.

On the live system, that would be problematic: visitors might see a partially revised, and therefore potentially inconsistent, state of the website in the meantime.

The editor therefore works in their own workspace.

There, they might, for example, change a page on Monday, add further content on Tuesday, and swap out images or text on Wednesday. Using the preview function, they can check at any time how the website would look with all changes made so far.

The publicly visible website remains unchanged in the meantime.

Only once the entire revision is complete are the changes applied to the live workspace together.

A standalone workspace like this is therefore particularly suitable for more extensive changes meant to be published as a cohesive package.

3.2 Editorial Approval Process

Another classic use case is an editorial approval process.

In larger organizations, editors are often allowed to create and modify content, but not to publish it independently.

TYPO3 Workspaces enable exactly this kind of division of responsibilities.

An editor first creates or modifies content within the workspace. Once their editing is complete, they mark the changes for further processing or publication, for example as "Ready to Publish."

The person or group responsible for approval can be notified about the new status.

The responsible editor or approver can then review the changes made and view the result in the preview.

After that, there are generally two options:

• The changes are fine and are applied to the live workspace.
• The changes need revision and go back to the responsible editor.

This makes it possible to establish a four-eyes principle for publishing website content.

This is useful, for example, for companies, public authorities, associations, or academic institutions where content must be reviewed professionally or organizationally before publication.

3.3 AI-Assisted Content Maintenance

A particularly interesting use case arises from the growing integration of AI systems into content management systems.

An AI could, for example, be given the task:

"Update all references to TYPO3 13 on our service pages and adapt them to TYPO3 14."

Technically, it would certainly be possible to give an AI direct access to published content. However, that would also create the risk of faulty or unwanted changes appearing on the website immediately.

TYPO3 Workspaces can elegantly solve this problem.

The AI essentially takes on the role of an editor. It may create or modify content, but works exclusively within a workspace set up for this purpose.

The process might look something like this:

1. An editor gives the AI a task.
2. The AI analyzes the relevant content.
3. It makes the desired changes within the workspace.
4. The changes remain invisible to website visitors for now.
5. Once finished, the AI sets the changes to an appropriate approval status.
6. A responsible editor is notified, for example by email.
7. The editor reviews the changes in TYPO3 and, if needed, views them via the preview.
8. Only the human decides whether the changes are published or sent back for further revision.

This creates a human-in-the-loop process: the AI takes on part of the editorial work but doesn't have final control over published content.

This approach is particularly interesting for large websites. An AI could, for example, check numerous pages for outdated information, optimize metadata, update text, or prepare structural improvements.

The actual publication, however, remains a deliberate editorial act.

Conclusion

TYPO3 Workspaces are far more than a feature for large editorial teams. Even a single editor benefits from being able to prepare extensive changes independently of the live system first.

With multiple editors, workspaces enable structured review and approval processes, supporting, for example, the four-eyes principle.

AI-assisted content maintenance adds a further use case. Here, workspaces can serve as a safety layer between automated content editing and the public website.

The AI is allowed to work – but the human decides what actually gets published.