Purpose
How people and systems securely access Exterview, and how test and production stay separated.Access model
User login
Your team signs in using your company’s existing Microsoft account, so there’s no separate password to manage.
MCP client authentication
Authorized assistants use OAuth to connect as the signed-in user. Your
workspace’s sign-in configuration determines which sign-in options you see.
See MCP authentication.
Role-based access
Permissions are scoped by role, so configure, run, and review are separate.
Data Visibility sets which records each role sees: organization, department,
or own records.
Environment separation
Test and production are isolated from each other.
Environments
FAQs
How do developers authenticate to the API?
How do developers authenticate to the API?
MCP clients authenticate through Exterview OAuth as the signed-in user. Upcoming: API-key access for system-to-system integrations. See API Authentication.
Can we test without affecting live data?
Can we test without affecting live data?
Yes. Sandbox is fully isolated from production.
Who controls access?
Who controls access?
Your administrators, through role-based access configured in Governance.
Related
- API Authentication. How system access is authenticated and scoped.
- Governance. Configure users, roles, and access.

