Live. SleekView queries the same wp_termly_consents and wp_termly_settings tables the Termly dashboard reads. Filters apply at the SQL level, so a board scoped to the last seven days reflects records that landed in the last seven days, not yesterday's snapshot exported elsewhere.

No. SleekView writes a review workflow tag into the Termly metadata. External notification destinations like email, Slack, and webhooks keep operating on the original record, so the tag never replays an alert, never suppresses one, and never alters the metadata that mirrors already sent.

Yes. The site_id column on every Termly row tags records with their originating subsite. SleekView exposes that field as a filter and a board grouping option, so a network admin can scope to a single subsite or split each subsite into its own column for focused triage.

Yes. Every move runs through current_user_can('manage_options') and the Termly admin capability before any metadata write. A contributor account can drag for personal sorting but the change does not persist, with a toast notification explaining why the move was rejected by the system.

Filters are applied at the database query level rather than in JavaScript. A typical board scopes to the last seven days, to one severity, or to in-progress states only, so the rendered card count stays under a thousand. Older records remain queryable in archive views without slowing the live board.

Yes. Severity lives on wp_termly_consents and supporting context lives in wp_termly_settings. SleekView exposes both as card fields, so an analyst can spot repeat patterns across high severity records and queue them for action without leaving the kanban board for separate queries elsewhere.

Yes. Premium features add external destinations, reports, and search filters. SleekView reads the same metadata fields, so premium features like file integrity monitoring and external session tracking surface their consent visits on the same board for unified triage across the workflow.

Yes. Every drag writes a review entry into the Termly metadata naming the user, source column, destination column, and timestamp. The entry uses the Termly metadata API so audits, exports, and downstream automations can read the trail without needing a separate event log table.