CRITICAL story-role-based-access-control-peer-mentor-002 3 pts
3
Story Points
Critical
Priority
Role-Based Access Control
Feature

User Story

As a user
I want to see a dedicated no-access screen with a clear explanation and actionable navigation options when I attempt to access a restricted area
So that So that I understand why I cannot access the content and can take appropriate next steps such as switching roles or contacting support, rather than experiencing a silent failure or blank screen

Acceptance Criteria

  • Given a user with an insufficient role attempts to access a restricted route, when the Permission Guard evaluates the request, then the user is redirected to the No-Access Screen
  • Given the No-Access Screen is displayed, when the user views it, then it shows a clear human-readable explanation of why access was denied
  • Given the user has multiple roles and is on the No-Access Screen, when they view the screen, then a role switch option is visible and functional
  • Given the user has only one role and is on the No-Access Screen, when they view the screen, then a contact support option is presented
  • Given a Global Administrator attempts to access standard app routes, when the Permission Guard evaluates the request, then they are redirected to the No-Access Screen with guidance toward the admin portal
  • Given the No-Access Screen is displayed, when the user presses the back button, then they are navigated to a safe fallback screen without error

Business Value

Silent failures and blank screens when access is denied are a major source of support requests and user confusion. A clear no-access screen with self-service options reduces coordinator and support team burden significantly. For global admins who should never use standard app flows, this screen provides critical guidance preventing them from accidentally modifying production data in the wrong context.