Issue Summary

Currently, when a user attempts to access a page via a URL that originally belonged to a now-deleted space, and that user does not have access to the new destination space, the following behavior occurs:

• The page itself has no page-level restrictions
• However, the user sees the message:
  "You’ve stumbled on restricted content"

This message is misleading, because the actual access failure is due to lack of access to the space, not to the page itself. The message incorrectly implies that the page has individual restrictions.

Suggested features

Improve the condition logic so that in the following situation:

• The page has no restrictions
• The user does not have access to the space
• The original space was deleted and the page was moved
• The user accesses the old page URL (which redirects to the new location)

...then the message should reflect the true cause of access failure — for example:
"You don’t have access to this space"

Steps to Reproduce

1. Create a page in Space A with no restrictions. (i.e. https://kkim5.atlassian.net/wiki/spaces/hahaha/pages/101449738/)
2. Move the page to Space B. (https://kkim5.atlassian.net/wiki/spaces/spaceB/pages/101449738/)
3. Delete Space A.
4. As a user with no access to Space B, access the original Space A page URL. (https://kkim5.atlassian.net/wiki/spaces/spaceA/pages/101449738/)

Expected Results

Display “You don’t have access to this space”, since there are no page restrictions.

Actual Results

the user sees “You’ve stumbled on restricted content”.

Workaround

Clarification and Workaround

This issue occurs only under specific conditions:

• The original space was deleted, not archived
• The user has no access to the new space
• The user accesses the original URL

When the original space is archived instead of deleted, the correct message “You don’t have access to this space” is shown.

Workarounds:

• Archive the original space instead of deleting it
• Update any internal references or links to point to the new space's page URL directly