Issue Summary

Whenever importing Notion data into Confluence, all Notion Database elements (inline or full page) automatically become Restricted VIEW/EDIT exclusively to the user who performed the Import action.

This happens despite the source element having no restrictions applied to it on the Notion side. This happens regardless of whether access mapping is used during the import.

It can be a problem when importing huge sets of databases, as it requires manually removing the restrictions from each of the new content imported in CC. 

Steps to Reproduce

1. Export any Notion subset of pages containing Databases (inline or full page)
2. Import into Confluence and check the "Share" option on any database created for restrictions

Expected Results

Only restricted content from Notion becomes restricted in Confluence (and only if using the access mapping). Otherwise, the imported content is available to every use with Space permissions to the destination space.

Actual Results

Regardless of the access assigned to the Database on the Notion side, it gets created as Restricted content on the Confluence side, only available to the user who performed the import.

Workaround

For the moment, the only workaround available is manually removing the Restrictions from newly imported Databases in Confluence Cloud.