---
title: "Project, workspaces and languages"
slug: "project-workspaces-and-languages"
description: "Manage project visibility with control over workspaces and languages in Private and Mixed access projects. Customize access for your knowledge base."
updated: 2026-07-10T04:07:50Z
published: 2026-07-10T04:07:50Z
canonical: "docs.document360.com/project-workspaces-and-languages"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Project, workspaces and languages

The **Project, workspaces, and languages** section on the Reader access page lets you view your project structure — including the number of workspaces and languages — and control their individual visibility. This section is available only for **Private** and **Mixed** access projects.

---

## How visibility works per access mode

- **Public projects:** The entire knowledge base is available to everyone. This section is not applicable.
- **Private projects:** All workspaces and languages are private. Readers must log in to access any content.
- **Mixed projects:** You can mark specific workspaces or languages as **Public** or **Private** independently, allowing granular control over who can access which parts of your knowledge base.

![Project, workspaces, and languages section on the Reader access page showing workspace and language visibility settings.](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/project%20workspace%20and%20languages(1).png)

---

## How to access this section

1. Navigate to **Settings** () > **Users and security** in the left navigation bar in the knowledge base portal.
2. In the left navigation pane, navigate to **Reader access**.
3. Scroll to the **Project, workspaces, and languages** section.

---

## Mixed access: Controlling workspace and language visibility

In a Mixed project, each workspace and language can be independently set to Public or Private. Use this to expose some content publicly while keeping other sections login-restricted.

For example, you might keep a main English workspace Public for all readers, while marking a German workspace as Private for internal users only.