Skip to main content

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

Always validate in sandbox first. Production workflows should only be enabled after go-live readiness is confirmed.

FAQs

MCP clients authenticate through Exterview OAuth as the signed-in user. Upcoming: API-key access for system-to-system integrations. See API Authentication.
Yes. Sandbox is fully isolated from production.
Your administrators, through role-based access configured in Governance.