Most Notion users have one view on each database. Usually a table — because that is what Notion creates by default. They use it to add items, check properties, and scan the list. It works. It is also leaving most of the value of the database unused.
Database views are not cosmetic. They are different ways of interacting with the same data that make different questions easy to answer. A table makes it easy to compare many properties across many items. A board makes it easy to move items through a workflow. A calendar makes it easy to see what is happening when. A gallery makes it easy to scan items visually. A timeline makes it easy to see sequence and overlap. A list makes it easy to read through items quickly without visual noise.
The data is the same in every view. The usefulness changes dramatically depending on which view you are using for which purpose. This guide covers all six views, what each one is actually good for, and how to combine them so your databases work for you across every workflow they support.
You need a Notion workspace with at least one database to follow along. Create your free account here — the free plan includes all six view types.
Why Views Are the Most Underused Feature in Notion
The reason most users stick to table view is that adding a new view feels optional. The table already works. There is no obvious prompt to add another view unless you already know what it would give you. And because Notion does not restrict how many views you can add, there is no pricing incentive to explore them.
The result: databases that answer one question well when they could answer six different questions equally well, each through a different view. A task database with only a table view makes it hard to see workload by assignee, impossible to see what is due this week on a calendar, and tedious to understand what stage each task is in without reading the Status column for every row. Adding a Board view, a Calendar view, and a filtered Today view to the same database transforms it from a list into a system.
What a View Actually Is
A view is a saved configuration of how a database is displayed. Each view stores its own: display type (table, board, calendar, etc.), filters (which items are shown), sorts (what order items appear in), grouping (how items are organised into sections), visible properties (which columns or card details are shown), and property widths and ordering for table views.
Changing a view’s filter does not change any other view’s filter. Adding an item in one view adds it to all views — the item exists in the database, and every view shows it according to its own filter. This is the key insight: views are independent presentations of shared data. They do not interfere with each other, and any change to actual data (editing a property, changing a status) is immediately reflected in every view that shows that item.
Table View: The Spreadsheet That Is More Than a Spreadsheet
Table view displays every item as a row and every property as a column. It is the densest view — the one where you can see the most information about the most items simultaneously. That density makes it the right view for data-heavy work: adding and editing properties, comparing values across items, importing or auditing data.
Where table view is underused: property management. Drag column headers to reorder them. Click a header to sort by that column. Right-click a header to hide it in this view without removing it from the database. These controls make table view much more flexible than it appears — you can create a “data entry” configuration with all properties visible and a “review” configuration with only the properties relevant to a specific audience, both saved as separate views on the same table.
The Calculate row at the bottom of each column is often missed. Click “Calculate” under any numeric column to show Sum, Average, Min, or Max across all visible items. For a budget database, Sum on the Amount column shows total spend without any formula. For a task database, Count on the Title column shows how many tasks are in the current filtered view. For a deals database, Sum on Expected Revenue shows weighted pipeline value. These calculations update instantly as filters change.
Best for: initial data entry and auditing, financial databases, inventory, client lists, and any workflow where seeing many properties across many items simultaneously is the priority.
Board View: Your Kanban Without the Complexity
Board view groups items into vertical columns based on a Select or Multi-Select property — typically Status, Phase, or Owner. Each item appears as a card. Drag a card from one column to another and the underlying property updates automatically across every view that shows that item.
The group-by property is what makes or breaks a board view. Group by Status and you have a workflow pipeline. Group by Assignee and you have a team workload view. Group by Priority and you have a urgency matrix. Group by Phase and you have a project stage tracker. Same database, same items, completely different operational picture depending on which property you group by. You can save each grouping as a separate named view.
Card configuration matters almost as much as grouping. Click “Properties” in the board view to choose which properties show on each card. The right balance: two to four properties visible on the card, enough to read the context without crowding the card. For a task board: Assignee and Due Date. For a content pipeline: Publish Date and Platform. For a deals board: Value and Close Date. Everything else stays accessible by opening the full card.
Best for: project task management, sales pipelines, content production pipelines, hiring funnels, and any workflow with defined sequential stages.
Calendar View: Scheduling Without a Calendar App
Calendar view places each item on a calendar based on a Date property. Switch between month and week display. Click any date to create a new item with that date pre-filled. Drag an item to a different date to reschedule it — which updates the underlying date property instantly across all views.
Calendar view is most useful when combined with filters. A content calendar database might have three calendar views: All Scheduled (no filter, showing everything), Published (filtered to Status = Published, showing the posting history), and This Week (filtered to Date = this week, for daily workflow). Each view tells a different story about the same content pipeline.
One underused setting: the date property the calendar uses. By default it uses the first date property in the database. Change it to use a different date property — for a project database, you might want one calendar view based on Start Date and another based on Deadline, giving you both a production schedule and a deadline calendar from the same database.
Best for: content calendars, event planning, leave and absence tracking, project milestone scheduling, and any database where the primary organising dimension is time.
Gallery View: When Visual Matters More Than Data
Gallery view displays items as cards with a large visual cover — a page cover image, a specific file/media property, or an image URL stored in a URL property. Text properties appear below the image on each card. The result is a visual grid rather than a data table.
The cover source setting is what makes gallery view powerful or pointless. If your database items do not have cover images set, the gallery view shows a blank grey rectangle above each card — aesthetically ugly and functionally useless. Set page covers on database items (click the top of any item page and add a cover image) or use a Files and Media property with images for each item. Once covers are set, the gallery view becomes genuinely powerful for visual scanning.
Card size is adjustable: small (dense grid), medium (balanced), and large (large images with more visible text). For portfolio databases and template galleries, large cards work best. For product catalogs and recipe databases, medium is usually right.
Best for: portfolio databases, template galleries, product catalogs, recipe collections, inspiration boards, and any database where visual identification of items matters more than reading their properties.
Timeline View: The Gantt Chart You Did Not Have to Build
Timeline view requires a Date Range on each item — a Start Date and an End Date. Items appear as horizontal bars spanning their duration across a horizontal time axis. Zoom between day, week, month, quarter, and year scales. Drag bars to reschedule. Drag bar edges to extend or shorten duration. Group by any property to see timelines for different phases, teams, or categories in separate rows.
The most powerful feature of timeline view is overlap visibility. When two items occupy the same time period, their bars overlap on the timeline. For a project schedule, this shows task parallelism — which tasks are running simultaneously and where resource conflicts might occur. For a content calendar, it shows when multiple pieces are in production at the same time. For a team schedule, it shows when multiple projects compete for the same people.
Timeline view works best as a planning tool rather than an execution tool. Use it to lay out a schedule, identify conflicts, and agree on sequencing. Use board or table views for daily task management. The timeline tells you whether the plan makes sense; the board tells you whether the plan is being executed.
Best for: project schedules, product roadmaps, campaign timelines, sprint planning, and any workflow where the sequence and duration of activities matter.
List View: The View Most People Forget Exists
List view is the most minimal display: items appear as a simple vertical list, with the title prominent and a small number of visible properties below it. No visual weight, no cards, no columns. Just a fast-loading, easily scannable list.
List view is best when the title alone is enough to identify each item and the properties are supplementary. A reading list where the book title is the primary information. A link database where the URL and source are supporting details. A quick-reference database where you just need to scan names and grab the one you want. List view is also the fastest loading view on both desktop and mobile — useful for databases with large numbers of items or for mobile-first workflows.
Best for: reading lists, resource libraries, link databases, navigation menus built from databases, and any use case where titles are self-explanatory and visual density is more important than visual richness.
How to Layer Views for Maximum Usefulness
The most useful databases have four to six views, each answering a different question. Here is what that looks like for a task database used by a small team:
A Today view (table, filtered to Due Date = today and Status not Done) answers: what needs doing right now. A Board view (grouped by Status) answers: where is each task in the workflow. A By Assignee view (board grouped by Person) answers: what is each team member working on. A Calendar view (by Due Date) answers: when is everything due this week and next. An All Tasks view (table, no filter) answers: what is the complete picture of everything in the system. And a Blocked view (table, filtered to Status = Blocked) answers: what has stopped moving and needs attention.
Six views. Six different answers from the same data. None of them duplicates the others. Each one makes a specific workflow task dramatically easier than it would be with the default single table.
View-Specific Settings Worth Knowing
Lock a view to prevent accidental filter or sort changes. Right-click any view tab and select “Lock database.” A locked view can still be read and items can still be added, but filters and sorts cannot be changed without unlocking. Useful for shared team databases where the main view should always show the same thing regardless of who is using it.
Set a default filter that cannot be removed — available through the filter settings as a “filter that always applies.” This is different from a regular filter, which users can remove manually. A permanent filter ensures that private or archived items never appear in a shared view, even if a user accidentally removes the standard filter.
Wrap cells in table view by clicking the row height control at the top right of the table. Tall rows show more text per cell — useful for databases where description or notes properties contain longer text that you want to read without opening each item.
The View Combination That Works for Most Workflows
For most databases, this four-view combination covers the majority of use cases: a Board view for workflow management (moving items through stages), a Calendar view for time-based planning (seeing what is when), a filtered Today or This Week table view for daily focus (what needs attention right now), and an All Items table view for complete visibility and bulk editing (the master list). Add a Gallery view if the database has visual content. Add a Timeline view if the database has date ranges. The four core views serve everything else.
All of the professional templates at createdigitaltools.com use this multi-view architecture — every database is pre-configured with the right views for its specific workflow. The Project Management with AI template in particular demonstrates the full range of view types across its databases, making it a useful reference for understanding how views should be applied in a professional system. Start with a free Notion account here to explore.
Disclosure: This post contains affiliate links. If you sign up for Notion through the links in this post, we may earn a small commission at no extra cost to you. All opinions are our own.
0 Comments