Permissions & restrictions
View restrictions inherit but edit restrictions don't, and the resulting mismatch has been an open complaint since 2006.
What people actually say
✕Edit restrictions aren't inherited — only view restrictions cascade down — so admins have to lock down every child page individually or write scripts to do it for them.
Source: Atlassian — Page restrictions docs ↗✕The request to inherit page edit permissions like view permissions has been open on Atlassian's tracker since 2006, with Atlassian explicitly declining to ship it.
Source: Atlassian — CONFSERVER-5095 inherit edit permissions ↗✕Even when permissions look right, inherited restrictions are sometimes not respected, and Atlassian's own KB documents the failure modes administrators have to debug.
Source: Atlassian — Inherited permissions not respected ↗
Permissions are a single typed model in your repo — space, page, role, action — with view and edit inheritance both expressed as recursive Postgres queries. One CI test fails the day someone breaks the model, and 'who can edit this page' is one SQL query you can read, not four overlapping schemes.