Pages

Here is a test topic from dogman. It is synced from Dogman’s member page, so I don’t think anyone can delete it but dogman or an admin. Is this correct? ## Account Permissions - Configure permissions for all personal pages so that all other community members can comment on each other’s writing, but nobody can edit their page. - It is possible to downgrade my permission on this site and make it so I don’t have access. This might be helpful for some future use cases, but for now, it’s all on my Notion account, and I think it wouldn’t be good to let other people post on my Notion account without me having the ability to change it. - Dan has account permissions to write in someone’s synced note page because he is the admin. Everyone else can’t write in dogman’s synced post. This is the default setting and can be configured in any other way. ## Notion Database Property Viewing Settings ### Customize All Pages - It is possible to customize the view of properties for all pages. ### Property Visibility - You can change the Property Visibility to Always show, hide when empty, or always hide. - When you hide it, you can find it in the little arrow at the bottom. ### Show On Page Feature - It’s possible to make other properties show up below the top properties. This could be very helpful. ## Seeing Authorship Ideally, I think we’d be able to see who wrote what. Currently, I’m not sure if this is possible. - Check the page analytics and history features to see if it shows who made each change. - Consider: I think it is possible to do this with a more structured Notion page. We could set up buttons to add new entries to a database(s). The button can include the author as whoever clicked the button. - Here’s how it looks in synced blocks details.

Account permissions can be configured to allow community members to comment without editing personal pages. Admins have the ability to write in synced notes, while property visibility settings can be customized for all pages. There is a need to explore authorship visibility and consider structured setups for tracking changes and authors in a community database.