Issue Summary

When a Confluence page belongs to a space that has been changed from open to restricted, clicking “View changes” from an existing Slack notification opens a request-access view where the title shows a raw i18n key instead of a proper, user‑friendly message.

Only the title is affected; the body text below is rendered correctly (e.g. “Hit the request access button and we'll find someone who can give you access”).

This is confusing to end users and looks like a broken/localization issue.

Steps to Reproduce

1. In Confluence Cloud, create a space that is initially open (no access restrictions).

1. Create a page in that space and make changes so that Slack notifications are sent to a configured Slack channel.

1. In Slack, locate one of the existing notifications for that page (from when the space was open).

1. In Confluence, change the space to a restricted space so that access now requires permission/request.

1. Back in Slack, on the old notification, click “View changes”.

Expected Results

• Slack / Confluence renders a proper, localized title that clearly states the page is restricted and that the user needs to request access.

• No raw i18n keys are displayed to the end user.

Actual Results

• The title displays a raw i18n key similar to:
  confluence.request.access.pagerestricted.requestaccess.title..page

• Only the body text under the title is user‑friendly; the heading looks broken/technical.

Impact

• End users see internal i18n key values instead of a meaningful message.

• Creates confusion, appears as a broken or technical error rather than a clear “this page is restricted” explanation.

• Reported by an Enterprise customer preparing for production rollout of the Confluence Slack app.

Customer Evidence / Attachments

• Screenshot from customer: view_changes_message_2026-04-30T18_11_08.474Z.png (shows the raw i18n key).