SleekView for Rescue Key Recovery: rescue tokens as tables
Rescue Key Recovery issues one-time rescue tokens per administrator and tracks issuance and use through wp_usermeta and an options-backed log entry. SleekView turns that token lifecycle into one filterable grid for the security team.
♾️ Lifetime License available
A token lifecycle that reads like a register
Rescue Key Recovery is the lockout-rescue plugin that issues a one-time signed token per administrator and accepts that token in place of the password during a recovery flow. Token state lives in wp_usermeta keyed by user ID, and a per-event log entry is appended to a serialised array in wp_options. The combination keeps the lifecycle on-site without needing a custom table.
The plugin's default admin shows whether a token is currently issued per user and offers a button to revoke or rotate. What it does not offer is a list view of every token ever issued, who used which token, and from which IP. The serialised wp_options log carries that history but is not exposed as a queryable surface in the admin.
SleekView reads the per-user wp_usermeta entries and the serialised options log together, unpacks the events, and renders one row per issued or used token. Each row carries the user, the issuance time, the use time, the IP, and the resolution. Edits route back through the plugin's token API. The integration keeps doing the rescue; SleekView turns the lifecycle into the register a security review will ask for.
Workflow
From a serialised log to a real token register
Pick the source
wp_usermeta token state and at the serialised event log in wp_options. The join unpacks the log and writes one row per issued token.
Compose columns
Save and scope per role
Edit inline or jump out
Sample columns
Rescue tokens across every admin
wp_usermeta (token state) joined to wp_options (serialised event log) and wp_users
| Issued | User | Used at | IP | Result |
|---|---|---|---|---|
| May 17 10:12 | alex@studio.co | May 17 10:34 | 84.12.x.x | Used |
| May 15 08:01 | ria@design.io | 203.0.113.x | Outstanding | |
| May 12 17:48 | tom@hello.dev | 45.61.x.x | Revoked | |
| May 09 22:55 | mia@brew.coop | May 10 06:14 | 92.18.x.x | Used |
Comparison
Default Rescue Key Recovery admin vs SleekView
Default Rescue Key Recovery
- No list view of every token ever issued
-
Serialised log inside
wp_optionsis not queryable through the admin - Outstanding tokens are not surfaced as a separate filter
- No saved view for revoked tokens across the audit window
- Audit-ready CSV exports of the token register are not exposed
SleekView
- One row per issued token with the user, the IP, and the resolution
- Filter to outstanding tokens older than seven days
- Sort by user to read the full token history per admin
- Inline rotate or revoke a token through the plugin's API
- Saved view for security-review evidence packs
Features
What SleekView gives you for Rescue Key Recovery
Outstanding token surfacing
Filter to tokens issued but not yet used to surface every outstanding rescue key. Stale outstanding tokens become a one-filter list rather than a per-user click.
Per-user token history
Group by user to read every token an admin has ever held. The audit history that lives in the options log finally has a per-user surface.
Audit-ready CSV
Export any filtered slice to CSV for the security review. The export carries the user, the issuance and use timestamps, and the resolution per token.
Audience
Who uses SleekView for Rescue Key Recovery
Security leads
Daily glance at outstanding tokens older than a week. The saved view turns stale rescue keys from a hidden risk into a triage queue.
Account ops
Read the rescue history per user and rotate a token inline when an admin reports it lost. The grid and the action share one workspace.
Compliance
Export the token register for the audit window with the user, the IP, and the resolution per row. The compliance review gets a defensible CSV without scraping the options table.
The bigger picture
Why a rescue-token plugin needs a register
A rescue-key plugin grants high-trust access by design, it accepts a signed token in place of the password during a lockout. Rescue Key Recovery already records the right signal, the per-user token state in wp_usermeta and the per-event entry in the serialised options log. What is missing is the surface that reads those two stores together for the team that has to answer security questions.
Security leads need to know which tokens are outstanding past their expiry. Account ops need to read the token history per admin before issuing a replacement. Compliance needs a defensible export of the token register across the audit window.
SleekView unpacks the options log, joins the usermeta state, and renders one grid where every issued token is one row. Edits route through the plugin's own token API, so the change is the same one the user profile screen would make. The integration keeps owning the rescue, and the team finally gets the register the audit will ask for.
Questions
Common questions about SleekView for Rescue Key Recovery
No. The plugin keeps owning the token issuance and validation. SleekView only reads wp_usermeta and the serialised log in wp_options, then surfaces them as one grid.
Yes. The result column carries Used, Outstanding, and Revoked values. Filter to Revoked to surface every token rotated out before it was used.
 Yes. The plugin's event log already stores the IP attached to each token issuance and use, and SleekView surfaces them as sortable columns. Repeat issuance from one IP reads at a glance.
 Yes. The rotate and revoke actions route through the plugin's token API, the same path the user profile screen uses. No direct table writes bypass the integration.
 Apply a date filter and the CSV inherits it. Compliance reviews get the rescue register for the exact window without an additional export step.
 Yes. Each subsite has its own usermeta and options, and SleekView respects that scope. A network-level view rolls tokens up across blogs for the security team that monitors a whole network.
 The plugin's event log is bounded to recent events by design and rotates older entries. SleekView paginates the rows it does load, so the grid stays responsive even when the log carries thousands of events.
 Yes. The IP and matched user already fall under the WordPress privacy exporter surface, and SleekView CSV exports inherit the same fields. Subject-access requests continue to be served by the plugin's existing exporters.
 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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Woocommerce Laybuy
- Samcart Bridge
- Edd Fes Frontend Submissions
- Surecart
- Woocommerce Multistore
- Mollie Payments
- Wpc Buy Now Button
- Product Vendors Marketplace
- Woocommerce Correos
- Woocommerce Klarna Checkout
- Edd Stripe Marketplace
- Woocommerce Quote Request
- Woocommerce Invoice System
- Woocommerce Bitpay
- Woocommerce Grouped Products Pro