← All Notion guides · Try a short exercise
If you keep copying the same client, project or deadline information between Notion tables, the problem is usually not the data. It is the connection between the databases.
Start with a real problem: Clients and Projects live apart
Start with two databases called Clients and Projects. Use each database’s title property for the record name. In Clients, create Sarah Chen, Alex Rivera, and Maya Patel. In Projects, create Website redesign; you will add the other five projects in the rollup example below. If you already have these databases, use fictional test records instead of changing live client work.
CLIENTS
Sarah Chen
Active client
sarah@example.com
PROJECTS
Website redesign
In progress
Due 18 October
Sarah is the client for the website redesign. If you type “Sarah Chen” manually into the project, you have created text — not a connection. Rename the client, open Sarah’s page, or add another project and those pieces still know nothing about each other.
The cleaner model is:
PROJECT → belongs to → CLIENT
1. Connect the databases with a Relation
- Open the Projects database. Add a new property.
- Choose Relation as the property type.
- Select the Clients database as the database you want to connect.
- Name the property Client. Enable Show on Clients and name the reciprocal property Projects. This gives the Clients database the relation needed for the rollup below.
- Open the Website redesign project and select Sarah Chen in the Client relation.
Now Sarah is not duplicated inside Projects. The project points to the actual Sarah Chen record. With a two-way relation, Sarah’s client record can also show the projects connected to her.
2. Use a Rollup when you need information from the related database
A Relation answers which record is connected? A Rollup answers what information from those connected records do I need here?
Add a Number property called Project Value to Projects. These six fictional records give you a small, reproducible example; the amounts are illustrative, not pricing recommendations.
| Project | Client relation | Project Value (USD) |
|---|---|---|
| Website redesign | Sarah Chen | 3000 |
| Brand refresh | Sarah Chen | 2500 |
| Landing page | Alex Rivera | 1200 |
| Email templates | Alex Rivera | 800 |
| Portfolio site | Maya Patel | 1800 |
| Presentation deck | Maya Patel | 700 |
- Connect each project to its client using the Client relation.
- In Clients, add a Rollup property called Total project value.
- Choose Relation: Projects, Property: Project Value, and Calculate: Sum.
The expected totals are Sarah: $5,500, Alex: $2,000, and Maya: $2,500. To check the connection, change Website redesign from 3000 to 3200: Sarah’s total should become $5,700. Restore 3000 afterward. If the total is wrong, check the selected client, the numeric property, and the rollup calculation.
Relations are one-way by default. For this client-side total, keep the reciprocal Projects relation enabled. See Notion’s official Relations and Rollups documentation.
If you are still deciding which property you need, compare Notion Relations vs Rollups before adding more connections.
| Need | Use | Example |
|---|---|---|
| Connect records | Relation | Website redesign → Sarah Chen |
| Show related information | Rollup | Client → total project value |
| See the same database somewhere else | Linked view | Sarah’s projects on a client dashboard |
Projects relation:
Website redesign
Brand refresh
Website redesign: $3,000
Brand refresh: $2,500
Client relation: Sarah Chen
Projects → Project Value → Sum
$5,500
Test $3,200 + $2,500 = $5,700
Illustrative diagram using the fictional records in this guide; not a Notion screenshot.
Three checks before using the connection for real work
Use the fictional records above. These checks distinguish a real relation from copied text and show which source values contribute to a rollup. Change one thing at a time and restore the practice data after each test.
| Test | Expected result | What it checks |
|---|---|---|
| Rename Sarah Chen to Sarah Chen — Test in Clients. | Website redesign’s Client relation displays the updated page name. Sarah’s total remains $5,500. | The relation points to a page, rather than an independently typed name. |
| Change Website redesign’s Project Value from 3000 to 3200. | Sarah’s total becomes $5,700; Alex and Maya remain unchanged. | The rollup uses the intended Number property and Sum. |
| With the original values restored, replace Sarah with Alex in Brand refresh’s Client relation. | Sarah: $3,000. Alex: $4,500. Maya: $2,500. | The totals follow the related records, rather than a fixed manually entered amount. |
Important for the third test: replace the selected client; do not add Alex while leaving Sarah selected. This example assigns one client to each project. Restore Brand refresh to Sarah afterward and confirm the original totals again.
If a result differs, open the affected project and check its actual Client relation before changing the calculation. Use the rollup troubleshooting guide for calculation errors, or compare linked views and relations when a dashboard looks right but no records are connected.
3. Show the connected work where you actually need it
You do not need another Projects database inside every client page. Add a linked view of the existing Projects database and filter that view to the relevant client. The source records remain the same; the view simply changes what you see.
This is the difference between building more pages and building a system: one source of truth, several useful views.
Four mistakes that make connected databases harder than they need to be
1. Copying information instead of relating it.
If “Client name” exists as manually typed text in five databases, corrections will eventually disagree.
2. Using a Rollup before a Relation exists.
A Rollup needs a relationship to know where the information comes from.
3. Creating duplicate databases for different dashboards.
Usually you need another view of the same database, not another database.
4. Connecting everything because you can.
A relation should answer a useful operational question. If the connection changes no decision, view or workflow, it may not earn its place.
Try it: does your connection work?
Use the fictional records from this guide. Predict the result before making the change, then open the answer to check your reasoning.
Website redesign becomes $3,200. What should Sarah’s total be?
$5,700. The connected projects contribute $3,200 + $2,500. If the number stays at $5,500, check that you edited the same project, that Project Value is a Number property, and that the rollup uses Projects → Project Value → Sum. Restore $3,000 after the test.
A project has a client name in a text field, but its Client relation is empty. Is it connected?
No. Text names a person; the relation selects their database page. Choose the fictional client in the Client relation. Only the related projects contribute to the rollup through that relation.
You are done when the project opens its linked client and a small value change updates that client’s total. You can stop there; another database is not required.
Frequently asked questions
Do I need to copy the client into every project?
No. Select the existing client page in the Client relation. A text field containing the same name does not establish that connection.
Why does Clients need a Projects relation?
The client-side rollup needs a relation containing the project pages. Enable the corresponding Projects relation on Clients when setting up this two-way example.
Can a client have more than one project?
Yes. Allow multiple related pages in the client’s Projects relation. If each project has one client, its Client relation can be limited to one page.
Do I need a new database for each client dashboard?
Usually no. Add a linked view of the existing Projects source and filter it by client. Check source permissions before sharing; a filter alone does not restrict access.
If your total does not match, use the rollup troubleshooting checklist. For client-specific dashboards, follow linked views versus relations.
What this looks like in a working client system
A useful freelance setup can grow from the same principle:
The point is not to build the most complicated Notion workspace. It is to make one update carry its context everywhere it belongs.
If you would rather inspect a finished version before building your own, Freelancer CRM uses connected client-work databases as one operating system.