...
- Unspecified (that is, the user is authenticated, but not assigned a role via CTP): Users can view and monitor assets, but not provision, create, modify, delete, or deploy them. This is read-only access.
- Provision: Users can view and monitor assets as well as provision assets (for example, change proxy configurations, performance profiles, and data groups).
- System: Users can view, monitor, provision, create, modify, delete, and deploy assets, plus configure global JMS connections and global MQ queue managers.
- Admin: Users can view, monitor, provision, create, modify, delete, and deploy assets, plus have all the rights that a System user has plus the ability create/configure user accounts and modify all settings in the server’s configuration panel (Monitoring, Server Configuration, Connections, and so on). This is full access.
For a more detailed breakdown of the actions allowed for each role, see Understanding Role-Based Permissions.
...
| Capability | Full Access | System-level Access | Provision-Only Access | Read-Only Access |
|---|---|---|---|---|
| View assets (virtual assets, proxies, files) | X | X | X | X |
| Start/stop monitoring | X | X | X | X |
| Enable/disable assets | X | X | X | |
| Configure JDBC Controller settings | X | X | X | |
| Change Parasoft JDBC Driver modes | X | X | X | |
| Start/stop recording | X | X | X | |
| Change active data groups | X | X | X | |
| Change active performance profiles | X | X | X | |
| Configure JMS connection and MQ queue manager settings | X | X | ||
| Modify settings in the server’s configuration panel (Monitoring, Server Configuration, Connections, and so on)all Server Configuration settings | X | X | ||
| Refresh a server | X | X | ||
| Add assets | X | X | ||
| Delete assets | X | X | ||
| Re-deploy all assets | X | X |