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.

API authentication

System-to-system access is a documented requirement, not a shipped capability yet, see Authentication & Scopes for what’s required before it publishes.

Role-based access

Permissions are scoped by role, configure, run, and review are separate.

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

Not yet. Automated, system-level API sign-in is a documented requirement, not a shipped capability. See Authentication & Scopes for what’s required before it publishes.
Yes. Sandbox is fully isolated from production.
Your administrators, through role-based access configured in Governance.

API Authentication

The requirements that must land before API-key/OAuth access publishes.

Governance

Configure users, roles, and access.