Notion Guide: Pages, Databases & Sharing

Notion is a workspace for notes, documents, tasks, knowledge bases and databases. To get started, open Notion, create a page for one real purpose, give it a descriptive title and add text, a checklist or a simple table. Only create a database when you have repeated items that genuinely need properties such as Status, Owner or Due date.

Quick answers: A page holds content; a database organises many page-like records; views show the same database as a table, board, calendar or list; filters change which records are displayed; sharing controls determine who can read, comment, edit or publish. For private work, inspect both the page’s permissions and the wider workspace or teamspace access before copying a link.

The most common Notion mistake is overbuilding. A person who only needs five meeting notes may spend hours making a complicated dashboard with linked databases, icons and formulas. Another mistake is assuming that hiding a database column hides the information from collaborators. View settings are for presentation; confidentiality depends on actual access permissions.

Jump to: Create a page · Blocks · Databases · Views · Sharing · Exports · Privacy · FAQ.

What is Notion, and what is it best for?

Notion combines flexible document pages with structured databases. People use it for personal notes, reading lists, research, team documentation, task trackers, project plans and public knowledge pages. You can work alone or collaborate within a workspace. Features and limits depend on the plan, role and current product experience.

It helps to distinguish three jobs. A document page explains something in prose. A database keeps a repeated set of structured records. A workspace defines where people collaborate and which permissions and policies apply. These layers connect, but one does not replace the others.

Notion can become a useful operating home for a project when its structure reflects real work. It is not automatically a secure archive, a relational database for every technical workload or a replacement for specialist accounting and legal records. Choose it because the pages and views reduce effort, not because every task must be turned into a dashboard.

Create your first useful Notion page

Open Notion using the correct account and workspace.
Choose New page or the appropriate page-creation control.
Give it a specific title, such as ‘Project Kickoff — Decisions and Actions’.
Write the purpose in the first paragraph and add a clear heading.
Insert the necessary content: checklist, short notes, table or reference links.
Review where the page appears in your sidebar and who has access.
Return the next day and check whether you can find the information without remembering every click.

A good starting page might contain Goal, Current status, Next actions and Important links. That is enough for many small projects. Add complexity only when repeated work reveals that the simple structure is genuinely inadequate.

A page that starts with a useful answer is easier to trust and reuse than a page with a large cover image followed by vague introductory prose. Design can help orientation, but it should not delay the actual information.

What are Notion blocks?

Notion organises page content into blocks. A block might be a paragraph, heading, checklist item, image, toggle, table or embedded object. This allows people to move pieces of a document without necessarily editing a long, continuous text stream. The block model is convenient, but it can surprise newcomers who expect every page to behave exactly like Microsoft Word.

When using slash commands or the insert menu, choose the simplest block that matches the meaning. A checklist is appropriate when an item can be completed. A numbered list is appropriate when order matters. A heading introduces a new subject. A toggle can hide secondary detail without deleting it.

Do not place essential instructions inside many nested toggles merely to make a dashboard compact. The most important information should remain easy to discover. If new readers cannot tell where a decision is located, the structure is not serving its purpose.

Pages, subpages and the sidebar

Notion pages can contain nested pages or subpages, helping users group content by project or theme. A top-level page might be ‘Research Project’, with subpages for Sources, Interviews and Draft report. That structure is useful when the parts have clear relationships.

Too much nesting makes navigation slow. If people must open six pages to find one deadline, the workspace needs simplifying. Use descriptive page names and preserve important entry points in the sidebar. A small number of stable navigation pages can reduce repeated searching.

Remember that nesting also has permission implications. A subpage may inherit access from a parent or workspace settings. Moving a page into a different shared area can change its audience. Review permissions after major reorganisation.

When should you use a database instead of a page?

Use a database when you have many entries of the same type and want consistent properties, sorting or filtering. Examples include a reading list, a customer-support tracker, an editorial calendar or an inventory of research sources. An ordinary document is often better for a single essay, explanation or meeting note.

A Notion database contains items that are themselves pages, plus properties such as title, status, select, multi-select, date, person or number. This is why a database row can hold detailed notes as well as structured fields. It can be more flexible than a plain spreadsheet, but it is not automatically better for arithmetic-heavy tasks.

