How to Share a Filtered Database View in Notion (2026)

Since 2025, Notion can share part of a database natively. On the Business and Enterprise plans, page-level access shows each person only the database pages they are tagged on. On Free and Plus workspaces, a filtered view still doesn't hide anything, so you need a workaround.

Take a marketing agency with one master database of articles for every client. Each client should see their own articles, not the others'. This guide covers the native method first, then seven workarounds, from a duplicate database to automations and external sync tools.

Is it Possible to Share a Part of a Notion Database?

Filters Hide Pages, They Don't Restrict Access

A filter only changes what a view displays. When you share a database or a filtered view of it, recipients can still reach every page in the database, regardless of the filters you applied.

Say your articles database has a "Client" property and a view filtered on Company A. If you share that view with Company A, they can remove the filter, switch views, or open the source database and read Company B's articles.

The only native way to restrict which pages someone can open is page-level access, available on Notion's Business and Enterprise plans. Everything else in this guide is a workaround.

Common Use Cases for Filtered Databases

Even with this limitation, sharing filtered databases is common across various scenarios:

1. Client-specific content sharing: Share only relevant articles with each client.
2. Project management: Share task lists filtered by project or department.
3. HR processes: Share employee databases filtered by department or role.
4. Product catalogs: Share product databases filtered by category or availability.
5. Event planning: Share attendee lists filtered by event or registration status.
6. Educational content: Teachers or course creators might want to share specific lesson plans or resources with different student groups.

These use cases show the need for workarounds to Notion's sharing limitations. Sharing filtered views would streamline workflows, enhance privacy, and improve the user experience for database owners and recipients.

Methods to Share a Filtered Database in Notion

Advantages and Disadvantages of Different Methods

Method	Advantages	Disadvantages
Page-level access (native)	- Real access control per page - One database, no syncing	- Business or Enterprise plan only - Clients can't add pages without a form
Create and Share Two Databases	- Full control over shared content - Easy to update	- Manual syncing required - Potential for data inconsistencies
Publish a locked database	- Simple to set up - Updates automatically	- Public to anyone with the link - Viewers can still open other views
Share Using "Can Edit Content"	- Maintains database structure - Allows controlled collaboration	- Clients can see every page - Risk of data export
Using Notion Automations	- Automatic updates - Customizable triggers and actions	- Limited to paid plans - Potential for sync delays
Creating a Make/n8n Automation	- Highly customizable - Works across platforms	- Requires technical setup - Potential costs for external services
Using External Sync Tools	- Purpose-built for database syncing - Often user-friendly	- Additional cost - Reliance on third-party services

Use Page-Level Access (Business and Enterprise Plans)

Page-level access is Notion's native answer to this problem. You add a rule to a Person or Created by property, and everyone in that property gets the access level you choose on that page only. The rule applies to every view of the database, including linked views.

How to Share Only Each Client's Pages

1. Add a Person property to the master database, for example "Client contact", and tag the client's account on their articles.
2. Open the source database, not a linked view of it, and click Share.
3. Under Page-level access, select Add a new rule.
4. Pick the "Client contact" property, choose an access level such as Can view or Can edit, and select Create rule.
5. Create a page called "Client A portal", type /linked, and choose Linked view of data source to add a view of the master database.
6. Share the portal page with the client, but not the master database.

The client now sees only the articles where they are tagged, through the linked view. If they open the database itself, they get an error message instead of the other clients' work.

Hide Internal Columns With Property Access

Since 2026, Business and Enterprise workspaces can also restrict columns. Open the original database in a table view, open a column's menu, and select Property access. You can then hide internal columns like budget, rates, or private notes from clients, while your team keeps full access.

A database can have up to 20 properties with access rules. People with full access to the database always see every column, so test with a client account before sharing.

Limits of Page-Level Access

• Plan: it requires the Business plan, listed at $20 per seat/month, or Enterprise.
• New pages: clients who only have page-level access can't create pages in the database. Use a form, or the Can create permission, which lets people add entries without seeing other people's.
• Setup: rules live on the source database, so each client needs to be tagged on every page they should see.

If your workspace is on the Free or Plus plan, use one of the workarounds below.

Create and Share Two Databases

Duplicate the Master Database

The first step is to create a duplicate of the master article database. This new database will serve as the client-facing version. Here's how to do it:

1. Open the master database in Notion.

2. Click the three dots (...) in the top right corner.

3. Select "Duplicate."

   

4. Select if you prefer to duplicate with or without the items

Share the Public Database

Once the client-facing database is created, share it with clients:

1. Open the public database.

2. Click "Share" in the top right corner.

3. Choose the appropriate sharing settings:

   • Open the Publish tab to publish it as a Notion Site.
   • Invite specific people by email.

4. Set permissions (e.g., "Can view" or "Can comment").

5. Copy the generated link.

You can now send this link to clients, giving them access to a curated version of the article database.

