AIDEN - Role based access control
Control who can create tests using AIDEN, execute on Test cloud, and access other AI-powered features with granular permissions.
These settings help you balance team productivity with security and budget requirements by allowing different levels of access to AIDEN's capabilities.
Understanding AIDEN Permissions
In the role's permissions, the AIDEN section allows you to customize access based on team roles and organizational policies.
Instead of an all-or-nothing approach, you can now enable specific AIDEN capabilities while restricting others.
Available Permission Types
Manual Testing – Create: Controls access to AI-powered manual test case generation through the "Create with AI" feature.
Automation – Create: Manages the ability to generate automated test cases using AIDEN's automation capabilities.
Automation – Execute: Determines who can run automated tests on the Test Cloud platform.
Advisor – Analyse: Controls access to AIDEN's Test advisor feature for existing test cases.
Code Download: Manages the ability to export and download AI-generated test code.
Know the defaults
Standard system roles:
- Admin, Owner, Member: Full access to all AIDEN capabilities by default
- Read-Only: No access to any AIDEN features
Custom roles:
You can configure permissions for each AIDEN capability, when creating or editing the role.
Read more about custom roles, here.
What happens when a permission is disabled for a role?
When a permission is disabled, the corresponding feature disappears from the user interface to maintain clarity and prevent confusion.
Why might I need RBAC for AIDEN?
Budget Control: You may want to use only a specific feature and disable others to prevent accidental usage, or unexpected costs.
Security Policy Compliance: for example, your organization needs to prevent code export while allowing test creation.
Tiered Access: Different teams/roles require different AIDEN capabilities.
To completely disable all AI features in your workspace, please check this page.
Last updated