Adding Sub Roles to Individual User's Permission

Proposal: Streamlined Role-Based Access and UI Simplification

To improve governance, reduce clutter, and ensure quality, we propose enhancing the current role-based access model with access sub-role granularity and UI customization. This would allow teams to:

1. Restrict Feature Access by Sub-Role

  • Disable or hide capabilities like:
    • Creating REST connections
    • Defining functions
    • Managing web/mobile locators
  • Purpose: Prevent misuse, enforce standards, and route complex tasks to qualified QA analysts.

2. Simplify the User Interface

  • Hide tabs or menus irrelevant to a user’s role.
  • Reduce onboarding friction and cognitive overload for new users.
  • Ensure contributors focus only on what they need.

3. Enforce Governance and Quality

  • Prevent the creation of non-compliant artifacts.
  • Ensure that critical configurations go through vetted QA processes.
  • Reduce rework and improve maintainability.
0
1 comment
Avatar
Joseph Hamdan

Hi Zach,

We appreciate your continued interest in improving Subject7 and adding additional features. We are evaluating this and will provide updates hopefully soon. 

Regards,
Subject7 Team

0
Comment actions Permalink

Please sign in to leave a comment.