Permissions

This page documents roles and permissions in Veratrace for developers and administrators. Related: Source: Feature Inventory

​

Current Status

Permission enforcement is not found in the frontend codebase. Roles exist in mock data only. Source: Source: Feature Inventory

​

Available Roles

The following roles are defined in mock data:

​

Administrator

• Full access to all features and settings
• 24 permissions
• Can manage all resources (users, TWU models, agents, integrations)

Source: /Users/vincentgraham/clearline-ui/src/features/users/mockRoles.js

​

Manager

• Access to management features and reporting
• 16 permissions
• Can view and manage most resources

Source: /Users/vincentgraham/clearline-ui/src/features/users/mockRoles.js

​

Viewer

• Read-only access to reports and dashboards
• 8 permissions
• Can view but not modify resources

Source: /Users/vincentgraham/clearline-ui/src/features/users/mockRoles.js

​

Editor

• Can create and edit content, but cannot delete
• 12 permissions
• Limited modification capabilities

Source: /Users/vincentgraham/clearline-ui/src/features/users/mockRoles.js

​

Permission Enforcement

No role-based access control (RBAC) or permission checks found in frontend code. Source: Source: Feature Inventory

​

Authentication

Veratrace uses AWS Cognito for authentication via OIDC. User information is extracted from Cognito user profile (cognito:username). Source: Source: Feature Inventory

​

API Permission Checks

​

Role Assignment

​

Permission Definitions

​

Related

• Access Control - Access control configuration guide
• Authentication - Authentication details
• Manage Users Guide - User management