Roles and Permissions (RBAC)

TestMu AI Roles and Permissions (RBAC) allows organization admins to define fine-grained access control across products, projects, and features. With Custom Roles and Permissions, you can control which team members have access to specific products, what actions they can perform, and ensure that each user only sees what is relevant to their role.

This is especially useful for large enterprises with multiple teams where different groups need access to different parts of the platform, for example, one team working exclusively with KaneAI and Test Manager, while another only needs access to SmartUI and Automation.

info

Custom Roles and Permissions is an enterprise-level feature. Please contact your account manager or reach out to [email protected] to get it enabled for your organization.

Prerequisites

• You must be an Admin of your TestMu AI organization.
• Ensure your organization has the RBAC feature enabled by the TestMu AI team.
• Familiarity with User Management and Team Management is recommended.

Understanding Default Roles

Navigate to Organization Settings > Custom Roles & Permissions from the left sidebar. You will see the Custom Roles & Permissions page displaying all existing roles in your organization.

TestMu AI provides three default roles out of the box:

Role	Description	Entity Permissions
Admin	Full access to all products and entities with complete permissions.	List, Read, Create, Update, Delete, Execute on all entities
User	Standard access with full permissions on most products and entities.	List, Read, Create, Update, Delete, Execute on all entities
Guest	Read-only access across products with limited entity permissions.	List, Read only on entities

tip

Roles are auto-applied at login.

Creating and Applying Custom Roles

Custom roles give you the flexibility to tailor access permissions to match your organization's specific needs. Unlike the default roles (Admin, User, Guest), which cannot be edited, custom roles allow you to define exactly which products, entities, and actions each team member can access. To set up custom permissions, you need to create a custom role.

Step 1: On the Custom Roles & Permissions page, click the Create New Role button in the top-right corner.

Step 2: In the Create New Role dialog, enter a Role Name that clearly describes the role's purpose (e.g., "SmartUI Tester", "KaneAI Developer", "QA Lead").

Step 3: You can configure product-level access or entity-level access based on your requirements.

Step 4: Click Create to complete the process.

Step 5: Assign the custom role to users or teams based on your use case:

• To assign to individual users: Navigate to Organization Settings > Members, click on the user's row or the options menu, and assign the custom role.

• To assign to a team: Navigate to Organization Settings > Teams, select a team, and assign the desired custom role. All members of the team will automatically inherit the same permissions.

Product Level Access

Product-level access lets you control which TestMu AI products a user can see and interact with. This is the most impactful RBAC setting as it determines what shows up on a user's dashboard, sidebar, and which URLs they can visit.

When creating or editing a role, add List of Products as an entity and select only the products this role should have access to, such as KaneAI, HyperExecute, SmartUI, and more.

What happens when a product is restricted?

• The product is hidden from the sidebar and dashboard for the user.
• If a user tries to directly access a restricted product URL, they are redirected to a 403 page.

When to use Product Level Access

• Security & compliance:Restrict sensitive products like Insights or Settings to admins and leads only, ensuring regular testers don't have access to org-level analytics or configurations.
• Onboarding new members:New team members can be given a limited role with access to only Real Time and Automation while they ramp up, then gradually expanded to include KaneAI and HyperExecute.
• Client or vendor access:External contractors working on a specific product area (e.g., mobile testing) can be restricted to only Real Device and Automation without exposing the rest of the platform.

Entity Level Access

Entity-level access allows you to configure granular permissions for specific items and product areas within the platform. Currently, entity-level access is supported for Test Manager only.

info

Support for entity-level access in other products is planned for future releases.

Select Specific Entities

Assign permissions to specific items within the platform:

Entity	Description
Projects	Grant access to Test Manager projects.
Test Runs	Grant access to test runs.
Test Cases and Test Case Instances	Grant access to Test Manager test cases and test case instances.

Granular Control Coming Soon

Configure fine-grained permissions within specific product areas:

Entity	Description
HyperExecute	Control permissions for jobs, tasks, stages, and configurations within HyperExecute.
KaneAI and Test Manager	Control permissions for test plans, builds, milestones, and other Test Manager entities.
Automation	Control permissions for builds, sessions, and automation-related resources.
Analytics	Control permissions for dashboards, widgets, and reporting features.
Organization	Control permissions for organization-level settings, user management, and team management.

Each granular entity expands into sub-entities with specific permission levels:

• List:View items in a list.
• Read:View item details.
• Create:Create new items.
• Update:Modify existing items.
• Delete:Remove items.
• Execute:Run or trigger items (e.g., execute test runs, trigger jobs).