Form Locker writes per-entry context to wp_wpforms_entry_meta, typically including the locker mode at submit time and any password-challenge result. The exact meta keys depend on the add-on version; SleekView's column picker reads what's there. Form-level settings (the locker mode definition) live on the wpforms form post.

Failed password attempts don't create entries (the submission was blocked), so they aren't in wpforms_entries. If your installation logs failed attempts elsewhere (a security plugin, a custom hook), that data is separately queryable. SleekView surfaces the successful-attempt context: which password challenge each entry passed through.

SleekView computes the count per form against the configured limit (read from the form's locker settings on wpforms post-meta). The percentage-of-cap column updates as new entries land. For caps that close after a threshold, the column flips to a red state once the limit is reached, making the closure visible at a glance.

No. Locker settings live on the form post and are edited through the form builder; that's where validation and the form-wide settings UI exist. SleekView's inline edits are scoped to entry-side fields (the captured submission data and entry meta). Settings stay in their canonical UI.

Form Locker enforces uniqueness; only one entry per user/email/IP lands in wpforms_entries. SleekView shows the one entry per user as a row, with the locker mode indicating the uniqueness rule. Attempts to re-submit get blocked before an entry is created, so the audit is on accepted entries only.

Form Pages is a separate add-on that affects rendering; Form Locker affects access. Entries from a Form-Pages-rendered locked form still hit wpforms_entries and pick up the same locker meta. SleekView's view works the same regardless of whether the form was rendered inline or via Form Pages.

Yes. Locker meta records that the entry was accepted within the scheduled window. SleekView filters on the window meta (start/end timestamps if the add-on writes them) so you can confirm every entry was submitted in-window, useful for time-restricted promotions and competitions.

Form Locker's IP-based modes (when configured) record the accepted IP into entry meta. SleekView surfaces it as a column for audit; for privacy reasons, the column can be restricted to admin roles only via SleekView's per-view scoping, keeping it out of marketing-facing saved views.