Does Notion's 'Share to web' feature expose page history to public visitors?
0 reputation · 29 Jan 2020, 00:45 UTC
0 reputation · 29 Jan 2020, 00:45 UTC
Notion allows users to make pages accessible to the general public via the Share to web toggle. This mechanism bypasses standard workspace permissions and extends access to all nested sub-pages by default.
While the current page content is visible to anyone with the URL, there is uncertainty regarding the visibility of the page's version history and previous edits. In a private workspace, the page history is a restricted administrative feature, but the behavior for public-facing pages is not explicitly documented for all workspace tiers.
When a page is shared publicly, can an external visitor access the version history or previous iterations of that page? Does the public link restrict the view strictly to the most recent published state?
No. A public visitor opening a Share to web link sees only the current published state of the page. The version history (Page history / Updates) is not part of the public sharing surface — it is an authenticated workspace feature tied to membership and plan tier, so anonymous viewers get no history UI and no way to browse prior edits through Notion itself.
The confirmed part: Notion's public sharing renders a snapshot of the page as it exists now. The sharing menu's options (duplicate as template, search engine indexing, link preview) control distribution and presentation, not history access. Page history retention — how far back you can roll — is a paid-plan feature for workspace members, which strongly indicates it lives behind authentication.
The likely explanation: public pages are served as a rendered view, not an editable document session, so the history endpoints simply aren't exposed to the anonymous context. This matches how the feature behaves in practice, though Notion doesn't publish a formal permission matrix for every tier, and UI labels change over time.
Share to web.Workspace owners on higher tiers can also audit which pages are public and restrict sharing capability globally — worth doing if sensitive pages were ever shared, since the risk is stale public content and external caches, not Notion leaking its version history.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.