Auth0

Auth0, now part of Okta, is an authentication and authorization platform commonly used by companies building their own customer-facing applications. This isn’t a claims integration, Auth0 is about how your organization runs Polygrade itself as procured enterprise software: single sign-on for teams already standardized on Auth0.

What Polygrade does with Auth0

Where your organization already uses Auth0 as its identity layer, Polygrade can authenticate against it the same way it does against Okta or Entra ID, keeping one identity system across your tools.

This sits apart from Polygrade’s claim-handling integrations entirely. Auth0 doesn’t touch claim data, parts sourcing, or payment execution, it’s the layer that governs how your team accesses and monitors Polygrade as a system, the same way it governs every other vendor you run Auth0 against.

How the Auth0 connection works

Polygrade’s authentication layer accepts Auth0 as a SAML or OIDC identity provider, configured during onboarding.

This is configured during enterprise onboarding rather than left to a self-serve setup, since it touches how your team authenticates or how your operations team gets alerted.

What stays in Auth0

Auth0 continues to manage identity, observability, or incident routing exactly as it does for every other tool in your stack. Polygrade is one more system governed by the rules you already have in Auth0, not a special case.

Data handling and security

Polygrade is SOC 2 compliant, with both Type I and Type II audits complete, and each client runs on a company-specific instance, a property directly relevant to how access through Auth0 is scoped, since there’s no shared environment to accidentally expose.

Every claim recommendation Polygrade makes is logged with a confidence level and its supporting inputs, independent of whatever visibility Auth0 is configured to provide, Auth0 adds a second layer of oversight on top of an already-audited system, not a replacement for it.

Setting this up

A dedicated Forward Deployed Engineer configures the Auth0 connection as part of enterprise onboarding, working with whoever owns identity or operations tooling on your side.

Frequently asked questions about Polygrade and Auth0

Is Auth0 used for claims data, like Polygrade’s other integrations?

No. Auth0 governs how your organization accesses or monitors Polygrade itself; claim, parts, and payment data move through Polygrade’s separate category-specific integrations.

How does Polygrade connect to Auth0?

Polygrade’s authentication layer accepts Auth0 as a SAML or OIDC identity provider, configured during onboarding.

Is Auth0 required to use Polygrade?

No. Auth0 is available for enterprise clients who want Polygrade to run under their existing identity, observability, or incident management setup, it isn’t required for Polygrade’s core claims functionality.