Issue Summary

Ensure that archiving pages which are only protected by inherited restrictions does not widen access to space‑level permissions, but keeps them restricted by default.

Use Case

• Currently, if a page is “Restricted by a parent – Anyone on the parent – Can view” and a user archives it, Confluence drops the inherited restriction and the archived page becomes visible according to space‑level permissions.
• A warning is shown, but if the user proceeds, sensitive content can unintentionally become visible to everyone with space access (this has already occurred in a real incident).

Requested Improvement

For pages that rely solely on inherited restrictions, archiving should:

• Default to a safe, still‑restricted state (e.g., automatically apply a local restriction to the archiver + space admins / existing allowed users), and/or
• Present an archive dialog that forces an explicit permission choice, with a secure default (keep restricted), and an explicit opt‑in if the user really wants to open it to everyone with space access.
  This makes “Archive” the default, conservative, privacy‑preserving action for inherited‑restricted pages.

Workaround

There’s no global setting today.

The safe approach is to add a local page restriction before archiving , so the page remains restricted even after inheritance is broken.