> ## Content Index
> Fetch the complete content index at: https://notionsolutions.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# Why Every New Notion Task Links to the Same Client
- URL: https://notionsolutions.net/notion-template-same-relation/
- Published: 2026-10-30T10:17:01.000Z
- Updated: 2026-10-30T10:17:03.000Z
- Description: A client selected inside a database template becomes a starting value for every task made with it. Find that value, decide whether it is intentional, and check existing tasks separately.
- Author: Kevin Turner
- Tags: fix, client-work

When every new Notion task links to the same client or project, inspect the **Relation value inside the database template** used to create it. Notion warns that [a prefilled template relation links every new page to the same existing page or pages](https://www.notion.com/help/database-templates?ref=notionsolutions.net). A general task template should leave that choice empty; a template reserved for one client can keep it.

I would find the saved value before rebuilding the relation. The connection between your Tasks and Clients databases may be correct. The mistake can be a particular client selected in the template, ready to be copied into every new task.

## Find the template that supplied the client

1. **Open an affected task.** Note the page selected in its Client or Project relation. Open the linked page if you need to distinguish clients or projects with similar names.
2. **Identify how the task was created.** Was a template chosen from New, was the task created by a button, or did it appear on a repeating schedule? Check the template used by that route.
3. **Open the database's template menu.** Use the dropdown beside **New** or **+**, find the relevant template, select **••• → Edit**, and inspect its Client or Project relation.

Notion's [template editing instructions](https://www.notion.com/help/database-templates?ref=notionsolutions.net) also describe the bar at the top of the editor that identifies the database. Check that you are editing the template for the affected task database, especially if your workspace has several similarly named trackers.

A relation value is a link to an actual database page. Notion's [relation documentation explains how to open those linked pages](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net). Sample client text in a task brief is a separate thing: inspect the property field, not just the template's title or example wording. If multiple templates exist, finding the fixed value in one does not prove the others use it.

## Keep a deliberate fixed client; clear an accidental one

Choose based on what the template is meant to create:

- **A task for any client:** clear the selected page or pages from the template's relation value. Leave the Relation property available so the creator can choose the correct client on the new task.
- **A task always belonging to one client:** keep the fixed relation and give the template a client-specific name. For example, “Acme monthly report” communicates a narrower purpose than “New task.”

To clear the value, open the relation field and use the [minus control beside the selected related page](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net). Remove the selected link rather than deleting the Relation property. Preserve the template's useful checklist, brief, status, and other defaults.

[![The New task template’s Client relation removes Acme with the minus control while keeping the Client property.](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/template-clear-relation-controls.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/template-clear-relation-controls.webp?ref=notionsolutions.net)

Remove the selected client in the template; keep the relation field for the next task’s correct client.

In an educational example, the **Tasks** database has two templates:

| Template            | Purpose                       | Saved Client value           |
| ------------------- | ----------------------------- | ---------------------------- |
| New task            | Work for any client           | Empty after correction       |
| Acme monthly report | Work always belonging to Acme | Acme, intentionally retained |

Both use the same Client relation connected to the Clients database. Clearing Acme from New task changes a starting value; it does not mean removing the Client field or disconnecting the two databases. The second template is useful precisely because its fixed client is deliberate.

If the wrong client arrives on a schedule, inspect the repeating template too. Notion's [repeating templates create copies of the saved template](https://www.notion.com/help/database-templates?ref=notionsolutions.net), so the same fixed-relation warning matters there. A manually chosen general template and a scheduled client-specific template can serve different purposes.

## Check the next task and review old ones separately

Where it is safe to create a noncritical task, choose the edited template from the New menu and inspect the new task's relation. A general template with no saved client should leave its client relation empty; a client-specific template should contain the intended fixed page.

Check existing page-creation automations before adding that sample. Notion documents a [Page added trigger for database automations](https://www.notion.com/help/database-automations?ref=notionsolutions.net), so use a place where the check will not send client messages or change other records.

For that example, create a noncritical page from **New task** only where no other creation action writes the Client field. Inspect Client before choosing a page. If it is empty, select the intended client for this particular task. Then compare an older task that wrongly contains Acme. It still needs its own assignment decision; changing the template is not a cleanup operation on that page.

[![An empty Client default applies to Sample task, while an existing Review brief still needs its Acme assignment checked separately.](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/template-new-versus-existing-example.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/template-new-versus-existing-example.webp?ref=notionsolutions.net)

Fix the template for future pages, then review existing tasks against their actual client or project.

Review tasks already linked to the wrong client separately. Compare each task with its brief or confirmed project, then change only the mistaken relation. Keep a record of the old and intended links before a substantial cleanup; creation date alone is a poor basis for assigning a client.

For one confirmed mistaken task, open its Client relation, hover over the wrong selected client, and use **–** to remove that link. Search for and choose the correct existing client page in the relation menu, following Notion's [related-page selection and removal controls](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#view-and-remove-related-pages). Reopen the selected page to verify its identity. If the relation permits multiple pages, inspect every selected client; adding the correct one while leaving the wrong one would not complete the repair.

Be careful with shared tracking. In a two-way relation, [edits also appear in the related database](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net), and rollups calculate from related pages. Check the affected client or project in your [project tracker](https://notionsolutions.net/notion-client-project-tracker-template/) after correcting task links.

## If the template is empty, trace the other setting

An empty template relation rules out that particular saved value. It does not explain every route by which a task can receive a client.

**For a page button:** hover over the button and select **⚙️**, then inspect its **Add page to** action and any template it uses. The action can set properties on the page it creates. Notion also says [template values can overwrite values set by a button](https://www.notion.com/help/buttons?ref=notionsolutions.net), so check both before deciding which setting needs correction.

**For a database automation:** have a workspace member on a paid plan with Full access to the database open its **⚡** menu and inspect actions that create or edit the task. The [Edit property action can add or remove relation values](https://www.notion.com/help/database-automations?ref=notionsolutions.net). A relation that changes through an action needs an action-level correction; clearing an unrelated template will not address it. The distinction between [buttons and database automations](https://notionsolutions.net/notion-buttons-vs-automations/) helps identify the creation or change route.

**If the actual task relation is correct:** inspect the view that makes the tasks look wrong. A [database view filter selects entries by property values](https://www.notion.com/help/views-filters-and-sorts?ref=notionsolutions.net). Open that view's settings and inspect **Filter**; a condition fixed to one client may be why only that client's tasks appear. Diagnose the selected relation on the task and the display filter separately before changing either.