No. The default WordPress Users screen stays exactly as it is. SleekView sits alongside as its own admin page, optimized for moderation rather than general user listing. Most teams pin the SleekView grid as the moderator landing page and leave the default screen for occasional one-off lookups. Removing SleekView leaves your users, roles and TML state untouched.

From two sources combined — Theme My Login's own audit fields when you have its logging features enabled, plus standard WordPress login and login_failed action hooks that SleekView listens to. The combined feed gives you last login timestamp, last login IP and failed-attempts-today as live columns. Sites without TML logging still get the WordPress-side fields; sites with it get the richer set.

Yes. Restrictions, Profiles, Moderation and Custom User Links extension fields all appear as columns when present. Each is typed (string, boolean, datetime) so the right filter operators show up automatically. If you add a TML extension later, its fields surface in the column picker without any reconfiguration on the SleekView side.

Yes. Per-role row scoping limits which users support staff can see (for example, only subscribers and customers, never administrators or editors). Column-level read-only flags lock down sensitive fields — role assignment, capability changes, email addresses if you want — so support can approve and unlock without escalating their WordPress role to administrator.

Yes. SleekView reads from wp_users, TML's storage and the standard login hooks. It does not care which front-end pages handle the actual login form. Whether you use TML's default templates, fully custom theme templates or a page builder block, the moderation grid sees the same users and the same activity. Multi-page or multi-step login flows work identically.

Yes. Each site keeps its own users grid, its own saved views and its own moderation queue. Network admins can also configure a network-wide view that aggregates across sites, useful for sites where members might register on one and access content on another. Per-site capability checks still apply, so a network super-admin sees everything while site-level moderators see only their site.

Email addresses and IP fields are treated as personal data, so they can be masked by capability or hidden from CSV exports for users without the right role. Audit logs and moderation history do not leave the database — SleekView reads existing data, it does not create new logs of its own. If you need a user erased under a deletion request, the standard WordPress and TML deletion flows still work.

Yes. Bulk approvals run through TML's normal approval flow, which means the welcome email, password setup link or whatever email you have configured fires per user. Same for password resets and account locks. SleekView does not bypass the email layer; it just lets you call into it for many rows at once instead of clicking through them individually.