Skip to content

Blog

Organisation4 min read

A Notion Database for Client Projects: Structure, Relations and Sharing

Projects and tasks as linked Notion databases, with a board, a calendar and CSV import. And why you should never share the whole database with a client.

  • #notion
  • #organisation
  • #digitalisierung
Updated

AI-assisted · editorially reviewed Details

Text size
Also asMarkdownJSON

A spreadsheet of client projects works until three people are editing it at once or someone wants to know which tasks on a project are still open. A Notion database solves both, because each row can be a page of its own with notes, files and linked tasks. Before building it, think about who will need to see the database later, because both the structure and the plan depend on that.

What is free and what is not

Notion can be used for free, databases included. According to the pricing page, however, the Free plan is meant for individuals: once two or more members work in the same workspace, the number of content blocks is limited until you move to a paid plan. On the Free plan, files can be no larger than 5 MB, and page history goes back seven days.

Guests, meaning outside people such as clients, are free of charge and possible on the Free plan too; the pricing page gives a limit of ten external guests. The common claim that guest access requires the paid Plus plan is not correct. Plus is mainly worth it when several employees need to work in the workspace as full members. The pricing page shows the current price; Notion says yearly billing saves up to 20 per cent.

Two databases rather than one

For client projects, a setup with two linked databases works well: "Projects" and "Tasks". If you have many repeat clients, add a third, "Clients". A client's address is then stored once rather than again in every project.

To create a database, make a new page and choose the table under "Get started with", or type /database on an existing page (Notion help on databases). Full-page databases suit this better than inline ones, because they appear in the sidebar and can be locked against accidental changes to their properties.

Properties for the project database

In Notion, every column is a property with a fixed type (overview of property types). For client projects, this selection is usually enough:

  • Project name: the title column every database has automatically.
  • Client: a relation to the client database. Without a client database, a Select field will do, but then you have to prevent typos in client names yourself.
  • Status: the Status type with its three groups To-do, In Progress and Complete. You can add your own stages within them, such as "Quote", "Commissioned", "In progress" and "Invoiced".
  • Start and deadline: two date fields.
  • Owner: a Person property for members or guests of the workspace.

Adding more columns at the start rarely improves the database. A field nobody has filled in after four weeks can go.

Linking tasks and counting what is attached

In the task database, create a relation to the project database. According to Notion's help on relations and rollups, you add a new property, choose the type "Relation", select the target database and confirm with "Add relation". If the "Show on …" toggle is on, the link appears in both databases.

The project database can then summarise the tasks attached to it using a "Rollup" property: you choose the relation, the property of the linked tasks and a calculation. With "Count all", each project shows how many tasks are linked to it; with "Latest date" on a date field, it shows the latest deadline among them.

Views for everyday work

The same entries can be shown in different views. A new view is added with the plus sign next to the database name (Notion help on views). Two make sense to begin with:

  • Board by status: Each project is a card that moves from column to column. Grouping is set in the view settings under "Group".
  • Calendar by deadline: The calendar arranges entries by a date property, so you can see which week is getting too full.

Filters are also set in the view settings. Note the difference when saving: a filter applies only to you unless you choose "Save for everyone".

Bringing in existing projects

An Excel file cannot be imported directly, but a CSV file can. According to Notion's help on importing, you open a full-page database, choose "Merge with CSV" from the dotted menu and map each column to a property. Column headers should match the property names exactly. Two limits matter: an import only adds new rows and does not update existing ones, and it cannot create new relations, rollups or formulas. With only a handful of active projects, typing them in is often quicker and cleaner.

Giving clients access without showing everything

This is where mistakes happen easily. If you share the entire project database with a client as a guest, they can also see every other client's projects. According to Notion's help on sharing, permissions for individual rows by person are only available on the Business and Enterprise plans.

On smaller plans, the safe approach is to share only the individual project page, since every database entry is a page of its own. Under "Share", enter the email address and choose a level, usually "Can comment" or "Can view" for clients. The guest needs their own Notion account. Before sharing, check whether the page contains internal notes, such as pricing calculations.

When Notion is not the right fit

Notion is flexible, and that flexibility costs time: someone has to set up and maintain every property and every view. If all you need is a shared task list with deadlines, a ready-made tool such as Asana gets you started faster. And if you want quotes, time tracking and invoices in one program, industry software usually serves better than a home-built database that only imitates those parts.

Responsible: Yusuf Senel. Written with AI assistance and editorially reviewed after publication. How wischtig.de works

Read next