The decision is about repetition. If you create one event notice, write a page. If you manage two hundred event registrations with due dates, status and owners, a database or appropriate form system may be useful. Do not build a full database only because the app makes it visually appealing.

Create a simple task database

Create a new page and insert a database using the supported Notion controls.
Name the database ‘Project Tasks’ or another clear title.
Keep a Name or Task property for each record.
Add a Status property with simple values such as Not started, In progress and Complete.
Add an Owner property if more than one person is responsible.
Add a Due date only when the task actually has one.
Enter five genuine tasks and test whether sorting or filtering helps you find the next action.

Avoid adding twenty properties before entering real records. A task tracker is useful when it answers ‘What must happen next, who owns it and when is it due?’ Additional fields should earn their place by solving a recurrent question.

If the work involves an external dependency or approval, record it explicitly rather than marking the task Complete prematurely. ‘Draft sent’ is a different state from ‘Client approved’. Clear status names prevent incorrect assumptions.

Table, board, calendar and timeline views

Notion can display the same database through multiple views. A table shows records and properties in rows and columns. A board commonly groups cards by a property such as Status. A calendar displays items with dates. A timeline can show scheduled spans, depending on the available date information.

A key distinction is that switching views usually does not create a separate duplicate of every record. It changes how the same source data is presented. If you update a task’s status in Board view, the corresponding record reflects that change in other views where it is included.

Choose the view that answers the specific question. A board may be best for progress through stages; a calendar for dates; a table for detailed comparison; and a gallery for visually identifying media. More views do not necessarily improve the system.

How to create a second view of one database

Open the database and find the current view name.
Select the plus control next to the views or the current menu to add a view.
Choose Board, Calendar, List or another suitable layout.
Assign a name describing its purpose, not merely ‘View 2’.
Configure which properties appear and any grouping, filter or sort.
Check that the new view shows the intended records.
Explain to collaborators which view should be used for which task.

For example, a project database may have ‘All tasks’ as a table, ‘By status’ as a board and ‘Deadline calendar’ as a calendar. The records remain related, and users can move between overview and detail without maintaining three separate source lists.

If a calendar view looks empty, check whether the items have values in the date property selected by the view. An empty calendar does not automatically mean there are no tasks.

Filtering versus sorting: two different questions

Filtering decides which database records are displayed. Sorting decides in what order they appear. A filter might show only tasks assigned to a particular person. A sort might put the earliest deadline first. A view can combine them to answer a practical question such as ‘My incomplete tasks due soon’.

Notion’s current help describes creating filters through View settings, including advanced filters with combinations of AND and OR conditions. It also distinguishes personal view choices from settings saved for everyone. Be deliberate about whether a view should change for the whole team.

A filtered view is not a security boundary. Someone with access to the underlying database may be able to create or visit another view showing additional rows. If a person must not see a sensitive record, use suitable page-level or workspace access controls, not merely a filter hiding the row.

Why a hidden property is not confidential

A view may hide a property to make the screen less crowded. That does not necessarily remove the information from the underlying database record. A collaborator with broader access may be able to reveal properties or use another view. Display choices and access control are different systems.

Imagine a task database with a hidden column for private client notes. Hiding the column from a public-looking board does not make the notes safe for an external guest who can access the underlying page. Create a genuinely restricted record or separate database if confidentiality is required.

This principle also applies to published pages: review nested pages, embedded databases and visible links rather than assuming a simplified display can hide private material from everyone.

Relations, rollups and formulas: use only when needed

Notion offers more advanced database properties and relationships, including ways to link records across databases, calculate or summarise certain information and build formula expressions. These features can support project workflows, but they require a clear data model to avoid misleading outputs.

For example, a Projects database could relate to a Tasks database. The relationship can help a manager see which tasks belong to each project. But if people fail to assign tasks consistently, a summary can appear complete while some work is unlinked.

Do not build complicated formulas merely to produce colourful status indicators. Start with accurate source records and clear definitions. A simple manual status check may be safer than a sophisticated formula whose assumptions no one on the team understands.

Templates: make repeated work easier

Templates are useful when the same structure recurs. A meeting-note template might include Agenda, Decisions, Actions, Owners and Next meeting. A reading-note template might include Source, Question, Evidence and Summary. This reduces the time required to remember what information belongs in each record.

