One project should belong to one client, while that client can have several projects. Both use relations, but the two sides do not need the same selection limit.
This guide helps you choose a limit that describes your workflow, without treating every connection as interchangeable.
Start with one sentence
Before changing a property, complete this sentence: Each record here can connect to how many records there?
| Property | Workflow rule | Suitable limit |
|---|---|---|
| Projects → Client | Each project has one client | 1 page |
| Clients → Projects | Each client may have several projects | No limit |
| Tasks → Project | Each task belongs to one project | 1 page |
| Projects → Tasks | Each project may have several tasks | No limit |
If your work genuinely allows several clients on one project, the first rule needs revising. Choose the rule before the setting.
1. Inspect the actual relation
Open the property’s settings and confirm its related source. A select field containing project names has no relation selection limit.
If you still need the connection, follow how to connect two databases. Reuse an existing relation that already serves the purpose.
2. Locate the page limit
In the relation settings, inspect the limit option. Notion supports 1 page and No limit, as described in its relation documentation.
Choose 1 page when that record should have at most one related page in this property. Choose No limit when several selections are meaningful.
A one-page limit does not mean the field must be filled. You still need a separate process to review empty assignments.
3. Check the other direction separately
If your relation has a corresponding property, inspect that side too. Projects → Client and Clients → Projects describe different questions.
Under the example rule, one client can appear on many project records, and the client’s Projects property needs to accommodate those projects. A one-page selection on the project side is not a rule that every client may have only one project.
Use the two-way relation guide to identify the paired properties before changing them.
4. Review existing connections before narrowing a limit
If a property currently allows several pages, inspect its existing values before switching to 1 page. Do not rely on a limit change to decide which association should survive.
- Create an unfiltered Table view of the source.
- Show the relation property.
- Review records with several selected pages.
- Confirm which associations are intentional from the record context.
- Resolve conflicting assignments before applying the narrower rule.
For a large database, use a deliberate audit process rather than assuming a quick visible sample represents every record.
5. Test with fictional records
Create two fictional clients, Oak Studio and Cedar Studio, and one test project. After setting the project’s Client relation to 1 page, select Oak Studio and inspect the stored value.
Then attempt to choose Cedar Studio. Check the final stored selection rather than assuming the interface retained both. Confirm that the property holds at most one selected client.
Restore the intended test assignment. In the corresponding client property, verify that a second fictional project can also link to Oak Studio when that side permits several projects.
6. Keep missing assignments visible
A selection limit controls how many related pages the property can hold; it does not establish that the chosen page is correct.
Maintain an empty-relation review using the projects without a client guide. Check identity when similar client names make a selection ambiguous.
Common mistakes
- Applying the same limit to both ends without reading their meaning.
- Using No limit only because the intended rule is undecided.
- Assuming 1 page makes a relation required.
- Narrowing the setting before reviewing existing multiple associations.
Frequently asked questions
Does 1 page make a relation required?
No. It limits selections to at most one related page. Empty assignments still need review.
Can one client still have several projects?
Yes, under this model. Check that the client’s corresponding Projects property permits several related projects.
When should I choose No limit?
Use it when several related pages are meaningful for each record in that property.
Does the limit verify that I selected the correct client?
No. Confirm the identity of the selected page separately.
Should I change a populated relation straight to 1 page?
Review existing records with several associations first and resolve their intended assignments before narrowing the rule.
Explore the wider workflow
You can make these changes in your existing workspace. For a broader client and project workflow, explore Freelancer CRM and compare its structure with your needs.