AIDEN's role based access control lets you decide which team members can use specific AI capabilities, so you can balance productivity with security and budget requirements.
What it does?
Instead of an all-or-nothing toggle, you can enable or disable individual AIDEN capabilities per role. When a permission is disabled, the corresponding feature is hidden from the UI entirely.
Available permissions
Permission | Controls access to |
AI-powered manual test case generation (Test Designer) | |
Automated test generation (QA Architect) | |
Cloud test execution (AI Test Cloud) | |
Automation readiness analysis (Test Advisor) | |
Test code export (Automation Engineer) |
Default role settings
Role | AIDEN access |
Owner | Full access to all capabilities |
Admin | Full access to all capabilities |
Member | Full access to all capabilities |
Read-Only | No access to any AIDEN features |
For custom roles, you can configure permissions for each AIDEN capability when creating or editing the role.
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.
Disabling all AI features
To disable AIDEN entirely for your workspace (not per-role, but globally), see Disabling AI features.