Workspaces

Document360 workspaces allow you to create and manage multiple distinct knowledge bases within a single project. This flexibility is especially valuable for organizations with diverse audiences or documentation needs, enabling you to organize content that’s tailored to specific users or product areas. Workspaces keep your documentation organized, accessible, and relevant, no matter the complexity of your knowledge base.

Defining workspaces and their role

When you purchase a Document360 plan, you’re provided with a single project that serves as your knowledge base repository. A project can contain all of your documentation, making it easy to manage and maintain content in one place. Think of it as the central hub for your knowledge base content, whether you have a single product or multiple offerings.

Within your Document360 project, you can create one or more workspaces to better organize your documentation based on audience, product lines, or other criteria.

A workspace is essentially a specialized area within your project that can house content for a particular group or use case. For example:

• If you’re managing documentation for a single SaaS product, one workspace may suffice.

• If you have multiple products or need separate documentation sets for external customers, internal users, and support teams, multiple workspaces can be more efficient.

The number of workspaces you can create depends on your Document360 plan.

Getting started with Workspaces

When you create a new project in Document360, a default workspace titled v1 is automatically created. You can start building your knowledge base in this workspace immediately or create additional workspaces as your documentation needs evolve.

Using multiple workspaces allows you to keep your documentation streamlined, targeted, and well-organized. This way, every user—from internal teams to end customers—can access relevant information quickly and efficiently.

Adding a new workspace

To add a new workspace,

1. Navigate to Settings () in the left navigation bar in the Knowledge base portal.

2. In the left navigation pane, navigate to Knowledge base portal > Localization & Workspaces.

3. Under the Localization & Workspaces tab click the Add workspace button.

4. In the Add new workspace dialog, enter the required details.

   1. Select the Workspace type - Knowledge base docs site or API documentation workspace.

   2. In the Name field, enter your desired name for your new workspace in your preferred language.

      NOTE

      The Name field has a character limit of 30 characters. You can only use alphanumeric characters and hyphens.

   3. The Slug URL field will be auto-populated based on the workspace name you provided in the Name field. You can further customize the URL of your workspace based on your requirements.

5. Next, select the Workspace status for your new workspace.

   1. Main workspace: The Main workspace is the default workspace users will see when they visit your knowledge base site.

      NOTE

      The Main workspace should be public and cannot be deprecated.

   2. beta: Select beta to indicate that the workspace is in a creation/testing phase and not yet ready to go live.

   3. public: Select public for workspaces that should be visible to users.

   4. deprecated: Select deprecated to indicate the workspace is old and contains out-of-date information.

Base workspace

While creating a new workspace, you can choose to either create a new workspace or copy an existing workspace from the same project.

Create a new workspace

If you select Create a new workspace, you will create an empty workspace with no content.

Copy existing workspace

If you select Copy existing workspace, you can copy the contents of an existing workspace to your new workspace.

1. Select the workspace you wish to copy from the list of existing workspaces.

2. Click Choose categories (optional) to select specific categories from the existing categories. Only the contents of the selected categories will be copied to the new workspace.

3. Select either New or Existing for Internal links.

   1. If you select New, the article’s link will point to the article version created in the new workspace.

   2. If you select Existing, the article’s link will point to the original article in the existing workspace.

Languages

The default language of your project will be assigned as the default language of your new workspace as well. To add more languages, click the New language dropdown. From the dropdown, search for the desired languages and select the checkbox next to the language name.

For more settings related to a language, click the More options () icon next to the language name.

• Set as default: Select this option to set the corresponding language as the default language for your knowledge base site.

• Edit display name: Use this option to update the display name for your workspace. The updated name will be shown on the knowledge base site when the corresponding language is selected. You can set a custom display name for your workspace in each of the available languages.  

• Right to left: Enable this toggle for languages that follow a right-to-left script (Arabic, Hebrew). By enabling this toggle, the article’s content will start from the right and continue to the left in the knowledge base portal as well as the knowledge base site.

