Private Base

Learn how to configure and manage access to Private Bases in NocoDB.

The Private Base feature is available only on the Business plan and above

A Private Base in NocoDB allows base owners to fully control access at the base level, independently of workspace-level roles. This feature is ideal for projects that require confidentiality, restricted visibility, or selective collaboration within a workspace.

How Private Base Works

When a base is marked as private:

  • Workspace role inheritance is disabled — users with roles like Owner, Editor, or Viewer at the workspace level will not automatically gain access.
  • By default, only the base creator (Owner) can access the base.
  • Access must be explicitly granted to other members by assigning a base-specific role (Owner, Creator, Editor, Commenter, or Viewer).
Members without explicit access will not see the base listed in their workspace

Creating a Private Base

  1. Click + New BaseFrom Scratch on the workspace Bases tab.
  2. Enter a name for the base.
  3. Select Private as the Base Type.
  4. Click Create Base.

Create base Create base Create base

Only the base creator will have access by default. Other workspace members, including Workspace Owners, will not see the base unless explicitly added.
Private bases cannot be shared publicly. All view-sharing (except Form views) is restricted.

Converting an Existing Base to Private

  1. Open the base and go to Base SettingsGeneral in the sidebar.
  2. Under Base Type, select Private.

Convert to Private Base

Explicitly configured base-level roles will be retained. Inherited workspace access for other users will be removed.
If the base or view is currently shared publicly, sharing will be disabled when switching to private.

Disabling Private Access

  1. Open the base and go to Base SettingsGeneral in the sidebar.
  2. Under Base Type, select Default.
Workspace-level role inheritance will be re-enabled. Members with workspace roles will regain corresponding access. Explicit base roles remain unchanged.

Managing Access in a Private Base

Managing user access in a private base follows the same process as any other base. You can invite workspace members and assign them roles explicitly at the base level. Role changes at the workspace level will not affect access to a private base unless the base type itself is set back to default access.

For detailed steps, refer to the Base Collaboration Guide.