Roles
- OWNER: Manages users and resources in their own organization. Can permanently delete only Sessions and User Groups; every other entity is soft delete at most.
- MEMBER: Day-to-day access in their organization: view and contribute, with limited edits. Can permanently delete only Sessions and User Groups; every other entity is soft delete at most.
- HUMAN_EVALUATOR: Read-only across the organization, plus may annotate AI metrics and submit human evaluations.
- READER: Read-only across the organization. Cannot create, update, or delete anything.
Each cell shows what a role can do for that action. ✅ means allowed and ❌ means not allowed. A short rule (for example, “If product in own org”) means the action is allowed only when that rule is true at the time, checked against your organization and the record’s ownership.
Permissions by area
Identity & Organization
User
Organization
Subscription
User Group
Test Assets
Product
Version
Test
Test Case
Specification
Connections
Endpoint Connection
Phone Connection
WebRTC Connection
Evaluation & Results
Session
Evaluation
Annotating or submitting human evaluations also requires membership in the relevant User Group; the table shows the role-level gate only.
Inference Result
Trace
Comment
Free-form reviewer text on an inference result. Access also requires the parent inference result to be in your organization. Deleting is a soft delete; you may delete your own comments, and organization owners may delete any.
Monitor
Reference Data
Metric
Model
Analytics & Insights
AnalyticsNotes
- Read-only roles: READER and HUMAN_EVALUATOR can read exactly what a MEMBER can read (the same organization scope). They cannot create, update, or delete. HUMAN_EVALUATOR additionally may annotate AI metrics and submit human evaluations; READER cannot.
- Organization scope: “In own org” means the record (or its parent, such as a Product) has an organizationId equal to the signed-in user’s organization. This keeps each client organization’s data separate.
- Parent scope: For nested records (Version, Test, Evaluation, and so on) access is derived from the parent’s organization. Example: a Version belongs to a Product, and the Product belongs to an Organization. An Evaluation is reached through session to version to product.
- Global records: Some records (Metric, Model, and a Test with no product) can be global, meaning not tied to one organization. Global records are readable by every role in addition to their own organization’s records.
- Hard delete: Each entity table has two delete rows. Soft delete hides a record without removing it. Delete is a permanent removal, shown as allowed only for Session and User Group (OWNER and MEMBER, within their own organization); for every other entity it is denied to all roles listed here.