Before adopting a public template, inspect its database properties, formulas, links and sharing context. A polished dashboard may assume a workflow that does not suit your project. Remove unnecessary sections instead of spending hours adapting your work to the template.

A good template should reduce effort after the third or fourth use. If every new page requires substantial manual changes, simplify the template or return to a regular page.

Notion’s current help describes several access levels: Full access, Can edit, Can comment and Can view, with additional database-specific permissions in certain plans. Full access can include sharing rights. Can edit is appropriate when collaborators should change content but not necessarily manage the audience.

Open the page and select Share.
Review its current visibility and the inherited or workspace-level access.
Invite named people or groups who need the page.
Choose Can view, Can comment, Can edit or Full access based on actual responsibilities.
Check whether any public link or Publish setting is enabled.
Ask a trusted recipient to verify they can see only the intended content.
Remove or reduce access when the collaboration ends.

Notion also describes an ‘Anyone on the web with link’ sharing option. This can let someone open a page without being an ordinary workspace member. A link may be forwarded, so it is unsuitable by default for private financial, personnel or student records. Use narrower permissions when confidentiality matters.

Notion Site publishing is a separate workflow intended for presenting pages publicly on the web, sometimes with search-engine indexing and public-site features. Publishing a page deliberately is not the same as giving one colleague a private collaboration link.

Workspace members, guests and teamspaces

A workspace can contain members, guests and shared team areas. Their roles and access rights depend on the plan and configuration. Members may have broad default access to workspace content, while guests can be invited to particular pages. The exact model matters when you collaborate with a client or contractor.

A private one-on-one meeting note should not be placed in a teamspace that everyone can search if it includes sensitive information. Equally, a shared project guide should not live only in one person’s private section if the whole team needs it. Choose the location based on the intended audience and continuity requirements.

Review access when people change roles or leave an organisation. A workspace can outlive a particular employee, but only if ownership and permissions have been planned. An individual’s private page is not automatically the right permanent home for organisational knowledge.

Database permissions: editing content versus structure

Notion’s database permissions can distinguish people who edit records from people who change the database structure. The Can edit content role allows working with items and property values without general permission to alter database properties, views, sorts or filters, according to Notion’s current help.

This is useful when several people must update tasks but only a smaller group should redesign the tracker. Changing or deleting a Status property can break views and summaries used by everyone; adding a new task is a different level of responsibility.

Some more specific permissions, including the ability to create without seeing existing records and page-level database access, are plan-dependent. Do not promise these features to every free workspace. Check the account and documented eligibility before designing a workflow that requires them.

Notion databases are not spreadsheets with unlimited powers

A database table may resemble a spreadsheet, but Notion emphasises pages, properties and views rather than all the cell-by-cell numerical operations of a spreadsheet. If you need extensive calculations, financial modelling or large CSV transformations, Google Sheets or Excel may be the more appropriate primary tool.

If the goal is project organisation, Notion can keep task descriptions, meeting notes and responsible people connected with the same record. If the goal is a precise accounting ledger, choose a system that supports the relevant controls and audit requirements. The right choice is based on the job, not which interface looks more modern.

Data can also move between systems, but imports and exports may change formats or metadata. Test a sample before moving an entire critical workflow.

Notion search: find the right page later

A useful knowledge base allows readers to locate information by meaningful titles and consistent structure. Name pages after the question or decision they answer, not the mood of the day. ‘How to onboard a new volunteer’ is more discoverable than ‘Things we talked about’.

Search may find pages and content available under your access permissions. If a document is missing, check the workspace, teamspace, page hierarchy and whether you are signed into the intended account. A page disappearing from the sidebar does not always mean it was deleted.

Before creating a duplicate, look for an existing source page and confirm which is authoritative. Multiple nearly identical policy pages can cause contradictory decisions when only one is updated.

How to build a practical personal dashboard

A dashboard can bring together Today, This week, In progress and Important references, but it should remain lightweight. Show the information necessary for the next action. A dashboard that requires constant grooming becomes another project rather than a tool that helps complete projects.

A good starting dashboard links to two or three reliable pages or database views. If you cannot find a task within a few seconds, simplify the navigation and labels. Avoid giant cover images or a dozen decorative widgets that push actual work off the screen.

