CRITICAL story-no-access-screen-restricted-roles-organization-admin-001 3 pts
3
Story Points
Critical
Priority
No-Access Screen for Restricted Roles
Feature

User Story

As a Organization Administrator
I want to see a clear, informative no-access screen when I attempt to navigate to a section I do not have permission to use
So that I immediately understand that the area is restricted and I have not made a mistake or encountered a technical error

Acceptance Criteria

  • Given a peer mentor is authenticated and navigates to a coordinator-only route, when the role route guard evaluates permissions, then the no-access screen is displayed instead of the target route
  • Given the no-access screen is displayed, when the peer mentor views the screen, then a headline such as 'Access Restricted' and a plain-language explanation of the restriction is visible
  • Given the app uses organization-specific terminology, when the no-access screen renders, then labels are resolved through the organization labels provider so wording matches the org's configured terminology
  • Given a screen-reader user lands on the no-access screen, when VoiceOver or TalkBack reads the page, then the denial message and all interactive elements are announced correctly with appropriate semantics
  • Given the no-access screen is shown, when the peer mentor checks the bottom navigation, then navigation tabs that are inaccessible to their role are visually indicated as inactive or hidden

Business Value

Without a clear no-access screen, restricted users experience confusion, perceived app crashes, or silent failures that erode trust in the platform. A well-designed denial screen protects the product's credibility, reduces support tickets, and ensures security boundaries are communicated transparently — critical for volunteer organizations where diverse digital literacy levels mean users must never be left wondering what went wrong.