[TASK] RBAC / Wallet Detection for Features Access

[monaiuu]

Description

Implement a system that allows users to switch between Deployer, Operator, and Developer roles from the side navigation, while also detecting the connected wallet's role to manage access to certain features. The system will ensure that users can preview role-specific features but are restricted from full access unless their wallet is assigned the appropriate role.

Tasks

Role-Based Navigation:

• Allow users to switch views between Deployer, Operator, and Developer roles from the side navigation.
• Ensure each role view offers a distinct set of features and functionality, allowing users to preview features even if their wallet isn’t assigned to that role.
  Wallet Role Detection:
• Implement wallet role detection to verify the connected wallet’s role (e.g., Operator, Deployer, Developer).
• Example: If a user switches to the Operator role view but their wallet is not associated with the operator role, the system should:
  • Allow them to preview features such as the list of Blueprints.
  • Restrict actions such as pre-registration or editing features that require operator permissions.
    Access Control for Role-Specific Features:
• If the connected wallet does not have the necessary role for a specific feature, show a disabled state for the feature or prevent submission (e.g., preventing pre-registration for Blueprints if the wallet isn’t an operator).
  Landing Homepage Detection:
• On the landing homepage, detect if the connected wallet is not associated with a specific role (e.g., operator) and display a prompt to guide users on how to become an operator or deployer via linked documentation.

Screenshots