Fix Notion Rollup Cannot Show Property: Permission Inheritance Issue

You created a rollup property in a Notion database but the target property field is grayed out or missing from the dropdown. This usually happens when the database you are rolling up from does not have permission to read the source database where the property lives. The root cause is a broken permission chain between the two databases. This article explains why the rollup cannot see the property and provides step-by-step fixes to restore the permission inheritance.

Why a Rollup Property Cannot Show a Target Property

A rollup property in Notion works by reading data from a related database through an existing relation property. The relation property connects two databases. The rollup then pulls a specific property value from the related database. For this to work, the database that contains the relation property must have permission to read the database that holds the target property.

Notion uses a permission inheritance model. When you create a relation between databases, the database that initiates the relation inherits read access to the target database. However, this inheritance breaks if the target database is shared with specific individuals or groups instead of the entire workspace. If the relation database cannot see the target database, the rollup property will show an empty dropdown or a grayed-out property list.

Permission Inheritance in Detail

Every database in Notion has a sharing setting. The default setting is “Workspace members can view, comment, or edit.” When a database uses this default, any other database in the same workspace can create a relation to it and roll up its properties. Problems occur when a database is shared with specific people only. In that case, the relation database must also be shared with those same people, or the rollup will fail silently.

Rollup Property Configuration

A rollup property requires two prior properties in the same database: a relation property pointing to another database, and a target property in that other database. The rollup property then selects the target property from a dropdown. If the target property does not appear, the permission chain is broken. The rollup cannot even see the database structure, let alone its properties.

Steps to Fix the Permission Inheritance Issue

Follow these steps in order. Each step addresses a specific permission layer. Test the rollup after each step to see if the property appears.

1. Open the sharing settings of the target database
   Navigate to the database that contains the property you want to roll up. Click the three-dot menu in the top-right corner of the database page. Select “Add connections.” Then click the “Share” tab. Verify that the database is shared with the entire workspace or with the specific user who owns the relation database. If it is shared with “Specific people,” add the user or group that has access to the relation database.
2. Check the relation database sharing settings
   Go to the database that contains the relation property. Open its sharing settings the same way. Ensure this database is also shared with the same people or the entire workspace. Both databases must have overlapping permission groups. If one database is shared with “Workspace members” and the other with “Specific people,” the rollup will fail.
3. Inspect page-level permissions in the source database
   Open the source database (the one with the target property). Click the three-dot menu on any page within that database. Select “Add connections” and then “Manage permissions.” Look for individual pages that have “Private” or “Limited access” settings. If a page is set to private, the rollup cannot read its properties even if the database is shared. Change the page permission to “Full access” or share it with the relation database owner.
4. Remove and re-add the relation property
   If permission settings are correct but the rollup still shows no properties, delete the relation property from the database. Recreate the relation by selecting the same target database. This forces Notion to re-negotiate the permission handshake. After recreating the relation, open the rollup property and check if the target property appears.
5. Duplicate the target database as a test
   Create a duplicate of the target database by clicking the three-dot menu on the database name and selecting “Duplicate.” Place the duplicate in the same workspace. Create a new relation from your original database to this duplicate. If the rollup can now see the properties, the original target database has a permission conflict that cannot be resolved by sharing alone. Consider using the duplicate as the new source database.

If Notion Still Cannot Show the Rollup Property

Rollup dropdown is completely empty

An empty dropdown means the rollup cannot detect any relation property. This happens when the relation property itself is missing or incorrectly configured. Open the database properties and verify that a relation property exists and is linked to a valid database. If the relation property is linked to a deleted database, the rollup will have nothing to read. Delete the broken relation and create a new one.

Rollup shows only one property that is not the one you need

The rollup property dropdown may show only a single property, usually the title property of the target database. This indicates that the relation database has read access to the target database but not to its full property list. The target database may have column-level permissions enabled. Notion does not officially support column-level permissions, but if the target database is a template or a locked board, some properties may be hidden. Unlock the target database by going to its three-dot menu and selecting “Unlock database.” Then refresh the rollup property.

Rollup works for some pages but not others

If the rollup property displays values for some pages and appears blank for others, the issue is page-level permissions in the source database. Open the source database and sort by the “Last edited” column. Look for pages that have a lock icon in the sharing column. These pages are set to private. Change their sharing settings to “Full access” or share them with the relation database owner. Batch-select multiple pages and use the “Share” option to apply the same permission to all at once.

Notion Rollup Permission Requirements: Workspace vs Specific Sharing

Item	Workspace Sharing	Specific People Sharing
Default setting	All workspace members can view	Only invited people can view
Relation creation	Any database in the workspace can relate	Only databases shared with the same people can relate
Rollup property visibility	All properties visible	Only properties from shared pages are visible
Permission inheritance	Automatic for all members	Requires manual sharing of both databases
Common failure	Rare, unless page is private	Frequent when people groups do not match

If you use specific people sharing, make sure the same people are added to both databases. You can create a group in Notion by going to Settings & Members > Members > Groups and adding users to a group. Then share both databases with that group. This ensures the permission inheritance works for the rollup property.

You can now diagnose and fix a rollup property that cannot show a target property by checking workspace sharing, page-level permissions, and relation integrity. Start by verifying that both databases are shared with the same group or the entire workspace. If the problem persists, duplicate the target database to isolate the permission conflict. For advanced setups, use groups to manage access to multiple databases and avoid per-page permission mismatches.