Currently, when a user archives a page in Confluence, providing an "Archive Note" is optional. In many cases, pages are archived without any context. Years later, when teams encounter these archived pages, they lack the necessary information to understand why the content was archived or if the knowledge remains relevant. While this could be managed at an Org level, different spaces have different governance needs, making a global requirement too restrictive.

Suggested Solution:
Introduce a Space-level setting (within Space Settings > Permissions or Content Tools) that allows Space Administrators to toggle a "Require Archive Note" option.

• When enabled, the "Archive" dialog box must prevent the user from proceeding until a minimum number of characters are entered into the Archive Note field.

• This ensures that every archived page in that specific space has a documented reason, preserving the "paper trail" for future readers.

Workaround:
There is currently no native way to enforce this. Teams must rely on manual process documentation and "best effort" compliance from users, or use third-party apps like ScriptRunner to create custom listeners that intercept the archive event, though this is complex to maintain.