Skip to main content
IOXNAccess
Technical explainer

How IOXN Access intake persistence works

Connected brand workflows persist structured requests through the canonical IOXN Access intake layer while keeping the brand as the public commercial front door.

Commercial question answered: What technically happens when a connected IOXN intake is submitted?
Claim classification: Operating capability. Inspect the relevant workflow or request a documented capability review.
Evidence and verification rules

Canonical persistence path

A connected workflow submits a structured payload to the IOXN Access intake endpoint. The payload is validated and, when persistence is configured, becomes a confidential hidden operating record with a human-readable identifier.

Failure behavior

Persistence failures must remain visible as failures. A workflow can preserve a prepared fallback, but it must not display an IOXN Record ID or imply database persistence unless the canonical intake returns a successful result.

Identity linkage

A legitimate email can support account and record linkage, but account identity remains distinct from approval, membership, credential issuance or contract formation.

Data minimization

Pre-engagement selection and analytics should use only the minimum context needed for routing and aggregate funnel measurement. Free-text request content, private record identifiers and authenticated workspace URLs are not required for public conversion analytics.