Insights
Read identity and verification counts for the selected organisation and network, and know when to stop trusting the aggregate and open the participant record.
Insights is a read-only dashboard. It counts every registered participant On-Chain IdentityAn On-Chain Identity lets a subject's verification serve every asset that accepts it, so a screened wallet skips re-onboarding for the next regulated asset.Read the concept in the current organisation and network, counts the verifications issuers have signed for them, and charts how both moved over time. Reach for this page when you want a trend or a total, such as whether pending registrations are piling up or how many verifications the organisation has issued in total.
Reading it changes nothing: every figure counts something someone else already did, so opening this page carries no consequence for any participant. Insights is the wrong page for anything about one specific participant, because an aggregate can tell you that something changed without ever telling you which participant changed or why. A discrepancy always sends you to that participant's own record, under Users or Entities.
Open "Users" under "Organisation participants" in the sidebar, then select the "Insights" tab beside "All users"; the page heading reads "Identity insights".
Every number on this page is scoped to two selections you make before you ever open it: the organisation and the network. The organisation is the tenant whose participant population you are counting. The Console never blends counts across organisations, so switching organisations changes every figure on the page at once.
The network is the specific chain deployment behind the current view. Registration and verification records live on that chain, and a deployment can run more than one. The same organisation can show different totals on two networks, because each network keeps its own separate ledger of records.
Checking both selections first avoids a common misread: a number that looks like it dropped can belong to a different network than the one you checked yesterday.
How the page reads
The page opens like a briefing. A sentence at the top says what the registry looks like right now: how many identities exist, how many of them are registered, how many verifications are active, how many were revoked in the selected range, and how many registrations are still waiting. The sections below it back that sentence up, in this order:
| Section | What it shows |
|---|---|
| Key figures | "Identities" (registered identities, with registered, pending and the registered share of every identity created), "Active verifications" (with how many were issued and revoked), and "Verifications per identity" (active verifications divided by registered identities, "coverage depth"). |
| Needs attention | Three counts that link to where you act on them: "Registrations pending", verifications revoked in the selected range, and "Topics with no active verification". |
| Composition, as of now | "Active verifications by topic", the five largest topics plus "Other", and "Verification status", active, revoked and removed as shares of every verification issued. |
| Trend | "Identities and verifications": registered identities across the range, with the prior period as a dashed line. The chart description states how active verifications moved over the same range. |
| Participants by country | "Participants by jurisdiction", active participant identities per country of residence. |
One range drives every time-based figure on the page. It opens on "1 month" and the dropdown in the page header offers "All", "YTD", "12 months", "6 months", "3 months", "1 month", "Last 7 days" and "Last 24 hours". The range moves the key-figure deltas and trend lines, the revoked count in "Needs attention", and the trend chart. It does not move the composition, the map, the pending registrations or the topic count: those show the registry as it stands now, which is why the composition section is labelled as of now.
"Compare with prior period" is on by default. With it on, each key figure that has a history shows its change against the period of the same length just before the range, and the trend chart draws that prior period as a dashed line. "Verifications per identity" has no history and always shows its "coverage depth" line. The "All" range has no prior period, so the toggle disappears there. The freshness line under the range says when the figures last refreshed; they refresh as new blocks confirm on the selected network.
Identity counts and verification counts move independently
The page carries two independent groups of measures, and mixing them up is a common misread. The identity figures answer "how many participants exist and where are they in registration". The verification figures answer "how many signed attestations exist and are they still valid". A participant can be fully registered with zero verifications, or verified against a topic while its registration itself sits pending; the two groups track different on-chain records and neither implies the other. "Verifications per identity" divides one group by the other, so read it as an average, never as a guarantee that every identity holds that many.
| Figure | What it counts | Rises on | Falls on |
|---|---|---|---|
| Identities in the sentence | Counts every identity ever registered in this organisation's registry on the current network. | A new registration. | Never; a removed identity still counts here. |
| "Identities" key figure | Counts identities the registry currently treats as confirmed. | A registration is confirmed. | A removal. |
| "Registrations pending" | Counts identities the registry has recorded but not yet confirmed, the same state a participant's own Identity tab reports as "Pending registration". | A new registration awaiting confirmation. | Confirmation, or a removal. |
| "Active verifications" | Counts verifications not yet revoked or removed. | A new verification. | A revocation or a removal. |
| Issued, in the detail line | Counts every verification ever issued for this organisation and network. | A new verification. | Never. |
| Revoked, in the detail line | Counts verifications explicitly revoked from the Console, which preserves the record for audit rather than deleting it. | A revocation. | Never. |
The identity count in the sentence is not the sum of registered and pending. An identity later removed from the registry still counts there forever, but drops out of both the registered and pending counts the moment it is removed, and it lowers the registered share. If the identity numbers do not add up the way you expect, look for a removal first; it is the usual explanation.
"Active verifications" nets out only revocations and removals; it never subtracts expiry. A verification whose expiry timestamp has passed stays in "Active verifications" until someone revokes or removes it, even though the participant's own eligibility check already treats the required verification as expired. Read this count as how many verifications have not been revoked or removed, not as how many currently pass eligibility.
Revoking is self-service. The Console only shows the revoke control on a participant's own verification record to that same participant's signed-in account, never to an issuer or operator managing someone else's. The count alone does not identify the actor; check the claim history for the revocation.
A composition with nothing to count says "Nothing to show yet" instead of drawing an empty bar, and the trend chart says the same when the range holds no data.
Steps
Open Insights
Open "Organisation participants", then "Insights". The page loads identity counts and verification statistics for the selected organisation and network.
Screen equivalent: Identity insights opens with the range dropdown on "1 month" and "Compare with prior period" switched on. A sentence summarises identities, registered share, active verifications, revocations in the range and waiting registrations. Below it sit the key figures "Identities", "Active verifications" and "Verifications per identity", then three attention counts, "Registrations pending", the verifications revoked in the range and "Topics with no active verification". Two composition bars follow, "Active verifications by topic" and "Verification status", then the "Identities and verifications" trend chart and the "Participants by jurisdiction" map.
Set the range
Pick the range in the page header. Every delta, trend line, the revoked count and the trend chart follow it; the composition, the map and the pending and topic counts do not. Leave "Compare with prior period" on to see each figure's change against the period just before the range.
Work the attention counts
Each count opens the list where you act on it. "Registrations pending" opens "Users" filtered to pending registrations. The revoked count opens "Users", where each participant's verification history shows which verification was revoked and when. "Topics with no active verification" opens "Verification topics", where you can see which topics no issuer has verified anyone against yet. A count of zero is shown muted; a topic without any active verification is highlighted.
Compare the identity and verification figures
Read "Identities" against its registered, pending and registered-share detail, then read "Active verifications" against issued and revoked. Use the trend chart to see whether registered identities are rising, flat or falling over the range, and its description for how active verifications moved in the same range. A matching fall in active verifications and rise in revoked ones is consistent with revocation, but simultaneous changes can offset each other; inspect the claim history rather than assigning a cause from the totals.
Investigate the participant
Use this step to investigate a change or verify one participant. Open "Users" or "Entities" and find the affected participant. Review the signed records and registration status on its detail page. The aggregate page cannot prove one participant's current state; it can only tell you that the population-wide total moved.
Troubleshooting
Access restricted
Ask an administrator for the "Admin", "Identity manager", or "Verification issuer" role.
A chart and participant record seem different
Confirm the organisation and network first; a mismatch there explains most apparent discrepancies before you look any further. Then check the page range, and check which figure you read: issued verifications and the identity count in the sentence never decrease, while "Active verifications", the "Identities" key figure and "Registrations pending" do. The detail page shows individual indexed records; confirm their freshness when comparing them with the aggregate.
Active verifications dropped but revoked did not rise by the same amount
"Active verifications" can drop for a reason the revoked count never includes: a removal. A removal acts directly on the identity's on-chain record instead of going through the Console's own revoke control, so it leaves no trace on the revoked count even though it lowers "Active verifications". "Verification status" shows removals as their own share. Open the affected participant's verification history and look for a "Verification removed" event to confirm this happened. Insights reports only totals across the whole population, not the reason behind a single change.
Registrations pending keeps growing and Identities does not
A registration stays pending until the identity registry confirms it; nothing on this page moves it along or tells you why one confirmation is slow. Open the affected participant's record to check its own registration status, and treat a large or growing pending count as a signal to check the registration path for that participant kind, not a fact this page can explain by itself.
Frequently asked questions
Why is there no organisation or network switcher visible on this page?
The Console only shows a switcher when there is something to switch to. The organisation switcher renders in the sidebar only for an account that belongs to more than one organisation, and the network switcher renders only when the deployment runs more than one active network. A single-organisation, single-network deployment still scopes every number on this page to that one pair; there is nothing else to pick.
Can I look further back than the default 30 days?
Yes, using the range dropdown in the page header. For a custom window it does not offer, such as a specific start and end date, query the same identity and verification statistics directly through the Platform API.
Entities
Review and register organisation participants without login credentials, act on incoming registration requests, and see which data feeds each one publishes.
Verify a participant
Confirm a participant has a registered identity, add the issuer-signed verification, and check the target token's eligibility requirements.