Core concepts

Everything in Workover is built on four things: workspaces, projects, documents and tabs. The one decision worth making deliberately is how you split your content into projects, because a project is what decides who can see what.

Workspace

A workspace is your organization. It owns the subscription, the member list, the billing details and the workspace-level style guide.

Most companies need exactly one. Create a second only if you genuinely run two separate organizations, for example an agency keeping two clients apart. Each workspace has its own subscription and its own projects, so two workspaces means two subscriptions.

You can belong to several workspaces with one login and switch between them without signing out. See Workspaces.

Project

A project is normally one website. It holds the connection to that site, its address and the credentials Workover uses to reach it, and all the content destined for it. Workover connects to WordPress, Webflow and Mintlify sites.

A project does not have to be connected to a site. When you create a project, choose the Collection type for documents that will never be published, such as internal documentation.

A project is also the unit of access. Joining a workspace grants no project: someone sees a project only once they are added to it. So if you have content not everyone should see, a project is the line to draw it on.

Document

A document is one piece of content: an article, a landing page, a release note or a page of internal notes.

In a WordPress project, a document is either linked to a post on your site or not. Linked means Workover knows which post the document corresponds to, and can push changes to it and pull changes from it. Unlinked means it lives only in Workover, which is a normal, permanent state for plenty of documents.

A document becomes linked in one of two ways:

• you publish it for the first time;
• it was imported from your site, which happens to your existing posts when you connect it.

One document maps to at most one WordPress post.

Tab

A document can be split into tabs. Tabs are useful when several things belong together but should not be one long page, such as a piece of copy, its brief and its research notes.

The rule that matters: one tab is the tab that syncs to your site. The others stay in Workover, so your working notes can sit beside the copy without ever reaching your site. Document tabs covers this in full.

How they nest

Workspace  (your organization, the subscription, the member list)
└── Project  (one website or collection, one connection, one access boundary)
    └── Document  (one piece of content, optionally linked to a post)
        └── Tab  (a section within it; one syncs, the rest don't)

A note on people

Two kinds of access are worth separating early:

• Members belong to the workspace, occupy a paid seat, and can be added to projects. Someone from outside your workspace whom you add to a project becomes a member and takes a seat too.
• Guests are given a specific document, see nothing else, and do not take a seat.

That distinction answers most “how do I let a freelancer see this one article” questions. For the detail, see Roles and permissions, Members and seats and Guests and external collaborators.