Tips: Creating a "Sync" Page for Easy Updates

To streamline updates, create a "Sync" page:

1. Create a new page in Notion called "Article Sync."

2. Add two linked views to this page (type /linked, then choose Linked view of data source):

   • The original master database.
   • The client-facing "Client Articles" database.

3. For the master database view, create a filter like: "Ready for Client" is "Yes.", or "Client = Client A"

This setup allows for easy drag-and-drop updating. When a new article is ready for a client:

1. Navigate to the "Article Sync" page.
2. Find the new article in the master database view.
3. Drag it to the client database.
4. The article will now appear in the client's shared view.

By using this method, you can maintain a clear separation between internal and client-facing content. This system, while manual, offers complete control over what information is shared with clients.

If you want to keep the items in both databases, hold Alt while drag-and-drop. It will allow items to be copy-pasted, and not cut-pasted.

Publish a Locked Database

Difference Between Filters and Advanced Filters

Understanding the distinction between regular filters and advanced filters is crucial when publishing a locked database.

Regular filters:

• Visible to anyone with access to the database.
• Easily modified by users.
• Ideal for personal use or within a trusted team.

Advanced filters:

• Hidden from view in shared pages.
• Cannot be altered by viewers.
• Perfect for creating locked, curated views for clients.

Using advanced filters ensures that clients only see their relevant articles without being able to modify the filter settings.

Removing the Breadcrumbs

Sharing Notion databases comes with the challenge of breadcrumb navigation, which can expose the original database structure. Here's a workaround:

1. In the master database, create a new view with an advanced filter.

2. Set the filter to hide all entries (e.g., "Name" is empty).

   

3. Remove all other views from this database.

Now, even if a client clicks on the breadcrumb, they'll see an empty database, protecting fully your content.

To implement this for client sharing:

1. Create a new page titled "Client Articles."
2. Add a linked database to this page, connecting to the master database.
3. Apply an advanced filter to show only the specific client's articles.
4. Lock the database view.
5. Publish this page from Share → Publish, or share it with the client as Can view.

This method allows you to share a filtered, locked view of articles with each client. Clients can browse their assigned content without accessing or even knowing about the existence of other clients' articles.

For your internal use:

1. Create another linked database of the master database.
2. Remove the "hide all entries" filter.
3. This serves as the functional view of all articles, accessible only by you and your team.

By using this approach, you can maintain a single source of truth in the master database while providing secure, client-specific views of relevant content.

Share Using the "Can Edit Content" Option

Explanation of the "Can Edit Content" Permission

The "Can edit content" permission in Notion offers a balance between full access and view-only rights. This option allows clients to interact with their specific content without giving them control over the entire database structure.

Key features of "Can edit content":

• Users can create, edit, and delete pages within the database.
• Property values can be modified.
• Database properties, views, filters, and sorts remain locked.

How to Set It Up

1. Open the master article database.
2. Click "Share" in the top right corner.
3. Enter the client's email.
4. In the dropdown menu, choose "Can edit content".
5. Optional: add a personal message explaining the access level.
6. Click "Invite".

Best Practices for Maintaining Data Integrity

"Can edit content" offers control but requires careful management. To maintain data integrity:

1. Use property locking: Lock crucial properties like "Client" to prevent accidental changes.
2. Create backup views: Maintain a separate, admin-only view of the database.
3. Implement regular audits: Periodically review client-editable content for accuracy.
4. Provide clear guidelines: Explain to clients what they can and should edit.

Scenarios Where This Option Is Most Effective

The "Can edit content" option works well in situations like:

1. Collaborative content calendars: Clients can update article statuses or add comments without altering the overall structure.
2. Feedback collection: Clients can directly input their thoughts on articles in designated properties.
3. Project tracking: Allows clients to update progress or add notes to their specific projects.
4. Resource libraries: Clients can add their own resources to a shared knowledge base.

This method allows for a more interactive client experience. For instance, clients could mark articles as "Approved" or "Needs Revision" directly in the database, streamlining the feedback process.

This permission protects the database structure, not its content. Clients with "Can edit content" can still open every page, so combine it with page-level access if you are on the Business plan.

Using Notion Automations

Overview of Built-in Notion Automation Features

The Notion automations enable dynamic updates and notifications based on changes in the database.

Key automation capabilities:

• Trigger actions based on property changes.
• Automatically update related databases.
• Send notifications to team members or clients.
• Create new pages or items in other databases.

How to Set Up Automations to Keep Databases in Sync

Here's how to create an automation to sync the master database with a client-specific one:

1. In the master database, click ⚡ at the top of the database.

2. Select New automation.

3. Choose a trigger on a property change.

4. Set the property to "Client" and specify the client's name.

   

5. Add the action Add page to.

6. Select the client-specific database as the target.

7. Map the relevant properties from the master to the client database.

8. Save the automation.

