Governance × audit (visual-first)
Admin controls
- Scenario settings and output formats
- Knowledge sources / KB management
- Guardrails / policies
- Regression test sets
Audit trails
- What was asked and when (identity mapped by customer SSO)
- Which sources were used
- What output was produced
- Whether it was approved/executed
Acceptance-ready
- Turn chat into evidence
- Regression-ready quality
- Clear access and accountability
Key point: We do not replace your IAM (SSO/RBAC), but we provide the admin capabilities needed for governance and audits.
- What admins can govern (examples): scenario settings, knowledge sources/knowledge base management, guardrails/policies, regression test sets, output formats and response tone templates (agreement/version govern).
- Audit trails: trace “what was asked and when, which sources were used, what output was produced, and whether it was approved/executed”. User identity mapping (“who asked”) must rely on customer SSO/IAM (agreement/config govern).
- Audit-ready delivery: turn “chat usage” into evidence-based, verifiable delivery.
Other articles
Previous
How do SSO / permissions (RBAC) work?
Next
Will our chats and knowledge base be used to train models?
Related questions