TL;DR — The fastest way to learn how to use Notion is to stop treating it like a document editor and grasp one idea: everything is a block, and any collection of pages can be a database. This tutorial walks you from your first page to your first working system — creating pages with the "/" slash command, building a Notion database (where each row is a page and each column is a property), switching that one database between table, board, and calendar views, using filters and sorts instead of making a dozen separate databases, and connecting databases with relations (the "aha" moment). We finish with a start-to-finish build of a simple task tracker you can copy, and the beginner mistakes that trip almost everyone up — over-building, too many databases, and burying pages five levels deep. Follow it in order and you'll understand Notion better in twenty minutes of doing than an hour of reading.

The one idea that makes Notion click

Before any steps, internalize this, because it's what separates people who "get" Notion from people who bounce off it: everything in Notion is a block. A paragraph is a block. A heading is a block. An image, a to-do, a table — each is a block you can drag, nest, and rearrange. A page is just a collection of blocks. And Notion's real power is that any collection of pages can become a database — a set of pages that share properties, which you can filter, sort, and view in different ways.

That's the whole mental model. Most beginners use Notion like a prettier Google Docs — pages and text — and never touch the part that makes it worth learning. If you take one thing from this tutorial, take this: the moment you turn your notes into a database, Notion stops being a notebook and becomes a system. Everything below builds toward that.

Step 1: Create your first page and learn the "/" command

Open Notion and create a page (the + New page button in the sidebar). Type a title, hit enter, and start writing. Now learn the single most important shortcut in Notion: the "/" slash command. Type / anywhere and a menu appears with every block type you can insert — heading, to-do list, bullet, toggle, callout, divider, image, table, and more. Instead of hunting through toolbars, you type /todo for a checkbox, /h1 for a heading, /callout for a highlighted box.

Spend two minutes here just inserting blocks with / and dragging them around by the handle that appears on hover. Getting fluent with the slash command is 80% of feeling fast in Notion. Once / is muscle memory, the tool gets out of your way.

Step 2: Create your first database — where the power lives

This is the step that matters. Type /database and choose Table (inline or full-page). What you've made isn't a spreadsheet, even though it looks like one — it's a database, and the distinction is the key to everything.

Here's the rule to memorize: each row is a page, and each column is a property. Click into any row and it opens as a full page — with its own body where you can write freely, add blocks, and store detail. So a database isn't a flat grid of cells; it's a collection of rich pages with a shared structure. A "Tasks" database where each task is a page you can open and add notes, subtasks, and files to. A "Clients" database where each client opens into a full profile.

Add a few columns using the + at the end of the header row, and notice the property types: Text, Number, Select (a single tag), Multi-select (multiple tags), Date, Person, Checkbox, URL, and more. Properties are how you make your data filterable and sortable later — a Select property for "Status" (To do / In progress / Done) is what will let you build a board in the next step. Add three or four real rows now so you have something to work with.

Curious how Notion feels in practice?Start free — no card; try AI on the Business trialTry Notion →

Step 3: One database, many views

Here's the feature that changes how you think about organizing information. That single Tasks database can be displayed in multiple ways without duplicating the data. At the top of the database, click + (Add view) and you'll see the view types:

The point: it's one dataset viewed many ways. The project manager looks at the board, the writer checks the calendar, and you review everything in the table — same data, no copying, always in sync. This "one database, many views" idea is the concept most beginners never discover, and it's exactly why people who learn Notion properly stop using five separate apps.

Step 4: Filters and sorts — the antidote to database sprawl

Once you have views, add filters and sorts to each one. A filter shows only the rows matching a condition — "Status is not Done," or "Assignee is me," or "Due date is this week." A sort orders them — by due date, priority, or name. Each view keeps its own filters and sorts, so your "My tasks this week" view and your "Everything, by project" view read the same database but show completely different things.

This solves the single most common beginner trap directly. New users, wanting to separate "work tasks" from "personal tasks" from "someday tasks," create three databases — and now nothing connects and everything's a mess. The right move is one Tasks database with filtered views. One source of truth, sliced by filters. Learn to reach for a filtered view before you reach for a new database, and your workspace stays sane.

Step 5: Relations — connecting databases (the "aha" moment)

When you're comfortable with one database, connect two. A Relation property links rows in one database to rows in another. The classic setup: a Projects database and a Tasks database, with a relation so each task points to its project — and each project shows all its tasks. Add a Rollup property on the project side and you can surface information from the linked tasks (a count of open tasks, the latest due date, a percentage complete).

This is the moment Notion clicks for most people, because it's when your workspace stops being a pile of lists and becomes a connected system: open a project, see its tasks; open a task, jump to its project. You don't need relations on day one — but the first time you build one, you'll understand why Notion is more than a note app.

Step 6: Sharing and collaboration

Notion is built for teams. Use the Share button (top-right of any page) to invite people or generate a link. You can set permissions — full access, edit, comment, or view — per page or per person, and pages inherit access from their parent, so sharing a top-level "Team Wiki" page shares everything inside it. For occasional collaborators, add them as guests to specific pages rather than paid members. Comments (@mention a teammate, or highlight text and comment) keep discussion attached to the work instead of scattered in chat.

Ready to put Notion to the test?Start free — no card; try AI on the Business trialTry Notion →

A complete first build: a task tracker in 5 minutes

Concepts stick when you build something. Here's a start-to-finish task tracker — do it as you read:

  1. Create the database. New page → type /table → choose a full-page table. Name it Tasks.
  2. Set up properties. Keep the default Name column. Add a Select property called Status with options To do, In progress, Done. Add a Date property called Due. Add a Select (or Person) property called Priority with Low / Medium / High.
  3. Add real tasks. Enter five things you actually need to do this week, filling in Status, Due, and Priority for each.
  4. Add a Board view. Click + Add view → Board, and group by Status. Now your tasks are cards in To do / In progress / Done columns — drag one to "In progress" and watch it move.
  5. Add a Calendar view. + Add view → Calendar, using the Due property. Your tasks now appear on the days they're due.
  6. Add a filtered view. Duplicate the table view, name it This week, and add a filter: Due is within the next 7 days and Status is not Done. That's your daily working view.

You now have a single database showing three ways — a board to work from, a calendar to plan by, and a filtered list of what's due — with zero duplicated data. That's Notion working the way it's meant to, and you built it in five minutes. Everything more advanced (relations, rollups, templates, AI) is a variation on what you just did.

The beginner mistakes to avoid

Almost everyone makes at least one of these. Skip them and you'll save yourself weeks of frustration:

A few features that level you up fast

Once the basics feel natural, these four features are the ones that separate a casual user from someone genuinely fast in Notion — worth learning early:

None of these are day-one essentials, but each removes friction the moment you hit it — and knowing they exist stops you from doing manually what Notion will do for you.

Where to go next

You now know the mechanics that matter: blocks and the slash command, databases where each row is a page, multiple views of one dataset, filters and sorts, relations, and sharing. The best next step isn't more reading — it's picking one real workflow (your tasks, your projects, your notes) and building it, then refining as you go. If you'd rather not start from a blank page, grab a ready-made setup from our Notion templates guide and customize it — editing something that already works is the fastest way to learn. To see how AI can now do work inside these databases, see our Notion AI guide; for the full verdict on the tool, read our Notion review, and check the pricing guide to see what your setup will cost.