Role-based access
Admin · QA lead · Support · Developer · Read-only roles with scoped permissions.
whetoresecurity
QA data handled with visibility and control
Role-based access, private workspaces, attachment controls, log redaction, audit history, data retention, and integration permissions — built for product quality data, not sensitive regulated content.
- RBAC Role-based access control
- 90 days Default retention window
- Audit Full action history
- 0 Auto code deploy
Security controls
Visibility and control over QA artifacts
Private workspaces
Isolated client or team workspaces with separate retention and integration scopes.
Attachment controls
Upload limits, file type restrictions, and automatic PII detection on screenshots.
Log redaction
API keys, tokens, and email addresses masked before storage and export.
Audit history
Every view, edit, approval, and sync logged with actor and timestamp.
Data retention
Configurable retention per workspace — 30, 90, 180 days, or custom enterprise policy.
Integration permissions
OAuth scopes reviewed at connect time. Sync only on human approval.
No auto-deploy
Whetore prepares QA artifacts. Teams verify bugs, decide priorities, and ship releases.
Whetore handles product quality and testing information — not medical, financial, legal, or recruitment data. It does not automatically change production code or deploy releases.
QA workflows with control built in
Low-risk category — high visibility over every artifact.