• Hide: Select this option to hide the language from the knowledge base. Hidden languages are indicated by strikethrough in the Knowledge base portal for reference.

• Remove: Select this option to remove the language from your knowledge base.

Once you complete customizing the details of your new workspace, click the Add button at the bottom right to finish creating the new workspace.

Purchasing workspaces from Localization & Workspaces

1. Navigate to Settings () in the left navigation bar in the Knowledge base portal.

2. In the left navigation pane, navigate to Knowledge base portal > Localization & Workspaces.

3. Under the Localization & Workspaces tab click buy more on the right side of the screen.

NOTE

The buy more link is available only for users assigned the Owner role in projects.

3. Add or remove workspaces in the Purchase add-on panel. The corresponding cost will be displayed as Amount due.

4. Click Confirm Payment to proceed with the payment. Once the payment is processed, a payment success message will display, and the additional workspaces will be added to your project successfully.

5. Click Download invoice to download the invoice for the payment made.

NOTE

You can also purchase workspaces from the Billing section in Document360 settings. To learn more, read the article on Purchasing add-ons.

Managing workspace label and switching behavior in the Knowledge base site

Document360 allows you to customize the term Workspace across the Knowledge base portal and control switching behavior when switching between workspaces (versions) on the Knowledge base site.

NOTE

This feature is available only for KB Site 2.0 projects.

Customizing the Workspace label

You can rename Workspace to align with your internal terminology, such as "Version", "Edition", or "Release".

To update the workspace label:  

1. Navigate to Settings () > Knowledge base portal> General in the Knowledge base portal.

2. In the Project settings page, locate the Customize workspace label field.

3. Enter your desired term (for example, “Version”) with a maximum of 30 characters and no special characters.

   NOTE

   • This change updates all instances of the term Workspace across the portal UI.

   • The default label is Workspace.

   • You can customize the Workspace label for Knowledge base site from Localization variables page.

   Configuring workspace switching behavior

   When a user switches between workspaces in the Knowledge base site, you can control how the redirection works:

4. Below the Customize workspace label field, you can select any one of the following options:

   1. Redirect to root article (default)
      Users are redirected to the root article of the selected workspace.

   2. Redirect to same article

      • If the same article exists in the target workspace, users are redirected to it.

      • If not, they’ll be redirected to the root article instead.

      • This setting is particularly useful when you maintain different versions, localized content, or audience-specific documentation, and want readers to switch between workspaces without losing context.

   Example scenario:

   You have two workspaces: Workspace A and Workspace B

   1. Workspace A contains articles: A1, A2, A3

   2. Workspace B contains articles: A1, A2, A4

      Assume Workspace B is your main workspace:

      Scenario	Configuration	Outcome
      You switch workspaces	Redirect to root article	Always redirects to the root article of the selected workspace
      You are on article A2 in Workspace B and switch to Workspace A	Redirect to same article	Redirects to article A2 in Workspace A
      You are on article A4 in Workspace B and switch to Workspace A	Redirect to same article	Redirects to the root article of Workspace A (A4 doesn't exist there)

5. Click Save to apply your selected behavior.

Troubleshooting

Encountering 404 Page not found error when navigating to a secondary workspace

Error: 404 Page not found error

A 404 error can occur for various reasons, including missing or restricted content. If you're experiencing this issue while navigating to a workspace or an article, it may be due to workspace visibility settings or the absence of published articles.

NOTE

For other potential causes of 404 errors, refer to the 404 Page article.

Steps to resolve:

This error may occur due to one of the following reasons:

1. Check if the workspace is set to Public:

   1. Navigate to Settings () in the left navigation bar in the Knowledge base portal.

   2. In the left navigation pane, navigate to Knowledge base portal > Localization & Workspaces.

   3. Under the Localization & Workspaces tab locate the respective workspace and click the Edit () icon.

   4. In the Choose workspace status section, select the Public checkbox.

   5. Click Update.

      

2. No articles are published in the workspace.

3. All articles in the workspace are hidden.

   Ensure at least one article is published and visible on the Knowledge base site.