Connect identity evidence

Add the identity evidence RAIL uses to resolve usage owners. See Docs authority & product state.

Execute this step in SaaS guided setup. For self-hosted deployments, use the same /domains/adoption/onboarding path on your own instance host.

Steps

Role: Engineer for connector setup; Admin for directory role changes.

1. Choose the directory, repository, tag, or approved identity source.
2. Register its read-only identity-resolution connector and select the allowed tenant or organization scope.
3. Run the readiness probe and inspect the sample identities and stable keys.
4. Set evidence precedence when more than 1 source can resolve the same owner.

IdP federation authenticates users to Venturi. An identity-resolution connector provides attribution evidence. Do not substitute 1 for the other.

Success evidence

The connector is read-only and fresh, sample identity keys resolve without cross-tenant results, and unresolved identities remain explicitly unknown.

Recovery

Correct the connector scope, stable key, or precedence rule named by the probe. If evidence conflicts, keep the record unresolved until an authoritative source is available.