What is a View?
A view is a saved configuration that determines how table data is displayed and accessed. Views allow you to:- Customize which columns are visible
- Apply filters and sorting
- Group and organize data differently
- Share specific data subsets with others
- Create forms for data collection
Multiple Layouts
Display data as Grid, Gallery, Kanban, Calendar, and more
Independent Configs
Each view has its own filters, sorts, and visibility settings
Shareable
Generate public links to share views externally
Collaborative
Team members see the same organized data
View Types
NocoDB supports 8 different view types:Grid View
The classic spreadsheet-style view:- Best for: Data entry, bulk editing, detailed analysis
- Features: Inline editing, column resizing, row selection
- Use cases: Managing customer lists, inventory tracking
Gallery View
Card-based visual layout:- Best for: Image-heavy data, portfolios, catalogs
- Features: Cover images, customizable card content
- Use cases: Product catalogs, team directories, project showcases
Form View
Data collection interface:- Best for: External submissions, surveys, intake forms
- Features: Custom fields, conditional logic, branding
- Use cases: Contact forms, registration, feedback collection
Kanban View
Drag-and-drop board layout:- Best for: Workflow management, status tracking
- Features: Column grouping, drag-to-update, progress visualization
- Use cases: Project management, sales pipelines, task boards
Calendar View
Time-based visualization:- Best for: Event scheduling, date tracking
- Features: Month/week/day views, date ranges
- Use cases: Event calendars, deadlines, scheduling
Map View
Geospatial data display:- Best for: Location-based data
- Features: Interactive maps, marker clustering
- Use cases: Store locations, delivery routes, property listings
List View
List view is currently in development. The view type is defined in the type system but full implementation is pending.
- Best for: Parent-child relationships, nested data
- Features: Expandable levels, linked records
- Use cases: Organization charts, category trees, threaded discussions
Timeline View
Timeline view is currently in development. The view type is defined in the type system but full implementation is pending.
- Best for: Project timelines, scheduling
- Features: Start/end dates, duration display, Gantt-style layout
- Use cases: Project planning, resource allocation, scheduling
globals.ts:36-45
Creating a View
Configure view settings
- Title: Name your view
- Description: Add context (optional)
- Type-specific settings: Configure view-specific options
View Properties
| Property | Description | Type |
|---|---|---|
id | Unique identifier | string |
title | Display name | string |
description | Optional description | string |
type | View type (Grid, Gallery, etc.) | ViewTypes |
fk_model_id | Parent table ID | string |
show | Visibility status | boolean |
order | Display order | number |
uuid | Shared view identifier | string |
password | Shared view password | string |
lock_type | Collaborative/locked | string |
show_system_fields | Include system columns | boolean |
View.ts:93-135
View Columns
Each view maintains its own column configuration:- show: Whether the column is visible
- order: Column display order
- width: Column width (Grid view)
View.ts:1100-1147
Filters & Sorts
View Filters
Filters determine which records appear in the view:View Sorting
Control record order:Sharing Views
Share views publicly with external users:Enable Sharing
Password Protection
Verify Access
Disable Sharing
View.ts:1564-1679
View-Specific Features
Gallery View Options
Kanban View Options
Calendar View Options
Form View Options
Managing Views
Listing Views
Getting View Details
Updating a View
View.ts:1681-1792
Duplicating a View
Create a copy with all settings:View.ts:295-799
Deleting a View
View Permissions
Lock Types
Control edit access:- collaborative: Anyone with access can edit
- locked: Only owner can modify view settings
- personal: Private view visible only to creator
Row Coloring
Conditional formatting based on rules:Advanced Features
Column Insertion
Add columns to all views automatically:View.ts:829-966
View Caching
Optimize performance with query caching:Best Practices
Create views for different audiences
Create views for different audiences
Make separate views for different user types (e.g., customer-facing, internal team, executive summary).
Use descriptive view names
Use descriptive view names
Name views based on their purpose: “Active Projects”, “Q4 Sales”, “Pending Approvals”.
Minimize visible columns
Minimize visible columns
Show only relevant columns in each view to reduce clutter and improve performance.
Combine filters strategically
Combine filters strategically
Use view filters instead of manual filtering to save time and ensure consistency.
Share with care
Share with care
Choose the right view type
Choose the right view type
Match view type to use case: Kanban for workflows, Calendar for events, Gallery for visual content.
Related Resources
Filters & Sorting
Learn how to filter and sort data in views
Tables
Understand the relationship between tables and views
Fields
Configure which fields appear in each view
Sharing
Share views with team members and external users