# What is Workover?

Workover is a document editor for teams that write content for a website: product documentation, help centers, marketing pages and internal wikis. You write and review in Workover, then publish to your WordPress, Webflow or Mintlify site.

Workover is at an early stage and still growing. If something you need is missing, [tell us](/docs/contacting-support/).

## How Workover is organized

A **workspace** holds your team, your subscription and your **projects**. A project is usually one website: it holds the documents destined for that site and the connection Workover uses to reach it. A project can also be a collection of documents that is never published. Each **document** is one piece of content, and it can be split into **tabs**, only one of which syncs to your site.

Access is granted per project, so joining a workspace does not by itself let someone see any content. [Core concepts](/docs/core-concepts/) explains the model in full.

```
Browser editor ──┐
                 ├──▶  Document  ◀── publish / pull ──▶  Your site
Claude Code ─────┘                                       (WordPress, Webflow
(CLI and MCP:                                              or Mintlify)
 propose; edit or publish
 to WordPress only if granted)
```

## What you can do

### Write and review together

Several people can edit the same document at once, with threaded comments and [version history](/docs/version-history/) you can restore from. See [Real-time editing and presence](/docs/presence-and-real-time-editing/) and [Comments and suggestions](/docs/comments-and-suggestions/).

### Work from an agent

Claude Code and other agents can reach Workover through the [CLI and MCP server](/docs/cli-and-mcp/). By default an agent can search and read your documents and propose changes, which arrive as suggestions for you to accept or reject. It can also create new documents. Editing existing documents directly, or publishing to a connected WordPress site, only works if you grant that permission when you sign the agent in.

### Draft with AI

AI drafting writes a first draft from a brief and follows your [style guides](/docs/style-guides/), set at workspace and project level. It can also read a connected GitHub, GitLab or Bitbucket repository, so a technical page describes how your product actually works. When AI revises a document, its changes arrive as suggestions that you accept or reject one at a time or all at once. See [Drafting with AI](/docs/ai-drafting-overview/).

### Publish and sync

Connect a WordPress site to a project and a finished document becomes a real post or page, with the permalink, categories, excerpt, featured image and SEO fields you set in Workover. When you connect the site, your existing posts come into Workover as documents, and changes made in WordPress can be [pulled back](/docs/pulling-from-wordpress/). See [How WordPress sync works](/docs/how-wordpress-sync-works/).

To stop Workover reaching a WordPress site, revoke the **Workover** application password in your WordPress profile. Posts already on the site stay as they are.

> **Warning:** **Delete project** in Project settings is not a disconnect. It deletes every document in the project.

### Monitor published pages

[Monitor](/docs/monitor-overview/) re-checks your published pages and reports what changed and whether it matters, such as a page that starts returning a 404 or a `noindex` left on after a deploy. You add a site to Monitor separately; connecting or publishing does not enroll it. Monitor is enabled per workspace by arrangement.

## Start here

1. [Core concepts](/docs/core-concepts/): workspaces, projects, documents and tabs, and who can see what.
2. [Quickstart: publish your first document](/docs/quickstart/): connect a WordPress site and publish a post, end to end.
3. [How to connect a WordPress site](/docs/connecting-your-wordpress-site/): connect another site, and fix connection errors.
4. [Inviting your team](/docs/inviting-your-team/): bring colleagues into your workspace and projects.