✨ 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 Uncanny Toolkit: module activity and settings as tables

Uncanny Toolkit ships dozens of modules covering login, registration, admin, and front-end UX. Several modules persist activity to options and custom keys. SleekView reads what each enabled module stores and turns it into a sortable, filterable grid.

♾️ Lifetime License available

SleekView table view for Uncanny Toolkit

Toolkit modules, surfaced as columns

Uncanny Toolkit and Toolkit Pro bundle a long list of opt-in modules that change WordPress behavior: front-end login forms, custom registration flows, admin tweaks, password resets, redirects, and access controls. Each enabled module persists its own slice of data, typically into wp_options, user meta, or a small module-specific table when activity logging is part of the module.

The default Toolkit admin lets you toggle modules and configure each one in isolation, but it does not present module activity as data. To see which login redirect rules fire most often, which registration captcha module catches the most spam, or which admin tweak is currently active per user role, the team has to read settings screens module by module.

SleekView reads the underlying option keys, user meta, and module-owned tables and presents them as joined columns in one grid. A login activity view shows recent logins by user with the redirect rule that fired and the source IP. A registration view groups signups by source form and outcome. A modules-overview view lists every active module with its last update timestamp and capability scope. The data is whatever the modules already store, surfaced as a working table instead of buried in nested settings pages.

Workflow

From scattered settings to one module dashboard

1

Pick the data source

Module-owned tables, option keys, and user meta. SleekView lists every storage location the active Toolkit modules expose so columns come from data that is actually present.
2

Compose the columns

User, role, module, outcome, IP, timestamp. Or for an overview view, module name, scope, last update, and capability. Aggregate columns compute in SQL where useful.
3

Save the views

Pin one view for recent logins by module, one for registration outcomes by form, and one for active modules by scope. Each view is gated by capability and persists per user.
4

Hand off to ops

Filter the relevant slice and export to CSV. Membership operators get the signup grid, security gets the login grid, and the modules-overview view goes straight into the next audit document.

Sample columns

A typical Uncanny Toolkit login activity view

Login events with user, role, redirect rule, source IP, and timestamp.
Source: Uncanny Toolkit option keys, user meta, and module-owned activity tables
User Role Module Result IP Time
iris subscriber Front-end Login success 203.0.113.7 2026-04-25 14:22
milo customer Front-end Login redirect 198.51.100.5 2026-04-25 14:14
june (unknown) Custom Registration captcha fail 192.0.2.91 2026-04-25 13:58
ash editor Admin Login Logo success 203.0.113.12 2026-04-25 13:30

Comparison

Default Uncanny Toolkit admin vs SleekView

Default Toolkit screens

  • Modules configured one by one with no cross-module activity view
  • Module activity sits in options and user meta with no admin grid
  • No filtering of recent logins by module or redirect rule
  • Registration outcomes are not aggregated across forms
  • Settings drift between modules cannot be compared at a glance

SleekView

  • Module activity surfaced from options, user meta, and module tables
  • Filter by module, role, or outcome
  • Sort by timestamp or login count
  • Saved views for login activity, registration outcomes, and active modules
  • CSV export for handoff to ops or compliance

Features

What SleekView gives you for Uncanny Toolkit

Login activity

Pull the front-end login module's activity into a grid with user, role, redirect rule, and IP. Filter to failed attempts to spot a brute-force pattern before it shows up in support tickets.

Registration outcomes

Group registration events by source form and outcome to see which signups produce real users versus mostly captcha failures. Optimize the form that is actually working.

Module overview

List every active Toolkit module with its scope, last update, and the role it applies to. Easy spot-check during audits, instead of clicking through dozens of settings screens.

Audience

Who uses SleekView for Uncanny Toolkit

Membership operators

Review login and registration activity in one grid filtered by membership tier. Confirm new signups landed on the right role and the redirect rule fired without browsing each module's settings.

LMS administrators

Pair Toolkit modules with LearnDash and surface student login history alongside the redirect rule that sent them to the right course on each session.

Site administrators

Audit which Toolkit modules are active across the network, what their scope is, and when each was last updated. Useful before annual security reviews and before activating a new module on staging.

The bigger picture

Why bundled modules need a unified surface

Uncanny Toolkit's value is breadth: a single plugin replaces a long list of small utilities a membership site or LMS would otherwise install one by one. The cost of that breadth is fragmentation. Each module ships with its own settings screen, its own scope, and in many cases its own slice of activity data.

The site is configured well, the modules are doing their job, and yet answering routine questions, which login redirect fired most yesterday, which signup form caught the most captcha failures, which admin tweak is currently active for editors, requires opening twelve nested settings pages and reading them in sequence. None of the data is hidden. It is just spread out.

A grid that reads option keys, user meta, and module-owned tables together, and exposes them as filterable columns, gives membership operators, LMS admins, and security leads a working surface that matches how they actually use Toolkit. The plugin keeps doing what it does best, and the team finally has somewhere to look at the result.

Questions

Common questions about SleekView for Uncanny Toolkit

No. Logging depends on which modules are active and how each is configured. Some modules write activity into options or user meta, others write into a module-owned table, and others do not log at all by design. SleekView reads whatever the enabled modules already persist.

 

Yes, when a Toolkit module that records logins is active and storing the data. The grid surfaces user, role, redirect rule, source IP, and timestamp as filterable columns, sourced directly from where the active module already keeps that activity.

 

Yes, when a Toolkit registration or signup module is active and writing outcomes to options, user meta, or a module table. Group by source form to see which signup flow actually produces real users versus mostly captcha failures.

 

No. The Toolkit admin remains the place to enable, configure, and update each module. SleekView complements it for cross-module visibility, surfacing module-stored data as one grid rather than as settings pages opened one by one.

 

Yes. Role is a filterable column on every activity grid sourced from user meta. Scope to subscribers to review free-tier signups or to editors to audit higher-privilege logins, without touching the Toolkit settings screens.

 

Inline edits write through standard WordPress update paths for posts, options, and user meta. Module hooks fire normally where the underlying field is something Toolkit watches. For activity tables that are intended as audit logs, leave inline editing off to keep the trail honest.

 

Yes. Filter the grid, then export to CSV. Visible columns only, which keeps exports tight for compliance handoffs and avoids leaking module-internal flags unless you explicitly choose to include them.

 

Yes. Pro modules add more option keys, user meta, and in some cases their own tables. SleekView lists those as available data sources alongside the free Toolkit, so a Pro membership login module shows up in the grid the same way the free login module does.

 

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