👁️ Lesson 3.3: Views — Table, Board, Calendar, Gallery, List & Timeline

Here's the payoff for everything you built in this module. Your Reading List is one collection of pages — but Notion can show it as a spreadsheet, a kanban board, a calendar, a gallery of covers, a clean list, or a Gantt-style timeline. Same data, many views. Once this clicks, you'll never think about "organizing" the same way again.

📚 What You'll Learn

By the end of this lesson, you will be able to:

Grasp the key insight — one dataset, many views — and why it changes everything
Choose the right view for the job: Table, Board, Calendar, List, Gallery, Timeline
Create, name, reorder, and switch between views on one database
Understand that each view keeps its own settings — visible properties, card size, and (next lesson) filters and sorts
Recognize a linked database view — a view of an existing database placed on another page

⏱️ Estimated Time: 60 minutes

🎯 Project: Add three views to your Reading List — a Board grouped by Status, a Calendar by your Date property, and a Gallery of covers.

In This Lesson

The Key Insight: One Dataset, Many Views

In Lesson 3.1 we said the "table" you see is just one view of the data. This is the lesson where that idea becomes a superpower. The data — your rows and their properties — lives underneath, invisible. A view is a lens that arranges that same data into a shape: a grid, a board of cards, a calendar, and so on.

Crucially, changing a view never changes the data. Drag a card between board columns and you're editing a property (its Status); switch to the calendar and that same book appears on its date. One collection, seen every way you need it. Your Reading List can be a checklist while you triage, a calendar when you plan, and a gorgeous gallery when you browse — with no copying, no duplication.

graph TD A["🗃️ One Reading List
(the same rows & properties)"] --> B["📊 Table"] A --> C["📋 Board
(by Status)"] A --> D["📅 Calendar
(by Date)"] A --> E["🖼️ Gallery
(covers)"] A --> F["📃 List"] A --> G["📈 Timeline
(date ranges)"]

🧠 Mindset

If you've ever kept the "same" information in three different apps — a task app, a calendar, and a spreadsheet — and hated keeping them in sync, this is the moment Notion pays you back. You maintain one list. The views sync themselves, always, because they're all looking at the same data. That relief is the feeling of Notion clicking.

A Tour of the Six Views

Each view type is best at something. Here's the whole family with a plain-language "use it when…".

View	Looks like	Use it when…	Needs
📊 Table	A spreadsheet grid	You want to see many properties at once and edit fast	—
📋 Board	Kanban columns of cards	Tracking things through stages you drag between	A Select or Status to group by
📅 Calendar	A month/week grid	Anything time-based — due dates, events, plans	A Date property
📃 List	A clean, minimal stack of titles	Distraction-free reading; embedding on a dashboard	—
🖼️ Gallery	A grid of cards, often with images	Visual collections — book covers, recipes, moodboards	Nice with a Files/cover image
📈 Timeline	A Gantt-style horizontal bar chart	Projects with start/end dates and overlap	A Date property (a range is best)

📊 Table

The default and the workhorse. Every property is a column; great for bulk editing and for seeing all the details together.

📋 Board

A kanban board, grouped by a Select or Status property. Each option becomes a column, each row becomes a card, and dragging a card to another column updates that property. This is the classic "To Do → Doing → Done" workflow view.

📅 Calendar

Places each row on a date from a Date property. Perfect for content calendars, deadlines, and events. Click a day to add a new row right there.

📃 List

The most minimal view: just titles (and a few chosen properties) in a clean vertical stack. Ideal for a simple index or for tucking a database onto a dashboard without visual noise.

🖼️ Gallery

Shows rows as cards in a grid, and can use a Files/media property or the page's cover as the card image. Beautiful for anything visual — a bookshelf of covers, a recipe box, a portfolio.

📈 Timeline

A Gantt-style view that draws each row as a horizontal bar across dates — excellent for project plans where things have a start and end and may overlap. Use a Date range (end date on) for the full effect. Some of Timeline's more advanced planning touches (like a side table alongside the bars) are worth exploring once you're comfortable.

Seeing It: Board & Gallery

Descriptions only go so far — here's the same Reading List shown two ways. First, a Board grouped by Status, where each column is a stage and each card is a book:

📋 By Status

To Read The Hobbit · Educated

Reading Dune

Done Atomic Habits · Project Hail Mary

In real Notion these are side-by-side columns of draggable cards. Drag "Dune" from Reading to Done and its Status property updates instantly — the board is just editing the data.

Now the same books as a Gallery of cards, each showing a cover image and a couple of properties:

🖼️ Shelf

🟪 Dune — Sci-fi Reading

🟨 Atomic Habits — Self-help Done

🟥 The Hobbit — Fantasy To Read

Each card is a page you can open. Gallery cards can show a cover image, and you choose which properties appear beneath the title.

💡 Board needs something to group by

A board organizes cards into columns by a property — almost always a Status or Select. If your database has neither, Notion will prompt you to pick or create one. This is exactly why we added a Status property last lesson: so your board would have meaningful columns.

Creating & Managing Views

A database starts with one view, but you can add as many as you like — and they all sit as tabs along the top of the database. Here's the workflow:

Add a view: Click the + beside the view tabs (or the view name → + Add view). Pick a type (Table, Board, Calendar…) and Notion creates it on the same data.
Name it: Give each view a clear name — "By Status", "This Month", "Shelf". Good names make the tabs a menu of ways to look at your data.
Switch views: Click a tab. Nothing about the data changes — only how it's shown.
Reorder / rename / duplicate / delete: Click a view's name for its menu. Deleting a view never deletes rows — it only removes that lens.
Set the default: The leftmost view is what people see first. Drag your most-used view there.

📚 Reading List

📊 All Books 📋 By Status 📅 Calendar 🖼️ Shelf + Add view

Each tab is the same data, arranged a different way.

⚠️ Watch Out — delete the view, not the data

Deleting a view is safe: your rows live in the database, not in any single view. But deleting a row (a page) removes it from every view, because there's only one underlying collection. When in doubt, remember: views are lenses; rows are the real thing.

Per-View Settings & Card Previews

Here's what makes views genuinely powerful: each view has its own settings. Visible properties, sort order, card size, grouping — all stored per view. Your table can show ten columns while your gallery shows just a cover and a title. Change one view and the others are untouched.

Common per-view settings you'll use:

Properties shown: Toggle which properties appear (on cards, or as columns). Each view remembers its own set.
Card preview & size (Board/Gallery): Choose the card image source (a Files property or the page cover) and card size (small / medium / large).
Group by (Board): Choose which Select/Status property forms the columns.
Calendar by / Timeline by: Choose which Date property positions the items.
Sort & Filter: Also per view — a whole topic of its own, which is exactly the next lesson.

✅ Pro Tip — one database, many jobs

Because settings are per view, one Reading List can serve totally different moods: a dense "All Books" table for editing, a calm "Shelf" gallery for browsing, a "By Status" board for triage. You're not building three databases — you're giving one database three faces. That's the whole art of Notion.

💡 A tease for next lesson

Views become truly personal once you add filters, sorts, and grouping — "show only unread," "sort by rating," "group by genre." That's Lesson 3.4. For now, just get comfortable creating and switching views; the filtering magic builds right on top of them.

Linked Database Views

One more idea that unlocks dashboards. So far your views live on the database itself. But you can also drop a view of an existing database onto any other page — that's a linked database view.

Type /linked (or use the "Create linked database" option) and pick an existing database. Notion places a live view of it there. It's the same data — edit a row in the linked view and it changes everywhere — but this particular view can have its own filters, sorts, and visible properties. It's how a "Home" dashboard can show "Today's tasks" from your master Tasks database and "Currently reading" from your Reading List, all in one place, always current.

📖 Definition

Linked database view: A view of an existing (source) database that lives on another page. It reads and writes the same underlying data — it is not a copy. Delete the linked view and the source database is untouched. This is the backbone of every good Notion dashboard.

⚠️ Linked view vs. duplicate

Don't confuse a linked database with a duplicated one. A linked view shows the same live data; a duplicate is a separate copy that drifts out of sync the moment you edit either. For a dashboard, you almost always want a linked view, not a duplicate.

🎯 Project: Three New Views on Your Reading List

Time to feel the "one dataset, many views" magic firsthand. You'll add three views to the Reading List you enriched last lesson — and watch the exact same books rearrange themselves each time.

🏋️ Add a Board, a Calendar, and a Gallery

Objective: Create three well-configured views on one database and confirm that editing in one updates the others.

Instructions (about 20 minutes):

(2 min) Open your Reading List. Note its current Table view — this is view #1.
(5 min) Click + Add view → Board. Set Group by to Status. Name it "By Status". Drag a card between columns and watch its Status change.
(5 min) Add another view → Calendar. Set it to use your Date property (Finished/Started). Name it "Calendar". Click a day to see how you'd add a book on a date.
(5 min) Add a third view → Gallery. In the view settings, set the Card preview to your cover image (or "Page cover"), and choose which properties show under the title. Name it "Shelf".
(2 min) Switch between all four tabs and confirm the same books appear in each — proof that it's one dataset, many views.
(1 min) Reorder the tabs so your favorite view is first (the default).

💡 Hint — if a view looks empty or wrong

Board is empty / one big column?
  → Set "Group by" to your Status property.

Calendar shows nothing?
  → Make sure rows have a Date value, and the
    view is set to use that Date property.

Gallery cards have no image?
  → Set Card preview to "Page cover" or a Files
    property, and give a few rows a cover.

Most "broken view" moments are just a setting that hasn't been pointed at the right property yet.

✅ Project Completion Checklist

You added a Board view grouped by Status
You dragged a card between columns and saw its Status update
You added a Calendar view using your Date property
You added a Gallery view with a card preview image
You named all your views clearly and reordered the tabs
You confirmed the same rows appear in every view

🎯 Quick Quiz

Question 1: You switch your database from a Table view to a Board view. What happens to your data?

Question 2: Which property does a Board view most need in order to make useful columns?

Best Practices for Views

✅ Do's

Name every view clearly. The tabs become a menu — "By Status" beats "Board".
Match the view to the task. Board for triage, Calendar for planning, Gallery for browsing.
Use linked views for dashboards so one database can appear wherever you need it, always in sync.

❌ Don'ts

Don't duplicate a database when you just want a different view — add a view or a linked view instead.
Don't cram every property into every view. Hide what a given view doesn't need.
Don't fear deleting a view — it never deletes your rows.

📓 Learning Journal

Keep a learning journal — the best place is inside your own Notion. After each lesson, take a few minutes to write down:

Key concepts you learned
Techniques that clicked for you
Questions or confusion points to revisit
Ideas you want to try
Your progress and feelings about learning this

✍️ This lesson's prompt: Which view surprised you by being the most useful for your data — and did seeing "the same books" reshape into a board and a calendar change how you think about organizing your life? Jot one place you keep duplicated info today that could become one database with views.

📝 Lesson Summary

🎓 Key Takeaways

The key insight: one dataset, many views. A view is a lens on the same data, and switching views never changes the rows.
Six view types — Table, Board, Calendar, List, Gallery, Timeline — each best at a different job.
Board needs a Select/Status to group by; Calendar and Timeline need a Date property.
Each view keeps its own settings: visible properties, card previews, grouping — and (next) its own filters and sorts.
A linked database view shows an existing database on another page — the same live data, ideal for dashboards.

🎉 What You've Accomplished

You just experienced the single most powerful idea in Notion: your Reading List became a board, a calendar, and a gallery without you copying a thing. That's the moment most people fall in love with Notion — and it's the foundation for every dashboard and workflow you'll ever build. You now understand databases from the data up to the views on top.

❓ Common Questions at This Stage

If I delete a view, do I lose the data in it?

No. Rows live in the database, not in any single view. Deleting a view only removes that lens — the data stays and appears in every other view. (Deleting a row is different: that removes the page from all views, because there's only one underlying collection.)

Why is my Board just one big column, or my Calendar empty?

A Board needs a Select or Status property set as its "Group by," and a Calendar needs rows with a Date value and the view pointed at that Date property. Empty or lumped-together views are almost always a setting that hasn't been aimed at the right property yet.

Do extra views or linked databases cost money?

No — unlimited views and linked database views are available on the Free plan. Paid plans add team collaboration, bigger uploads, and longer history rather than more views. Build as many views as your workflow enjoys.

🔭 Looking Ahead

You can now see your data every way — next you'll control which data shows. Lesson 3.4: Filters, Sorts & Grouping — Seeing Only What Matters is where views get personal: "only unread books," "sorted by rating," "grouped by genre." It builds directly on the views you just created.

✅ Before the Next Lesson

Keep your Board, Calendar, and Gallery views — you'll filter and sort them next
Make sure your Board groups by Status and your Calendar uses a Date
Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

You've now built and reshaped a real database — the heart of Notion — and made it show up as a board, a calendar, and a gallery. That's a genuine skill most Notion users take months to internalize, and you did it in one module. Next we make those views laser-focused. You're building something real. 👁️