Workspaces & languages

Workspaces and languages give you the flexibility to serve the right content to the right audience, all within a single Document360 project.

When you create a Document360 project, a default workspace named v1 is automatically created. This single workspace is enough if you're managing documentation for one product or audience. But as your documentation grows across product versions, user roles, or regions, you can create additional workspaces to keep content organized and targeted.

A workspace is a self-contained documentation area within your project. Each workspace has its own categories, articles, and language settings, and appears as a distinct version on your knowledge base site. For example:

• If you manage documentation for multiple products, create a separate workspace for each product.
• If your audience includes both end users and administrators, separate workspaces keep each group's content focused and relevant.
• If you release versioned software, workspaces let you maintain v1, v2, and v3 documentation side by side.

Languages add another dimension. Each workspace can support multiple languages, so readers can access your content in their preferred language while your team manages everything from one place. When you add a language to a workspace, all existing categories and articles become available in that language, ready for translation.

The number of workspaces you can create depends on your Document360 plan. You can also purchase additional workspaces as an add-on.

Getting started

Best practices

• Customize the workspace label early. Renaming "Workspace" to "Version" or "Release" before your team starts working prevents confusion later. This change applies across the entire portal UI.
• Use "Redirect to same article" for versioned documentation. This keeps readers in context when switching between workspace versions instead of dropping them at the home article every time.
• Use a single multilingual workspace rather than creating separate workspaces per language. Document360 recommends this approach for simpler content management.
• Set workspace status to Beta while building. This keeps new workspaces hidden from readers until the content is ready to publish.