You update a task on a dashboard, then find the same change in the original database. That is expected when the dashboard uses a linked view of the same source.
The important question is what you edited: a record, the source structure or the way this view displays information.
What you will check
A small reversible test will distinguish a shared record edit from a local view change. Use a fictional task so the check does not change real project work.
1. Identify the source before editing
Open the linked database’s settings and inspect its data sources. Current Notion interfaces offer Manage data sources; a linked source is identified there. Open its original database and confirm which task source you are using.
Names alone are insufficient when several databases are called Tasks. Check that the same fictional task page is accessible from both places.
If you are unsure whether you need a relation or a linked view, read linked database versus relation.
2. Separate record changes from view settings
| Action | What changes |
|---|---|
| Edit a task title, date or status | The shared task record |
| Edit the task page body | The shared page content |
| Change a source property definition | The shared source structure |
| Change a linked view filter or sort | This view’s display settings |
| Hide a property in this view | Its visibility here; the property still exists |
Notion’s data source documentation distinguishes shared source edits from linked view settings. Hiding a column and deleting the property are different actions.
3. Test a shared record edit
- Create a fictional task called Linked view test in your existing task source.
- Use an unfiltered linked Table view to locate it.
- Open that task and rename it Linked view test — checked.
- Open the original source and locate the same page.
- Confirm that its title has also changed.
- Restore the title to Linked view test.
One page has been edited from two entry points. You do not need a second task or a manual sync step.
4. Test a view change separately
In the linked view, add a filter that selects your fictional task by its title. Confirm that the linked view now shows that task.
Open an existing unfiltered view in the original database. Its own filter settings should remain as they were. Remove the temporary linked filter afterward.
The test concerns distinct views. If you open the very same view through a direct link, you are inspecting that view, not creating an independent display.
For more complex criteria, use the AND and OR filter guide.
5. Check the right thing when a record disappears
Suppose your dashboard shows only unchecked tasks. Checking Done makes a task leave that view, while the original record remains.
Search the source before rebuilding the task. Check completion, project, date and other view criteria. The task visibility guide gives a step-by-step diagnosis.
Deleting a task page through the linked database acts on the shared record. It is not a way to hide that page from just one dashboard.
6. Choose shared information deliberately
If two dashboards should display different selections of the same work, keep the source and use different views.
If you need a separate record with its own independent history, that is a different data design. Define who maintains it and how it relates to the original before introducing another copy.
7. Review access separately from appearance
Linked sources respect access to their original source. A person who receives a dashboard may still lack permission to see its database content.
Conversely, a filter should not be treated as a rule that restricts someone to the displayed records. Check the actual source and page permissions before sharing a client dashboard.
Use a view to focus attention. Use the workspace’s permission controls to manage access.
If the same task appears on two dashboards, use the record identity checklist before treating it as an accidental duplicate.
Common mistakes
- Expecting independent task values: a linked view reads the same record.
- Deleting a property to hide a column: use view visibility settings instead.
- Recreating a filtered-out task: inspect the source first.
- Sharing before checking source access: a visible dashboard shell does not establish database access.
Frequently asked questions
Why did a dashboard edit change my original task?
The linked view displays the same task record. Editing that record updates it in the original source too.
Does a linked view filter change the original view’s filter?
No. Filters and other view settings belong to their respective views.
Can I hide a property without deleting it?
Yes. Adjust that view’s property visibility rather than deleting the shared source property.
Does deleting a task from a linked database only remove it from that dashboard?
No. Deleting the task page acts on the shared record. Use a filter when your goal is to exclude it from one view.
Why can’t a guest see my linked database?
Check whether the guest has access to the original source. Sharing the containing page alone may not provide that access.
Explore the wider workflow
You can build this with your existing databases. If you also need a workspace for clients and projects, explore Freelancer CRM and compare its structure with your workflow.