Sign in with Google

How to Use Notion: A Beginner's Setup That Sticks

Learn the one idea Notion is built on, then build the smallest setup that survives a real week.

beginner10 min read
creative-toolsnotionnote-takingproductivitybeginners
Most people abandon Notion in week two, and not because it is hard. They spend the first evening building a nine-database life-management system with relations and rollups, then never put a single real note into it. It collapses under its own maintenance cost before it holds anything worth keeping. This guide goes the other way: learn the one idea Notion is built on, build the smallest setup that survives a real week, and grow it only when something breaks.
iWhat you need
A free account at notion.com, a browser, and about 30 minutes. On the Free plan an individual gets unlimited pages and blocks; uploads cap at 5 MB per file, page history goes back 7 days, and you can invite up to 10 guests. Notion AI on Free is a limited trial, not a permanent feature — check the current pricing page before planning around it.
Notion is a tree of pages. Every page holds text, and every page can hold other pages. That tree is the entire filing system — no folders, no separate "documents" area hiding somewhere. The second half of the idea trips everyone up: any page can also be a database, meaning a page whose children are rows with structured fields attached.
Hold those two sentences and the interface stops feeling arbitrary. The left sidebar is the tree; the area on the right is one page from it. A database is a page whose child pages have properties, which is why you can always click a row open and write inside it like any other page.
Your sidebar is your structure, so keep it shallow. Three or four top-level pages is plenty; nesting six levels deep on day one guarantees you lose things.

Getting around the tree

  1. 1Hover a sidebar item and click the plus that appears to create a subpage directly under it.
  2. 2Press Cmd+P on Mac or Ctrl+P on Windows to open search and jump to any page by typing a few letters of its name. This becomes your main way to navigate — faster than clicking through the tree.
  3. 3Drag pages in the sidebar to re-parent them. Nothing breaks when you move a page; links to it follow.
  4. 4Favorite the two or three pages you open daily so they pin to the top of the sidebar.
Everything inside a page is a block: a paragraph, a heading, an image, a to-do, a whole database. Type / on an empty line to open the block menu, then keep typing to filter it. That one keystroke replaces most of the toolbar hunting a normal document editor demands.

The ten block types worth knowing on day one

  1. 1Text — the default. Start typing.
  2. 2Heading 1, 2, and 3 — page structure. Type #, ##, or ### then a space.
  3. 3Bulleted list and Numbered list — a dash or 1. then a space.
  4. 4To-do — a checkbox. Type [] then a space.
  5. 5Toggle — collapsible content. Type > followed by a space. Good for detail you rarely need.
  6. 6Callout — a boxed note with an icon, for reminders to yourself.
  7. 7Quote — for other people's words, so you can tell them from your own later.
  8. 8Divider — three dashes. Cheap structure inside a long page.
  9. 9Code — a monospaced block with syntax highlighting and a language picker.
  10. 10Table view, Board view, Calendar view — these create a database inline, which is the next section.
✓The grip handle is the other half of editing
The six-dot handle left of every block drags it anywhere, including side by side to make columns. Click it instead of dragging for Duplicate, Turn into, Move to, and Copy link to block.
This is the feature people misunderstand most, and the misunderstanding is expensive. A table, a board, a calendar, and a gallery are not four things you keep in sync. They are four views of one set of rows. Change a due date on the calendar and the table shows it immediately, because there is only one underlying set of data.

Adding a second view to a database

  1. 1Click the plus next to the existing view name in the top-left of the database.
  2. 2Pick the layout: Table, Board, Calendar, Gallery, List, or Chart.
  3. 3Name it after the question it answers — Today, By project, Someday — not after its layout.
  4. 4Set its filters and sorts. Those belong to that view alone and change nothing elsewhere.
  5. 5Switch views using the tabs along the top. Both are live; neither is a copy.
!One database, many views — not many databases
If you catch yourself making a second Tasks database because you want a different arrangement, add a view instead. You can also drop a linked view of an existing data source onto any page, so the same tasks appear on your daily page without being duplicated.
Properties are the columns on a database: text, number, date, select, multi-select, checkbox, person, and more. Two do most of the work. A Select property gives each row one label from a fixed list, which is what makes grouping possible. A Date property makes filtering by time possible. Add those two and you can build the only two views most people need.

Build Today and Everything by project

  1. 1In your Tasks database, add a Select property called Status with options To do, Doing, Done; a Date property called Due; and a Select property called Project.
  2. 2On the default table view, open Filter and add: Status is not Done, then Due is on or before today. Rename the view Today.
  3. 3Open Sort on that view and sort by Due, ascending, so the most overdue thing sits on top.
  4. 4Add a second Table view called By project. Open Group, group by Project, and add one filter: Status is not Done. That is a per-project backlog that maintains itself.
Anything you write more than twice should be a template. Inside a database, open the New button's dropdown and choose New template — every row created from it starts with your headings in place. On a plain page, a template button block does the same job.
markdown
## Context
Who was there, and what prompted this.

## Notes
Raw notes during the meeting. Messy is fine.

## Decisions
Only what was actually decided.

## My next actions
[] One line each, with an owner and a date.

A meeting-note template worth saving — four headings, no cleverness

Typing @ followed by a page name drops an inline link to that page. This is the habit that beats a folder tree: a meeting note can link to the client, the project, and the person, and each of those pages shows the connection from its own side. A file lives in one folder. A page can be mentioned from everywhere.
Three pages. That is the whole thing. Resist adding a fourth until you have used these for two weeks.

The fifteen-minute setup

  1. 1Create a top-level page called Notes. Leave it almost empty — one heading that says Inbox is enough. Everything you capture goes here first as a subpage.
  2. 2Create a top-level page called Tasks. Type /table on it and choose Table view to create a new database. Add the Status, Due, and Project properties from earlier.
  3. 3Build the Today and By project views on it, then favorite the Tasks page.
  4. 4Create a top-level page called Reading. Type /table again. Give it a Status select with Want to read, Reading, Finished, plus a URL property called Link.
  5. 5Add a Gallery view on Reading and name it Shelf. Covers make a reading list you revisit.
  6. 6Put five real things in. An empty system teaches you nothing about whether it works.
The over-engineering trap is not a discipline problem — building the system feels like progress, which is why it substitutes so easily for the work. Use a rule with a hard trigger: add structure only when the same annoyance has bitten you twice. Not when you can imagine it biting you. Twice, in reality, with dates you could point to.
✓The two-strike rule in practice
If you have lost track of which tasks belong to which client twice, add the Project property. If you have never once wished for it, do not add it, no matter how neat the template you saw looked.
Every page has a Share button in the top-right with two separate things behind it. Invite gives a specific person access at Full, Can edit, Can comment, or Can view level. Publish puts the page on the public web at a Notion URL. Permissions inherit down the tree, so sharing a parent shares everything under it — check what is nested underneath first.
Install the mobile app and treat it as a capture device, not a workspace. Editing a complex database on a phone is miserable; adding a row to your Notes inbox on a bus is what it is good for. The iOS and Android share sheet can send a link straight into a Notion database, which makes your Reading list far more likely to get used.

Symptom, cause, fix

  1. 1A filter shows nothing at all. You have stacked two filters that cannot both be true — often Status is Done alongside Status is not Done. Check whether the filter group is set to And or Or.
  2. 2Your calendar view is empty. It points at a date property most rows leave blank. Fill in the dates, or point the view at a different date property in its layout settings.
  3. 3You made a second database instead of a second view, and the numbers now disagree. Move the rows back into the original and delete the copy. Two databases of the same thing always drift.
  4. 4A shared page shows a colleague more than you meant. Permissions inherit downward from the parent you shared. Share the specific child page instead.
  5. 5You cannot find a page you know exists. Press Cmd+P or Ctrl+P and search the title, then check Trash in the sidebar — deleted pages sit there before purge.
  6. 6The system feels heavy and you have started avoiding it. You built ahead of your needs. Delete the views and properties you have never filtered on.
Notion is one answer to note-taking, and it is worth seeing the other shape before you commit years of writing to it: How to Use Obsidian for Note-Taking covers the plain-text, local-files alternative and makes the tradeoff obvious. Once the tool question is settled, the harder problem is method, which is what How to Build a Second Brain is about. How to Make a Study Schedule pairs with the Tasks database you just built, and How to Use Excel for Beginners covers the spreadsheet skills a Notion table won’t replace. For the whole skill rather than one tool, the Learning Mastery roadmap sequences capture, retrieval, and practice in the order they build on each other.