Each time a visitor signs in with Facebook, Google, Apple, or another configured provider, Nextend Social Login writes the linked profile ID, the cached display data, and the OAuth grant state into the user's usermeta under nsl_* keys. The default WordPress Users screen never surfaces any of it, so finding which account belongs to which provider means clicking into individual profiles or running a raw SQL join across wp_usermeta. Neither scales past a few hundred users.

SleekView turns that scattered metadata into a structured table with one row per linked account: user ID, provider (Google, Facebook, Twitter, Apple), social ID, display name, linked-since date, and token status. The columns come straight from the keys Nextend already maintains, so adding a new provider through Nextend Pro Addon makes its rows appear in the grid the same minute it is enabled. Nothing to import, no second registry to keep in sync.

The token-status column is what most admins did not realise they needed. Nextend stores enough metadata to tell whether a grant has been revoked or is heading toward expiry, but the standard WordPress profile editor does not surface it. A revoked Apple grant from November means that user cannot log in next time, but you do not know that until they hit the broken flow. The grid catches it weeks earlier and lets you filter exactly the cohort that needs a re-link prompt.

Social login is one of the few WordPress features where the data is high-value and almost completely invisible. Nextend captures the exact mix of providers your users actually pick, when they linked, and whether the grants are still valid. Marketing wants that data to know whether Google or Apple drives more registrations.

Security wants it to know how many revoked grants are sitting in usermeta unable to authenticate. Compliance wants to know which users have linked accounts at all when an SAR comes in. Three teams, one dataset, all of it stored as serialized usermeta that no default WordPress screen exposes.

The cost of keeping that data hidden is real: it shows up as broken logins for revoked tokens, as marketing decisions made on guesswork, and as compliance answers that take hours instead of minutes. SleekView changes the cost by treating linked accounts as the structured dataset they already are, just one that happens to live behind a meta key prefix instead of a custom table.