✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for WordPress Social Login: linked identities as tables

WordPress Social Login uses HybridAuth to link users by provider, persisting the link in wp_usermeta and optional profile fields in wp_wslusersprofiles. SleekView pivots both into a unified provider-per-user grid.

♾️ Lifetime License available

SleekView table view for WordPress Social Login

HybridAuth links and provider profile fields as one grid

WordPress Social Login (the free open-source plugin built on HybridAuth) creates a usermeta row per linked provider plus an optional wp_wslusersprofiles row that mirrors the provider profile (display name, profile image URL, identifier). The default settings page lists the configured providers and a basic stats panel, but the underlying identity map is not exposed as a user-by-provider grid anywhere in the admin.

SleekView reads wp_users, wp_usermeta, and wp_wslusersprofiles and surfaces each user's linked providers as columns, with the mirrored profile data joinable on demand. Filters like 'users whose profile image is missing' or 'users linked to a deprecated provider' become first-class chips. Saved views handle the common identity-team scenarios (deprecation queue, dormant-user queue, duplicate-email queue).

Edits flow through WordPress Social Login's documented hooks when unlinking, and direct wp_wslusersprofiles edits get an admin-only override with a clear warning. Inline edits to the mirrored display name or profile URL are particularly useful when a provider rotates URLs (common on Twitter and Facebook over the last two years).

Workflow

From settings page to a queryable identity grid

1

Pick the source tables

Point SleekView at wp_wslusersprofiles and join to wp_users. The agent UI suggests wp_usermeta joins for any custom WSL link keys it finds.
2

Compose the identity grid

Pick user, email, provider, provider identifier, link date, and mirrored profile fields. Save the layout for identity admins and a slimmer one for support.
3

Scope per role

Identity admins get unlink and edit rights, support gets read-only. The capability map uses WordPress roles directly, no parallel permission system.
4

Audit and edit inline

Filter to deprecated providers, bulk-unlink through the plugin's hook path, fix rotated display names inline, and export the rest for the next DPO review.

Sample columns

A typical WSL identity view

Pivots wp_usermeta on WSL link keys and joins wp_wslusersprofiles for the mirrored profile fields.
Source: wp_users + wp_usermeta + wp_wslusersprofiles
User Email Provider Provider ID Linked Status
alex_studio alex@studio.co Google 1138429102 Apr 23 Active
ria_design ria@design.io Facebook fb_998812 Apr 21 Active
tom_hello tom@hello.dev Twitter tw_44021 Mar 18 Stale
mia_brew mia@brew.coop LinkedIn li_77291 Jan 12 Orphan

Comparison

Default WordPress Social Login admin vs SleekView

Default WordPress Social Login admin

  • Linked-identity data is split between wp_usermeta and wp_wslusersprofiles with no unified grid
  • Mirrored profile fields are not exposed as filterable columns
  • No view of users linked to deprecated providers (e.g. legacy Twitter or older Google scopes)
  • Bulk-unlink across users requires raw SQL
  • No saved-view export for compliance and DPO requests

SleekView

  • Pivot the wp_wslusersprofiles table into one row per user-provider link
  • Filter to users with missing profile image or empty display name
  • Bulk-unlink legacy provider IDs through the plugin's hook path
  • Sort by linked-at timestamp to find dormant connections
  • Export the linked-identity map as CSV with provider and identifier columns

Features

What SleekView gives you for WordPress Social Login

User and identity join

Joins wp_users, wp_usermeta, and wp_wslusersprofiles so each row carries the user, provider, identifier, and mirrored profile fields without writing custom SQL.

Provider deprecation scan

Filter to users still linked to deprecated providers (legacy Twitter app, retired LinkedIn scope, removed OAuth flow) before flipping the kill switch in settings.

Inline profile cleanup

Edit the mirrored display name or profile URL inline when a provider rotates URLs. The write hits wp_wslusersprofiles through the plugin's documented hook path.

Audience

Who uses SleekView for WordPress Social Login

Identity admins

Plan provider deprecations from one queue. The pivot shows exactly how many active users would lose a login path if Twitter or an older Google scope were removed.

Compliance teams

Export the linked-identity map for DPO and security questionnaires. Provider, identifier, and link date are the columns a privacy audit asks for.

Support agents

Look up a stuck login by email, see which providers are linked, and decide between an unlink-and-retry path or a password reset. The history is on one screen.

The bigger picture

Social-login identity data is the most under-managed user data on most sites

Sites that have run social login for more than two years carry a long tail of linked identities, deprecated provider scopes, and orphaned profile rows. The data sits in wp_usermeta and wp_wslusersprofiles doing nothing visible until something goes wrong, like a Facebook scope change that breaks logins for a chunk of users, or a security review that asks 'how many users authenticate via Twitter only'. The default WSL admin is built for installation, not for ongoing identity work.

Identity admins need a pivot. Compliance teams need an export. Support agents need a per-user lookup.

SleekView delivers all three from the same grid because the underlying data is just two joined tables. Provider deprecation planning, dormant-account cleanup, and DPO questionnaires all reduce to filters and exports on the same view. The identity layer becomes legible, which is exactly what identity layers fail to do by default in WordPress.

Questions

Common questions about SleekView for WordPress Social Login

The free plugin is community-maintained on the WordPress.org repository and HybridAuth is the underlying library. SleekView treats the schema as a stable read source and only writes through documented hooks, so version drift in the plugin itself does not change the grid's behavior.

 

Yes. wp_wslusersprofiles stores the profile image URL as a column. SleekView surfaces it as an image column with hover-preview, useful when verifying that a user is the person you think they are during support interactions.

 

Provider strings live in wp_usermeta and wp_wslusersprofiles as text. If a provider has been renamed (for example Twitter to X) the historical rows still carry the old string, which the grid exposes as-is so you can choose whether to bulk-rename them or leave them for audit.

 

No. SleekView treats access and refresh tokens as sensitive and never displays them in the grid or in CSV exports. The columns surfaced are the identifier and the mirrored profile fields only.

 

The grid only surfaces providers that exist in the wp_usermeta and wp_wslusersprofiles rows. Disabling a provider in WSL settings stops new links but the historical rows still appear so you can decide whether to keep, archive, or unlink them.

 

No. The pivot runs as its own SleekView and never overrides the core user list. You opt into the grid by opening the saved view; the default WordPress users screen is untouched.

 

Yes. Each provider is its own boolean column and filters compose naturally; the chip combination 'Google equals linked and Facebook equals linked' returns the dual-linked set. Useful for spotting users who would be safe to migrate off a third provider.

 

Yes. The bulk-unlink action calls the same do_action the plugin's own UI would call. Any third-party plugins listening for the unlink event (analytics, audit logs, downstream user-flag updates) still fire as expected.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView