Notion vocabulary is the practical language of pages, blocks, databases, properties, views, filters, templates and shared permissions. Start with workspace, page, block, database, property, relation, rollup, table view, board view, template and Can edit content. These words explain how information is stored, displayed and controlled.
The most important distinction is a database versus a view. In Notion, the underlying database stores records, while table, board, calendar, list or gallery views present the same underlying items differently. Creating a new view does not automatically create a separate copy of the data. Another key difference is Can edit versus Can edit content: the latter lets eligible database contributors change records without general permission to redesign the database’s structure.
Quick answer: Use ordinary pages for explanations and flexible documents. Use a database when every item needs consistent properties such as owner, status and due date. Create different views for different jobs, filter or sort without deleting records, and apply the minimum necessary access level. If enabling AI Meeting Notes, check plan entitlement, recording consent and the destination database’s sharing permissions before capturing confidential conversations.
- Build knowledge: pages, subpages, blocks, headings and links.
- Track work: database entries, properties, status, people and dates.
- Visualise tasks: table, board, calendar, timeline and filtered views.
- Connect information: relation, rollup and formulas.
- Reuse structures: page templates and database templates.
- Protect content: sharing roles, guests, public links and page-level access.
This independent guide explains Notion’s core working language. For spreadsheet terminology, see Vocabulary for Microsoft Excel | Formulas, Tables and Spreadsheet Terms Explained. For project-management vocabulary in connected documents, see the eduKateSG Vocabulary Articles & Knowledge Hub.
How one Notion database can answer several questions
Imagine a team recording every project task in a database. Each task is a page, while properties hold Status, Priority, Owner and Due Date. A table view makes precise editing easy. A board view groups the same records by status, and a calendar view positions them by their date. No one needs to maintain three separate copies of every task.
Now imagine showing only the tasks assigned to one person and due this week. A filter changes which records appear in that view; it does not erase the other tasks. Sorting changes their display order. Grouping organises items under a shared property. These are presentation choices, not proof that the underlying database has changed ownership or scope.
Notion’s official help explains that each database row opens as a full page, and that different views share the underlying entries. This is a crucial difference from a simple static table pasted into an ordinary document. A database becomes useful when the same set of structured records must be queried and displayed repeatedly.
Notion pages, blocks, workspaces and navigation
38 practical Notion terms. Read each definition with its example to understand what changes in the underlying information and what only changes on screen.
Notion
A digital workspace for documents, notes, databases and eligible team workflows. Example: Use Notion to organise shared project notes.
Workspace
The environment containing pages, members and related settings. Example: Join the correct workspace before creating client records.
Page
A content area that can hold blocks, subpages or databases. Example: Create a page for the meeting agenda.
Subpage
A page nested within another page for navigation and organisation. Example: Put each department’s notes in a subpage.
Block
A basic unit of Notion content, such as text, image, heading or to-do. Example: Move a block without rewriting the whole page.
Text block
A block containing ordinary writing. Example: Use text blocks for concise instructions.
Heading block
A block defining the title of a section within the document. Example: Heading blocks make long notes easier to scan.
Toggle block
A content block that can show or hide nested details. Example: Use a toggle for optional troubleshooting steps.
To-do block
A checklist item whose checkbox can be marked complete. Example: A checked to-do is not proof the whole project is approved.
Bulleted list
A set of related short items without a necessary sequence. Example: Use bullets for materials needed.
Numbered list
A sequence of items whose order matters. Example: Use numbers for a procedure.
Callout
A block visually setting off a specific note or warning. Example: A callout should contain a meaningful exception.
Quote block
A block presenting quoted words or a source statement. Example: Attribute the actual source of the quote.
Code block
A block displaying code or other preformatted text. Example: Use a code block for a reproducible snippet.
Image block
A media element displaying an uploaded or linked picture. Example: Give the diagram a meaningful caption.
File block
An attachment or file link inserted into a page. Example: Check file permissions before sharing.
Embed
Content from another service displayed within a Notion page where supported. Example: An embed may rely on external access rights.
Bookmark block
A link preview representing an external webpage. Example: A bookmark should point to a trusted destination.
Page icon
A symbol or small image helping identify a page. Example: Use consistent icons for projects.
Page cover
A banner-like picture displayed at the top of a page. Example: A cover is decoration rather than proof of accuracy.
Sidebar
A navigation area displaying workspace pages and sections. Example: Use the sidebar to find a recent project.
Favorites
A list of pages marked for quick access. Example: Favorite the current operating manual.
Private section
An area intended for pages not shared beyond the appropriate user under Notion settings. Example: Review sharing before treating a page as private.
Teamspace
An organisational area for selected teams with membership and visibility settings. Example: Create a teamspace for a department.
Teamspace owner
A role with management controls for an eligible teamspace. Example: A teamspace owner should review external membership.
Teamspace member
A person belonging to a selected teamspace under access policies. Example: Membership affects access to some pages.
Search
A feature for locating pages and related information accessible to the user. Example: Search for a project number rather than opening every folder.
Recent pages
Pages accessed recently under the user’s account interface. Example: Recent is not a permanent archive.
Trash
An area for deleted content that may be recoverable under current retention rules. Example: Check Trash before assuming a page is gone.
Duplicate page
A separate copy made from selected content. Example: Duplication can create outdated competing instructions.
Move page
Change a page’s parent or location under relevant permissions. Example: Moving a page can affect access inheritance.
Synced block
A block whose content can appear in multiple pages and update across those instances. Example: A synced block is not an independent copy.
Unsync
Break a block instance’s connection to its shared content under the feature’s controls. Example: Unsync before editing a one-off local variation.
Template
A reusable page or database layout that saves repeated setup. Example: Templates need checking before real use.
Slash command
A typing shortcut beginning with / to insert eligible content types. Example: Type /table to see related block choices.
Mention
A reference to a person, date or page that can link or notify in supported contexts. Example: Mention the responsible person in a task.
Page link
A reference navigating to another Notion page under access permissions. Example: A link does not automatically grant its recipient access.
Breadcrumb
A navigational indicator showing where a page sits in a nested structure. Example: Use breadcrumbs to return to the parent project.
Databases, properties, relations and rollups
39 practical Notion terms. Read each definition with its example to understand what changes in the underlying information and what only changes on screen.
Database
A structured collection of Notion pages described by properties and displayed through views. Example: Create a task database for projects.
Database item
An entry represented as a whole page with associated fields and content. Example: Open an item to read its full meeting notes.
Data source
The underlying dataset used by one or more eligible database views under the current Notion model. Example: Check which data source a view is showing.
Property
A named field associated with each database item, such as Status or Due Date. Example: Add a Status property for task tracking.
Title property
The main name field identifying an item or page in a database. Example: Give the task a specific title.
Text property
A field holding descriptive text without special numeric or date behaviour. Example: Use a Text property for notes.
Number property
A field holding numeric values for suitable sorting or formulas. Example: Store expected hours as a number.
Select property
A field permitting one choice from defined labels. Example: Use Select for priority.
Multi-select property
A field permitting multiple category labels. Example: Use Multi-select for relevant topics.
Status property
A field representing progress through a workflow with designated state categories. Example: Set tasks to In progress only while work is underway.
Date property
A field holding a date or eligible range of dates. Example: Store due dates rather than writing them only in body text.
Person property
A field associating members with a database record. Example: Assign the actual task owner.
Checkbox property
A true-or-false style field represented as a checkbox. Example: A checkbox can track a simple approval flag.
URL property
A field holding an internet address. Example: Store the primary source URL.
Email property
A field designed for email addresses. Example: Keep contact details in the intended field.
Phone property
A field intended for phone numbers. Example: Check the country code before calling.
Files & media property
A field holding file or media attachments. Example: Attach the final project deliverable.
Created time
A system-maintained property describing when a database entry was created. Example: Created time differs from the project’s actual start date.
Last edited time
A system property reflecting recent modifications to the database page. Example: Last edited time is not formal approval.
Created by
A system property identifying the account that created an eligible item. Example: Created by is not necessarily the present owner.
Last edited by
A system property showing a recorded editor of an item. Example: A recent edit may be minor formatting.
Formula property
A calculated field derived from other properties under Notion’s formula language. Example: A formula can calculate days remaining.
Relation property
A link connecting items between databases, or within the same database. Example: Relate a task to its project.
Rollup property
A field summarising selected values from related database pages under a relation. Example: Roll up a project’s completed task count.
Dependency
A relationship expressing that one task depends on another action or milestone. Example: The launch depends on final approval.
Parent item
A higher-level record containing or associated with sub-items under a chosen structure. Example: The parent task covers the whole campaign.
Sub-item
A smaller record belonging to a larger task hierarchy. Example: Break the project into sub-items.
Unique ID
A property generating a stable identifier for an item under supported settings. Example: Use the ID when referring to a specific request.
Button property
A database control triggering defined supported actions when selected. Example: Use a button to move an item through a workflow.
Automation
A configured workflow that reacts to events or actions under product and plan rules. Example: An automation can assign an owner when status changes.
Default value
The initial value a property can receive under a template or configuration. Example: A default status should not falsely mark work complete.
Required property
A field the workflow expects to be filled, sometimes enforced by database or form controls. Example: Make an intake field required where suitable.
Database template
A preset layout and selected property defaults used when creating new database entries. Example: Use a template for consistent meeting records.
Recurring template
A database template configured to create new pages on a repeating schedule, where supported. Example: A recurring template can generate weekly review pages.
Data consistency
Keeping property values and meanings stable across the database. Example: Do not use Pending and Not started interchangeably without rules.
Duplicate record
Two entries representing the same underlying task or entity. Example: Check for duplicate records before summing work.
Missing field
A record without a value needed for a report or decision. Example: A task with no owner is a governance problem.
Formula error
An invalid expression or data-type mismatch in a calculated property. Example: Inspect property names and types when a formula fails.
Database schema
The set of properties and structures defining how records are organised. Example: Agree a simple schema before importing hundreds of rows.
Views, filters, sorts and project planning
38 practical Notion terms. Read each definition with its example to understand what changes in the underlying information and what only changes on screen.
Database view
One presentation of existing database information using its own layout and settings. Example: A new view does not automatically duplicate the records.
Table view
A grid of database items as rows and properties as columns. Example: Use Table view for precise comparisons.
Board view
Cards arranged into groups, frequently based on status. Example: A Board is useful for moving tasks from To do to Done.
Calendar view
A view positioning records according to a chosen date property. Example: Use Calendar to review deadlines.
Timeline view
A representation of records along a time axis. Example: Timeline can show overlapping project stages.
List view
A simplified display of items with selected detail. Example: Use List for reading a concise action queue.
Gallery view
A card-oriented display highlighting images or page content. Example: Gallery suits a visual portfolio.
Chart view
A data visualisation built from database properties under eligible features. Example: A Chart can summarise workload by status.
Form
A structured intake interface writing responses to an associated database under current settings. Example: Use a form to gather project requests.
Dashboard view
An eligible layout combining relevant summaries or widgets for monitoring tasks. Example: Dashboards can help managers review multiple sources.
Linked view
A displayed view of a database placed somewhere else in the workspace. Example: A linked view points to the source rather than making a full copy.
Filter
A condition controlling which records appear in one view. Example: Filter to show tasks assigned to you.
Sort
An order applied to displayed records, such as due date or priority. Example: Sort by earliest deadline first.
Group
An arrangement collecting records under a shared property value. Example: Group a board by Status.
Subgroup
An additional level of grouping where supported. Example: Subgroup tasks by department after status.
Ascending
A sort order from smaller to larger or earlier to later. Example: Sort due dates ascending.
Descending
A sort order from larger to smaller or later to earlier. Example: Sort revenue descending.
Hidden property
A database field not shown in the current view but retained in the records. Example: Hidden properties still exist.
Visible property
A field selected to appear on cards or rows in the current view. Example: Show Priority and Owner on the board.
View settings
Controls governing layout, visible properties, filters and sorts. Example: Check view settings before assuming a task was deleted.
Save for everyone
An option applying selected view changes broadly rather than only to the current user where supported. Example: Do not change everyone’s preferred sort unnecessarily.
Personal view adjustment
A local display change not necessarily visible to other members. Example: Choose a personal sort without rewriting team workflow.
Freeze column
Keep selected table columns visible while scrolling horizontally. Example: Freeze the task title for a wide database.
Date range
A record holding start and end dates for a task or event. Example: A timeline needs an accurate date range.
Due date
The intended deadline for an action. Example: Write a specific due date with time zone when relevant.
Priority
The relative urgency or importance assigned to a task. Example: A high-priority task may not be the earliest due.
Task status
The stage of work such as Not started or In progress. Example: Completed should mean verified output.
Task owner
The person responsible for delivering a defined result. Example: Every action should have a clear owner.
Milestone
A significant checkpoint in project progress. Example: A draft approved is one milestone.
Project
A body of related work with a shared goal. Example: A project can relate to several task pages.
Kanban
A workflow representation showing work moving through states on a board. Example: Kanban can expose excessive work in progress.
Work in progress
Tasks actively underway rather than completed or not yet begun. Example: Too much work in progress can increase delays.
Capacity
Available time or resources for carrying out work. Example: Capacity affects realistic deadlines.
Backlog
A collection of potential or pending work not yet scheduled for execution. Example: Not every backlog item has a firm due date.
Dependency link
A connection expressing an ordered requirement between tasks. Example: Identify which approval must occur first.
Progress metric
A measure of work completed according to explicit definitions. Example: A progress chart can mislead when tasks differ greatly in size.
Status meeting
A recurring review of progress, risks and next actions. Example: Use status meetings to resolve blockers, not merely repeat updates.
Single source of truth
An agreed maintained record treated as authoritative for the current state. Example: Choose one master database rather than competing spreadsheets.
Sharing, permissions, templates and Notion AI
37 practical Notion terms. Read each definition with its example to understand what changes in the underlying information and what only changes on screen.
Share menu
The interface for granting and reviewing access to a page or database. Example: Review the Share menu before sending a link.
Workspace member
An account belonging to a workspace under the relevant role and plan. Example: Workspace membership may create broader visibility than guest access.
Guest
An invited external user with access to selected pages rather than the whole workspace by default. Example: Invite a client as a guest only to the necessary material.
Full access
A Notion permission enabling broad editing and sharing rights on an eligible page. Example: Full access should be limited to trusted managers.
Can edit
A permission to modify page content without the same broad sharing authority as Full access. Example: Use Can edit for a co-writer.
Can edit content
A database permission permitting page content and property changes without general schema editing. Example: Use Can edit content for task contributors.
Can create
A database permission on eligible Business or Enterprise plans that lets people add pages without necessarily viewing others’ records. Example: Can create can support confidential intake.
Can comment
An access level allowing feedback rather than direct editing. Example: Give Can comment to a reviewer.
Can view
An access level intended for reading without general editing or comments. Example: A recipient can view a handbook without changing it.
Public link
A link that can permit access beyond invited workspace users under configured permissions. Example: A public link should not contain private client records.
Web publishing
Making an eligible Notion page accessible as a site under selected settings. Example: Published to web is not the same as invited private sharing.
Link expiration
A rule limiting how long an eligible shared link remains usable. Example: A link can expire without erasing an already downloaded copy.
Page-level access
A selected permission rule applied to particular database items under supported plans. Example: Page-level access can restrict which tickets a user sees.
Inherited permissions
Access obtained from the enclosing page or workspace context. Example: Review parent access before placing confidential content below it.
Remove access
Revoke a sharing grant through supported controls. Example: Check whether another group permission still grants access.
Template gallery
A collection of reusable page and database templates. Example: Read a template’s actual properties before installing it.
Template duplication
Creating an independent copy of a selected template under its rights and limits. Example: Duplicating a template can create an outdated disconnected version.
AI Meeting Notes
A Notion feature transcribing and summarising eligible meetings under the relevant plan. Example: Verify meeting consent and access before recording.
Meeting transcript
A speech-to-text record generated from the meeting’s audio under an eligible workflow. Example: A transcript can mishear important numbers.
AI summary
A generated overview of meeting discussion and action items. Example: An AI summary can confuse a proposal with an approval.
Meeting-note sharing
The permissions controlling who can see AI meeting records. Example: Check whether auto-share is enabled before taking private notes.
Default meetings database
The database where newly created AI Meeting Notes are stored under account or workspace settings. Example: A default database’s sharing controls affect visibility.
Notion Agent
A Notion AI capability for supported tasks using available workspace context and tools. Example: AI actions need review and appropriate access limits.
Enterprise Search
A supported search experience using eligible connected and internal information. Example: Connected search cannot verify every claim.
AI Connector
An integration enabling eligible AI use of information from another system. Example: Review AI connector permissions before enabling it.
AI Autofill
A database feature that can help generate or update property values under specified rules. Example: Review autofilled summaries before relying on them.
AI block
A page element that can produce or transform supported content using Notion AI. Example: Generated content requires fact-checking.
Automation trigger
An event that starts an eligible configured workflow. Example: A changed status can trigger a notification.
Automation action
The operation performed after a valid trigger. Example: An action can update a property or send a message.
Automation failure
A workflow that did not complete as expected. Example: Check execution results before assuming a notification was sent.
Privacy audit
A deliberate review of permissions, public links, AI data access and saved records. Example: Audit access after contractors leave.
Data retention
Rules determining how long deleted or archived information remains recoverable. Example: A template is not a legal record-retention policy.
Export
A process for saving eligible Notion pages or workspace information in another format. Example: Keep an export before a major migration.
Import
Bringing material from another service or file into a Notion page or database. Example: Check for lost formatting after importing.
Backup
A separately recoverable copy of essential information, distinct from merely viewing a synced page. Example: Export or maintain suitable backups for critical records.
Source attribution
Documenting the origin of facts, images or borrowed content. Example: An AI-generated paragraph needs original evidence.
Editorial approval
An explicit decision authorising content to be published or used. Example: A checked box does not necessarily mean approved by the manager.
Five Notion questions that require precise vocabulary
A colleague sees the wrong tasks on a board
Check the active database view and its filters before assuming records were deleted. One view may show only tasks with Status = In progress or a particular person as Owner. Switch to the full table view to check the underlying entries. Do not delete and recreate the project because a view filter hid its items.
A contributor should update tasks but not break the database schema
Notion’s current sharing documentation distinguishes Full access, Can edit and Can edit content. The database-specific Can edit content role allows eligible users to create and edit pages and modify property values without changing the database structure, properties or views. Use the minimum level that supports the work; broad Full access includes sharing controls and should be granted carefully.
Projects need to show the number of completed tasks
A relation property can connect each task with its parent project. A rollup can summarise selected values from those related task pages. That is different from duplicating totals by hand in the project page. Make sure the relation is complete, and check what a rollup actually counts before reporting a progress percentage.
Private meeting notes appear in a shared workspace
Notion’s current AI Meeting Notes help warns that turning off automatic sharing does not make notes in a shared database private. The database’s own access permissions remain decisive. Before creating notes, review where they will be filed, whether automatic participant sharing is enabled, and who can view the underlying page. Participants’ consent and the organisation’s recording rules also matter.
A project keeps losing its agreed format
Use a database template with prefilled properties, headings and standard instructions for new records. A template helps produce consistent structure, but it cannot guarantee staff complete every field accurately. Combine templates with clear required information and a review process rather than assuming automation creates quality by itself.
Notion terms people often mistake for one another
- Page versus block: a page holds many individual blocks.
- Database versus table view: the data structure differs from one visual layout.
- View versus duplicate database: an additional view ordinarily displays the same records rather than an independent copy.
- Filter versus delete: hidden records remain in the database.
- Sort versus priority: a display order is not necessarily a business rule.
- Relation versus rollup: a relation links items; a rollup summarises linked data.
- Template versus automation: a reusable structure differs from a triggered action.
- Can edit versus Can edit content: database structure permissions differ.
- Can create versus Can view: eligible confidential intake can permit additions without exposing existing records.
- Public link versus private invitation: anyone with access to the public link may have broader reach.
A practical Notion workspace setup
Step 1 — Define the task. Choose one problem to solve: project progress, meeting records, notes, documents or client requests. Avoid building a huge database merely because many fields are possible.
Step 2 — Choose pages or a database. Use pages for unstructured explanations; use a database if many records share fields such as status, owner, date and category.
Step 3 — Start with minimal properties. Include Title, Status, Owner, Due Date and the necessary links. Add relations, rollups and formulas only after their purpose is clear.
Step 4 — Create views for specific readers. A board can help team execution, a table can support accurate data entry, and a calendar can show deadlines. Test filters with known sample records.
Step 5 — Set access rights carefully. Check workspace, teamspace, parent-page, guest, link and database permissions. A hidden property is not a security restriction.
Step 6 — Establish a review and backup process. Verify AI-generated notes, record important approvals, keep relevant original sources and export critical information where policy requires.
Practice: choose the Notion word
- A single document with paragraphs, images and headings: page with blocks.
- A collection of tasks with the same properties: database.
- A row that opens into its own detailed note: database item.
- Tasks grouped as To do, In progress and Done: board view.
- Tasks placed by deadline: calendar view.
- Display only work assigned to one colleague: filter.
- Connect a task with the corresponding project: relation.
- Count related completed tasks: rollup.
- Let a contributor change task data but not the database structure: Can edit content.
- A repeatable project-intake layout: database template.
Frequently asked questions
Is a Notion database the same as an Excel spreadsheet?
No. A Notion database consists of page-based records and typed properties, displayed through multiple views. Excel is a spreadsheet with grid cells and calculation behaviour.
Does creating a new Notion view duplicate the database?
No. Views ordinarily present the same underlying source items with distinct layout, filters and sorting settings.
What is the difference between a relation and a rollup?
A relation links records in one or more databases. A rollup derives a summary from properties on related entries.
What does Can edit content mean?
It is a Notion database permission for editing records and their property values without general control over database structure, views and properties.
Can someone submit information without seeing other records?
Certain Business and Enterprise setups offer a Can create permission for eligible database workflows. Check plan and configuration requirements.
Is a Notion shared page private if it has a long URL?
Not necessarily. The effective sharing settings, parent permissions and public-link arrangements determine access.
Do AI Meeting Notes automatically remain confidential?
No. Notion explicitly warns that notes filed in shared databases can inherit that sharing context, even when auto-sharing is disabled.
Are Notion AI summaries guaranteed to be accurate?
No. Generated notes should be checked against the original discussion and approved decisions before being used as formal records.
Official Notion sources and related learning
- Notion — create a database
- Notion — database views, filters, sorting and grouping
- Notion — sharing and permissions
- Notion — using database templates
- Notion — AI Meeting Notes and sharing limitations
- Notion — AI capabilities and limitations
- eduKateSG — Vocabulary for Google Drive
- eduKateSG — Vocabulary for Microsoft Teams
Notion features, permissions and subscription eligibility evolve. Before using an automated workflow or a shared database for personal or organisational records, inspect the current primary documentation and actual workspace settings.