Add provider evidence

Register at least 1 connected source. Venturi tenant, connector, federation, and external-ID setup artifacts are generated in-product. Customer-provided provider-account credentials are entered in-product. Credentials remain tenant-local and are validated for read-only access. 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 or Admin with connector settings access.

1. Select a cloud or provider source in guided setup.
2. For a cloud connector, apply the generated Venturi setup artifacts and register the resulting identifier in the same form.
3. For a provider API, enter customer-provided read-only provider-account credentials in-product.
4. Run automated credential validation.

Automated credential validation checks identity, scope, trust conditions, reachability, expected reads, and denied writes. It never accepts a partial credential.

Success evidence

At least 1 source shows Connected, with validation time, source scope, and the 1st readiness probe recorded.

Recovery

Use the exact failed field or provider error. Correct scope or trust settings or rotate uncertain credentials. Do not retry an unchanged credential after an authorization failure.