Overview
See Persona Connect Overview for what Persona Connect is and how organizations share data with each other. This article covers what you’ll see in your own Dashboard when a Verification or Inquiry was created by receiving shared data.
Persona Connect lets one organization share previously collected Verification and Inquiry data with another organization using a Share Token, so the receiving organization doesn’t have to put the same end user through Verification again. When data is shared this way, the resulting Inquiry and its Verifications are marked with a replication method of either:
- Clone: the shared data is copied as-is into the new organization’s Inquiry.
- Hydrate: the shared data is used to pre-fill an Inquiry that still runs its own new Verifications.
Only cloned Verifications and Inquiries are visibly flagged in the Dashboard — hydrated ones are not, since they go through their own independent Verification.
Where you’ll see it
On a Verification
If a Verification was created via Connect cloning, a purple Cloned sticker appears next to its Passed/Failed status indicator. Hovering or focusing the sticker shows a short explanation of what “Cloned” means.
Not every Verification type can carry this flag — it’s currently available on Selfie, Government ID, Document, Database, Phone Number, and Email Address Verifications.
On an Inquiry
If an Inquiry was created via Connect cloning, a banner appears at the top of the Inquiry’s detail page: “This Inquiry was cloned using Share Token <token>.” The Share Token is shown as plain text rather than a link, since there isn’t a Dashboard view for Share Tokens themselves.
If the same Inquiry is also redacted or in an inactive environment, you may see multiple banners stacked together — all of them remain visible while you scroll.
Why this matters
The Cloned sticker and banner are informational: they tell you the underlying Verification or Inquiry data originated from another organization’s prior Verification, rather than from a new Verification attempt with your organization. They don’t change the Verification’s Passed/Failed outcome or any of its checks — cloned data carries the same status and check results it had at the source.
If you don’t have the VERIFICATION_VIEW permission, you won’t see the Cloned sticker (or the Share Token that produced it), consistent with how that permission already gates other Verification-provenance details in the Dashboard.