Yes. Magic Login Pro extends the schema with additional columns for branded emails, expiration overrides, and per-role link lifetimes, and SleekView picks up new columns when you re-scan the table. The same masking, filtering, and preset features work; you just have more metadata fields available for filters and sorts.

Yes. Token state is a filterable column with values for pending, used, expired, and revoked. A common audit preset filters to expired in the last 30 days and groups by user, which surfaces both staff who never use their links and users whose mail flow may be silently failing for some other reason.

No. Token values are masked by default and only the metadata, meaning user, IP, issued and used timestamps, and result, is shown. If a security investigation needs the raw token, it can be unmasked for a specific role temporarily, but the default and the CSV export keep it hidden so the table can be embedded for compliance staff safely.

Yes. Use a custom capability mapped to a compliance role and the frontend embed to give read-only access to the table without granting full WordPress admin. The embed respects the same filters and presets as the admin view, so an auditor lands on a dashboard scoped to exactly the data they are entitled to see.

Yes. On a multisite network, you can scope the view to a single subsite by site_id or aggregate across the network with a site column visible. That pattern is useful for managed WordPress hosts where one network houses many client sites and a single security team reviews all of them.

Yes. Bulk delete fires Magic Login's revocation hooks rather than touching the database directly, so any custom integrations or audit listeners run as expected. That preserves the integrity of the audit trail itself: a revoked token leaves a record of who revoked it and when, not just an empty row.

Indirectly, through scheduled CSV exports or REST. The Magic Login token table is a normal WordPress table, and SleekView's filtered exports can be pushed to S3 or pulled by Splunk, Datadog, or a generic SIEM through standard means. The data shape is straightforward enough that mapping is a one-time job rather than ongoing engineering.

That depends on Magic Login's own retention configuration plus your data policy. SleekView does not change retention; it surfaces what is in the table. If your policy requires 12 months of authentication logs for SOC, configure Magic Login to keep tokens at least that long and run a periodic CSV export as a secondary archive in case retention shortens later.