We’ve prepared an email template to help improve our Notion integration. By sending this email to Notion, you'll nudge them to enhance their API, leading to a better experience for all Dust users.

Here's how you can help:

1. Copy the email template below.
2. Fill in your Notion pages' details where indicated.
3. Send it to Notion support.

This small step is a big move towards making our Dust-Notion integration smoother.

Thank you for your support!

To: [team@makenotion.com](<mailto:team@makenotion.com>)
Subject: Read permissions incorrectly propagated to children's pages

Dear Notion,

We'd like to report a critical issue with the way read permissions are propagated from top-pages to children pages in Notion when using Notion apps.

We authorized the following top-level page through the OAuth flow of the Notion Dust app[0]:

{URL_OF_TOP_LEVEL_PAGE}

It was later on discovered that the following page (children of the page above) was not accessible to the app:

{URL_OF_THE_CHIDREN_PAGE_WITH_NO_ACCESS}

We had to manually add this page to the connection in the Notion UI which is as far as we understand not expected.

We would like to understand in particular:
- the underlying issue and why read permissions are not properly propagated down the page/database tree?
- whether we should expect this issue to affect other pages?

Thank you! 

[0]
{
  object: 'user',
  id: 'cb19e2ab-e7dd-4a7c-9f9c-9078aafea22c',
  name: 'Dust',
  avatar_url: '<https://s3-us-west-2.amazonaws.com/public.notion-static.com/9d7b8b11-5b77-4e4d-813b-f3fb595d49fa/AppIcon.png>',
  type: 'bot',
  ...
}