What is a Base?
Bases are the primary organizational unit in NocoDB. Think of a base as a complete database project that contains:- Tables - Your data organized in rows and columns
- Data Sources - Connections to external databases (PostgreSQL, MySQL, etc.)
- Views - Different ways to visualize and interact with your data
- Relationships - Links between tables
- Automations - Webhooks and workflows
Workspace Organization
Bases live within workspaces and help you organize related projects together
Multi-Source Support
Connect multiple external databases to a single base
Collaboration
Share bases with team members and control access permissions
Data Isolation
Each base maintains separate data, users, and configurations
Creating a Base
Configure base settings
- Title: Give your base a descriptive name
- Description: Add optional details about the base purpose
- Icon & Color: Customize the visual appearance
Add a data source
Choose to:
- Start with a blank base (uses NocoDB’s internal database)
- Connect to an existing external database
- Import data from a spreadsheet or API
Base Properties
Base Metadata
Each base has the following properties:| Property | Description | Source Reference |
|---|---|---|
id | Unique identifier for the base | Base.ts:34 |
title | Display name of the base | Base.ts:36 |
description | Optional description text | Base.ts:39 |
prefix | URL-safe identifier | Base.ts:37 |
status | Current status (active/archived) | Base.ts:38 |
color | UI color customization | Base.ts:41 |
meta | Additional metadata (icon, settings) | Base.ts:40 |
order | Display order in workspace | Base.ts:43 |
fk_workspace_id | Parent workspace ID | Base.ts:35 |
Data Sources
Bases can connect to multiple data sources:- Internal Database: NocoDB’s built-in SQLite/PostgreSQL database
- External Databases: PostgreSQL, MySQL, SQL Server, SQLite
- Cloud Databases: AWS RDS, Google Cloud SQL, Azure SQL
Base Sharing & Collaboration
Shared Bases
You can share a base publicly with view-only or edit access:- UUID: Each shared base gets a unique identifier
- Password Protection: Optional password for shared bases
- Access Roles: Control what shared users can see and do
Base Users
Manage who has access to your base:- Owner: Full control over the base
- Editor: Can modify data and structure
- Commenter: Can add comments but not edit
- Viewer: Read-only access
BaseUser.ts:609-620 for user management.
Advanced Features
Managed Apps
Bases can be configured as managed applications:managed_app_master: Indicates if the base is a templatemanaged_app_id: Links to the managed app definitionmanaged_app_version_id: Tracks the current versionauto_update: Enables automatic version updates
Base.ts:58-65 for managed app properties.
Sandbox Mode
Create isolated testing environments:is_sandbox_master: Base can spawn sandbox copiesis_sandbox: Indicates a sandbox instance
- Testing changes before production
- Training environments
- Development workflows
Base Operations
Listing Bases
Getting Base Information
Updating a Base
Deleting a Base
Best Practices
Organize by purpose
Organize by purpose
Create separate bases for different projects or departments rather than combining everything into one large base.
Use descriptive names
Use descriptive names
Give bases clear, descriptive titles that indicate their purpose at a glance.
Set up permissions early
Set up permissions early
Configure base-level permissions before inviting team members to prevent accidental data exposure.
Regular backups
Regular backups
For critical data, set up regular exports or database backups at the source level.
Version control for structure
Version control for structure
Document schema changes and use managed apps for versioned deployments.
Related Resources
Tables
Learn how to create and manage tables within your base
Data Sources
Connect external databases to your base
Workspaces
Understand how bases fit into the workspace hierarchy
Sharing
Share bases with team members and external users