Insights is a read-only dashboard on a tab of Users, next to “Users” and “Invitations”. It counts the on-chain identities of people in the registry of the current organisation and network (contract and token identities are not counted), counts the verifications issuers have signed for those identities, and charts how both moved over time. Use it for a trend or a total, such as whether pending registrations are growing or how many verifications the organisation has issued.
Reading the page changes nothing. For one participant, open their record under Users or Entities: an aggregate shows that something changed, not which participant changed or why.
Identity insights opens with the range dropdown on “1 month” and “Compare with prior period” switched on, directly under the tabs.
Below the range controls sit the key figures “Registered identities”, “Active verifications” and “Verifications per identity”, then the attention counts that are not zero, here “Users pending identity registration” and “Topics with no active verification”. A count of verifications revoked in the range joins them when it is not zero. Two composition bars follow, “Active verifications by topic” and “Verification status”, then the “Identities and verifications” trend chart and the “Participants by country” map.
Steps
Set the range
Pick the range in the range dropdown. Leave Compare with prior period on to see each figure's change against the period just before the range. What each section shows lists which figures follow the range.
Work the attention counts
Each count opens the list where you act on it. Users pending identity registration 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”, the list of the system's topics, and its count shows in the warning colour.
The count covers enabled topics that no registered participant identity holds an active verification for, and that list does not mark which ones they are. A count of zero is not shown, and when all three counts are zero the section does not appear. A count that could not be read shows “Unavailable” instead.
Compare the identity and verification figures
Read Registered identities against its registered share and its “not yet registered” count, then read “Active verifications” against issued and revoked. The trend chart draws registered identities across the range, and its caption states how active verifications moved over 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 verification history rather than assigning a cause from the totals.
Investigate the participant
Open Users or “Entities”, find the participant, and read its registration status and verification history on its detail page.
What each section shows
The key figures describe the registry: how many identities exist, how many of them are registered, how many verifications are active, issued and revoked, and how many identities still wait for registration. The count revoked in the selected range sits in the attention counts. The sections go in this order:
One range drives every time-based figure on the page. It opens on “1 month” and the range dropdown 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 among the attention counts, and the trend chart. It does not move the composition, the map, the users pending identity registration 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 is turned off there and a line beside it says why. The figures refresh as new blocks confirm on the selected network. When the indexer is behind or rebuilding, a platform administrator or organisation owner sees a warning above the range that says so.
A composition with nothing to count says No data yet and “The breakdown appears once there is data to show.” instead of drawing an empty bar. The trend chart says “No data yet” and “The chart fills in once there is activity in this range.” when the range holds no data.
Identity counts and verification counts move independently
The identity figures count participants and where they are in registration. The verification figures count signed verifications and whether they are still in force. A participant can be fully registered with no verifications. The verification figures count only the verifications on registered identities, so an identity that leaves the registry takes its verifications out of them. 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.
The identities-created count is always the sum of the registered and “not yet registered” identities, so the registered share is read against identities that are still in the registry. An identity that is removed, or whose wallet was recovered under a new identity, leaves all three counts together.
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 a token whose rules include “Claim expiry” already refuses the participant once that verification has expired. Read this count as how many verifications have not been revoked or removed, not as how many pass eligibility.
The revoked count does not say who revoked a verification or why. Check the participant's verification history for that.
Troubleshooting
“Access restricted”
The page shows “Access restricted” without one of the roles. Ask a permission manager for the “Identity manager”, “Verification issuer” or “Permission manager” role in Admins and roles.
A chart and participant record seem different
Confirm the organisation and network first: a different organisation or network is the first cause to rule out. Then check the page range, and check which figure you read: issued verifications fall only when an identity leaves the registry, while “Active verifications”, the identities-created count, the “Registered identities” key figure and “Users pending identity registration” also fall for other reasons. The detail page and the aggregate both read indexed records, so check that the indexer is not behind before you compare them.
“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 takes the verification off the identity rather than marking it revoked. It happens when someone revokes without the issuer identity, from the Console's “Revoke verification”, the API or the identity itself. “Verification status” shows removals as their own share. Open the affected participant's verification history and look for a Verification removed event.
“Users pending identity registration” keeps growing and “Registered identities” does not
A user stays pending until an identity manager registers their identity, from Register identity on the user's page or by accepting their request on Entities. Nothing on this page moves it along. Open “Users” filtered to pending registrations and register each identity, or check “Pending participant registrations” on “Entities”.
Frequently asked questions
Why is there no organisation or network switcher visible on this page?
The account menu button at the top right names the active organisation when the top bar is wide enough, but the menu only offers a choice when there is something to switch to. It shows an Organisation submenu only for an account that belongs to more than one organisation or may create one, and a Network submenu only when multi-network support is on and the organisation has more than one active network. A single-organisation, single-network deployment still scopes every number on this page to that one pair.
Can I look further back than the default month?
Yes, using the range dropdown under the tabs. For a custom window it does not offer, such as a specific start and end date, query the same identity and verification statistics through the Platform API.