Review the dashboard after a week. Ask which sections were actually used. Remove unused sections. The smallest system that reliably supports a real habit is often the best one.

Export Notion pages, databases and workspaces

Notion’s official help describes exporting pages or databases in formats including PDF, HTML and CSV where appropriate. Desktop users can open a page’s menu, choose Export and select a supported format. Workspaces can have a separate export process subject to plan and administrative permissions.

Open the page or database you are authorised to export.
Find the top-right menu and choose the Export option.
Select PDF, HTML, Markdown/CSV or another supported format appropriate to the content.
Review whether subpages, files and images should be included.
Start the export and save the result in an authorised location.
Open the downloaded files and verify the content and attachment structure.
Keep a copy independent of the same workspace if backup is the purpose.

Notion warns that exporting a workspace does not mean it can be re-created instantly by simply reuploading the exported package. The data may be useful as a human-readable archive, but relationships, permissions and some features may not round-trip identically. Test the actual restoration route before treating an export as a complete backup.

Exports are also governed by access. Material you lack permission to view may not be included, and an administrator may restrict exporting. Do not bypass organisational controls to move confidential work into personal storage.

CSV and PDF exports have different purposes

A CSV can help move database records into a spreadsheet, but it cannot represent every Notion page layout, nested block or permission setting. A PDF is useful for a readable static snapshot, but not for reconstructing a living collaborative database. An HTML export can preserve a different kind of page representation.

Choose the format based on the next task. If the recipient needs to read an approved policy, a PDF might be suitable. If a data analyst needs records and properties, a CSV might be more useful. If a team must rebuild an interactive workspace, plan a structured migration rather than expecting an export to be a perfect clone.

Check that important dates, numeric properties, tags and links survive the export. A report that looks complete but omits an attachment or note may be unusable for the original purpose.

Backups and why sync is not enough

A cloud workspace can make your content available from several devices, but access depends on an account, service availability and permissions. An accidental deletion, incorrectly broad edit or loss of account access can still interrupt your work. An export and appropriate independent backup can improve resilience, subject to the limitations described above.

For irreplaceable information, maintain an appropriate external copy and review it periodically. A backup is useful when you can open it without the source system. Test a sample restoration or retrieval, not only whether a download succeeded.

For business records, consider the relevant retention and regulatory requirements before choosing a storage location or exporting confidential information. A backup process must be authorised as well as technically possible.

Privacy: private pages, public links and embedded content

A page in a private section is not the same as a published site. A page shared with the whole workspace is not automatically appropriate for external partners. Review the audience at every level. Notion’s current sharing settings make these distinctions visible, but the creator must choose correctly.

Do not paste API keys, passwords, account recovery codes or unnecessary personal identifiers into a normal project page. If sensitive details are necessary, use an approved secrets or records system rather than treating a hidden toggle or view as encryption.

Embeds and external links may involve third-party services with their own access rules. A person who can open the Notion page may not be able to open the embedded source, and an externally shared source might be accessible more broadly than the page itself. Check each service’s permissions separately.

Notion for study and personal learning

A student can use pages for topic summaries, a database for assignment deadlines and a reading list for sources. The value comes from retrieving and practising knowledge, not copying everything into a visually elaborate workspace. After taking notes, write a short explanation from memory and test the concept with a new example.

A reading database might contain Title, Author, Topic, Source, Date read and a paragraph explaining the main idea. Avoid making every imported article a completed learning outcome. The student should be able to say why the source matters and whether it is trustworthy.

For group assignments, use permissions that allow appropriate collaboration without exposing unrelated private notes. Follow the school’s rules on AI assistance, attribution and sharing student information.

Notion for a small business or project team

A team may build a simple project hub with a decision log, task tracker and reference documents. The task database provides status and owners; the decision page explains what was approved; the reference section links to official sources or contracts. This is more dependable than leaving every decision buried in chat history.

A useful operating rule is that every important action has one owner, a clear outcome and a realistic deadline. A status property called ‘In progress’ should not obscure the fact that the work is blocked by a supplier. Add a reason or dependency when it affects the next decision.

Do not use a public Notion page to handle private customer information just because it is easy to share. Data protection and permissions remain essential. If the business requires auditable financial transactions or regulated records, use the appropriate specialised system.