Now, whenever an article in the master database is assigned to a specific client, it will automatically appear in their dedicated database.

Use Cases for Automatic Database Updates

1. Content approval workflow: Automatically move approved articles to the client database.
2. Deadline notifications: Send alerts to the team when article due dates approach.
3. Client feedback integration: Update article status in the master database based on client input.
4. Cross-database tagging: Automatically tag articles in the client database based on categories in the master.
5. Ready-for-client flag: copy an article to the client database when a "Ready" checkbox is checked.

Using Notion's built-in automations can significantly streamline the process of sharing filtered content with clients.

Free plan users can only create Slack notification automations. Other database automations need a paid plan, starting with Plus at $10 per seat/month. Automations also skip pages whose access is restricted, so check the share settings of the client database.

By leveraging these automations effectively, the agency can maintain a single source of truth in the master database. This ensures each client has access to their relevant, up-to-date content without manual intervention.

Creating a Make/n8n Automation

Step-by-Step Instructions to Create Automations (1-way Sync)

Seeking advanced automation options, platforms like Make (formerly Integromat) or n8n offer powerful solutions. Here's how to set up a 1-way sync using Make:

1. Create a new scenario in Make.
2. Add a Notion module as the trigger: "Watch Database Items."
3. Configure it to monitor the master article database.
4. Set up filters to only process items for a specific client.
5. Add another Notion module: "Create a Database Item."
6. Configure this to add items to the client-specific database.
7. Map the relevant fields from the master to the client database.
8. Set up error handling and notifications.
9. Schedule the scenario to run at regular intervals (e.g., every 15 minutes).

This setup ensures that new or updated articles for a specific client are automatically synced to their dedicated database.

2-Way Sync

For a more robust solution, implement a 2-way sync:

1. Create two separate scenarios in Make.

2. Scenario 1: Master to Client (as described above).

3. Scenario 2: Client to Master

   • Trigger: Watch the client database for changes.
   • Action: Update the corresponding item in the master database.

4. Add filters to prevent infinite loops:

   • Only sync items where "Last edited by" is not the automation tool.
   • Use a "User Update?" formula property to distinguish manual edits.

This 2-way sync allows clients to make changes (e.g., add feedback) that reflect back in the master database, while still maintaining overall control.

Key Considerations for 2-Way Sync:

• Carefully manage permissions to prevent unintended edits.
• Implement conflict resolution strategies for simultaneous edits.
• Regularly audit sync logs to catch and resolve any discrepancies.

By leveraging external automation tools, our marketing agency can create a more flexible and powerful syncing system, tailored precisely to their workflow needs. This approach requires more technical setup but offers greater customization than Notion's built-in features.

Using External Sync Tools

For our marketing agency owner, several third-party tools address Notion's database sharing limitations:

1. Notion2sheets: Syncs Notion databases with Google Sheets.
2. Whalesync: Offers real-time, two-way sync between Notion and other platforms.
3. Unito: Provides bi-directional sync between Notion and various project management tools.
4. Coupler.io: Automates data transfers between Notion and other apps.
5. ShareBridge: Shares filtered views of a Notion database through a public link, with control over which fields are visible.

These tools are designed to handle the complexities of database synchronization and often provide more robust features than general-purpose automation platforms.

Just Use Airtable

Why Consider Airtable Over Notion

While Notion offers a versatile workspace, Airtable provides superior database functionality that might better suit their needs:

1. Native filtered views: Airtable allows sharing specific views without exposing the entire base.
2. Granular permissions: Control access at the table, view, and field level.
3. Robust API: Easier integration with other tools and custom solutions.
4. Advanced automations: More powerful built-in automation capabilities.

Setting Up a Client-Friendly System in Airtable

1. Create a base for all client articles.
2. Set up tables for different content types (e.g., blog posts, social media).
3. Use views to filter content by client.
4. Implement automations for content workflow (e.g., status updates, notifications).
5. Share filtered views with clients using view-specific share links.

Migrating from Notion to Airtable

1. Export the Notion database as CSV.
2. Import CSV into Airtable, mapping fields appropriately.
3. Set up views and permissions to mirror the Notion structure.
4. Create forms for client input if necessary.
5. Update internal processes and client communication.

Pros and Cons of Switching to Airtable

Pros:

• Better suited for complex database needs.
• More intuitive sharing of filtered data.
• Robust integration capabilities.

Cons:

• Less all-in-one than Notion (e.g., no built-in wiki functionality).
• Potential learning curve for team members.
• May require restructuring existing workflows.

While Airtable addresses many sharing challenges with Notion, it's important to weigh the benefits against potential disruptions.

Sharing filtered Notion databases presents unique challenges, but creative solutions are available.

If your workspace is on the Business plan, start with page-level access and property access: one database, real permissions, and no syncing. On Free or Plus, a duplicate database or an automation is the most reliable way to keep client data separate.