How to Use Notion Relation Property With Filter for Current User

Notion databases let you link records across tables using a relation property. When you filter a relation by the current user, you can show only items assigned to or linked to the person viewing the page. This is useful for personal task lists, project dashboards, and team views where each member sees their own data. This article explains how to set up a relation property and apply a filter that dynamically shows only records associated with the current user.

What the Relation Property and Current User Filter Do

A relation property in Notion connects two databases. For example, you might have a Tasks database and a Projects database. Each task can be linked to one or more projects. This creates a bidirectional link that you can display in either database.

The current user filter works with a Person property. A Person property stores one or more Notion user accounts. When you apply a filter condition that checks if a Person property equals the current user, Notion automatically changes the displayed records based on who is signed in. This is not a static filter. It updates every time a different user views the page.

To use this feature, you need at least two databases. One database holds the records you want to filter (for example, Tasks). The other database holds the related records (for example, Projects). The Tasks database must include a Person property that stores the assignee. The relation property links each task to a project. You then create a linked database view on a dashboard page and filter it so only tasks assigned to the current user appear.

Prerequisites

You need edit access to the workspace. You must have at least two databases with a relation already established between them. The database that contains the records you want to filter must include a Person property. This Person property should be populated with the user accounts that should see those records.

Steps to Set Up a Relation Property With a Current User Filter

1. Create the Person property in the target database
   Open the database that holds the records you want to filter. For instance, open your Tasks database. Click the + icon in the last column header. Select “Person” from the property type list. Name the property “Assignee” or “Owner.” In each row, click the Person cell and select the user from the list. You can assign multiple users, but the filter will match any user who is currently viewing.
2. Create the relation between two databases
   If you already have a relation, skip this step. Otherwise, open the Tasks database. Click the + icon in the last column header. Select “Relation” from the property type list. Choose the related database (for example, Projects). Click “Create relation.” A relation column appears in both databases. You can link a task to one or more projects by clicking the relation cell and selecting the project record.
3. Create a linked database view on a dashboard page
   Navigate to the page where you want the filtered view. Type /linked and select “Linked view of database.” Choose the Tasks database. Notion inserts a database block that shows all tasks. You can change the view type (Table, Board, Gallery, etc.) using the view dropdown at the top left of the database block.
4. Add a filter for the current user
   Click the filter icon (funnel) in the top right of the database block. Click “Add a filter.” In the filter row, click the property dropdown and select “Assignee” (or whatever you named your Person property). Click the condition dropdown and select “Is.” Click the value dropdown and scroll down. You will see “Current user” at the bottom of the list. Select “Current user.” The database now shows only records where the Assignee property matches the signed-in user.
5. Test the filter with another user account
   Sign out of Notion and sign in with a different user account that has at least one task assigned to it. Navigate to the same dashboard page. The linked database view should now show only tasks assigned to that user. If you see no records, verify that the Person property is set correctly and that the user has at least one assigned record.

If the Current User Filter Does Not Work as Expected

Filter option “Current user” does not appear in the dropdown

The “Current user” option only appears when you filter a Person property. The property must be of type “Person,” not “Text” or “Select.” If you created a text property and typed a name manually, Notion cannot recognize the user account. Delete that property and create a new Person property. Then assign users by clicking the cell and selecting from the list of workspace members.

Linked database view shows all records instead of filtered ones

This usually happens when the filter is applied to the original database but not to the linked view. Filters on a linked database view are independent of filters in the source database. Click the filter icon on the linked view block and confirm that a filter row with “Assignee” and “Current user” exists. If the filter is missing, add it again. Also check that no other filter is overriding it. For example, a filter that says “Status is Done” combined with “Assignee is Current user” works together, but if you also have a filter that says “Project is empty,” that could exclude all records.

The filter works for one user but not for another

Ensure both users have records assigned to them in the Person property. If User A is assigned to Task 1 and Task 2, but User B has no tasks assigned, User B will see an empty database. Also confirm that both users have at least Can View access to the page containing the linked database view. If a user cannot see the page, they cannot see the filtered data.

Relation Property With Current User Filter vs Manual Filter

Item	Relation Property With Current User Filter	Manual Filter by User Name
Setup effort	Requires a Person property and a relation	Requires only a text property with user names typed in
Dynamic behavior	Changes automatically for each viewer	Stays fixed on the name you typed
User recognition	Uses Notion account identity	Matches text only, no account check
Maintenance	None; works for new users if they have records assigned	Must update text values when users change
Best use case	Team dashboards, personal task lists, project overviews	Static reports where viewer identity does not change

You can now build a dynamic dashboard that shows each team member their own tasks or projects automatically. To extend this, add a second filter for a date property so users see only current or upcoming items. Another advanced tip: combine the current user filter with a rollup property that summarizes related data, such as the total number of tasks per project, while still restricting the view to the current user.