Three practical Notion examples

A study revision tracker

Create a database with Subject, Topic, Date, Status and Evidence of practice. Use a board to see topics by progress and a calendar for deadlines. Keep a separate page for explanations and worked mistakes. Review what you can recall rather than trusting a green Complete label.

A family event planner

Create one page with date, venue, travel details and an action checklist. Use a small database only if many guests, tasks or bookings must be tracked. Share the public event information separately from private addresses, expenses or personal documents.

A freelance project hub

Use a restricted client page with brief, milestones, delivered files and agreed decisions. Let the client comment if review is needed. Keep internal calculations and unrelated client information in genuinely separate private areas, not merely hidden columns on a shared board.

Common Notion problems and straightforward fixes

The workspace feels complicated and slow to use

Reduce unnecessary databases, properties and dashboard widgets. Begin with one page and one task list. Add structure only where a repeated problem justifies it.

The calendar view is empty

Check that records have values in the Date property selected by the view and that no filter hides them. The same records may still exist in Table view.

A colleague cannot edit the database

Inspect the page’s actual access role and any database-specific permissions. Can view, Can comment and Can edit content provide different capabilities.

Someone can see a property I hid

Hiding a property in one view does not necessarily restrict access to the underlying data. Use real permissions and separate restricted records where confidentiality is required.

A public Notion link reveals more than expected

Review Share and Publish settings, nested pages and linked databases. Restrict or unpublish the page as appropriate and remember that copies someone already saved may persist.

An export is missing information

Check file format, access scope, subpage settings and whether attachments or database properties were included. A workspace export is not a guaranteed one-click full restore.

The same task appears in several views

That may be intentional: different views of one database show the same underlying item. Check the record identity before deleting what looks like a duplicate.

A fifteen-minute Notion workspace audit

Identify the main purpose of the workspace.
Check that pages and database titles are meaningful.
Remove unused properties or dashboard elements that create confusion.
Verify that every important task has an owner and status.
Check whether filters hide records from a report.
Review public links, guest access and teamspace membership.
Ensure private information is protected by actual permissions.
Export one non-sensitive page and inspect the downloaded copy.
Confirm the authoritative source for the next project decision.

A good Notion setup is one that people can operate without a complicated manual. The system should reduce the time needed to find a decision, complete a task or learn something new.

Frequently asked questions about Notion

Is Notion free?

Notion offers a free experience and paid plans, with differences in features, limits and administration. Check the current plan terms for the capabilities you need.

What is the difference between a page and a database?

A page holds content; a database keeps a set of page-like records organised by properties and shown through different views.

Does changing a board change the underlying table?

When both are views of the same database, edits to records normally affect that shared source. The view changes the presentation rather than making an independent duplicate.

Does hiding a property keep it secret?

No. View visibility is not the same as access permission. Restrict the underlying data if it must remain confidential.

Can I give someone permission to edit tasks but not redesign the database?

In supported contexts, the Can edit content level allows editing database entries without broad permission to change the database structure.

Can I publish a Notion page on the web?

Yes, through the supported Publish experience. Public publishing is different from sharing a private collaboration link.

Can I export a database as CSV?

Yes, through supported export options. Check whether the resulting CSV contains the fields you need and whether any nested content is omitted.

Can a full export recreate my entire workspace automatically?

Not necessarily. Notion explicitly warns that an exported workspace cannot simply be reuploaded to recreate everything instantly.

Official Notion sources and next useful step

Notion’s documentation covers database basics, creating databases, views, filters and sorting, sharing and permission levels and exports and their limitations. Check current feature availability, which may differ across plans and workspaces.

Start by creating one page for a real project and five tasks with Status and Due date. Build a Board view only if it helps you find the next action. Then check permissions. That is enough to understand Notion’s core value without overengineering your workspace.

Explore Google Docs for shared writing, Google Sheets for structured calculations, Microsoft Teams communication and Notion vocabulary.

Continue this batch of practical guides: Google Forms · Microsoft Word · Microsoft PowerPoint. Each article addresses a distinct task; use the current official product help pages for changing interfaces or permissions.

Everything we need to know about Notion | Pages, Databases and Sharing