Directly from Tweetly Pro's queue table and send-log entries, joined to wp_posts on the originating post id and to standard columns like post_status, post_author and post_date. No exports, no shadow copies and no extra Twitter or X API calls happen because the plugin already wrote each row when the send occurred.

Yes. Each queue row and log entry is tagged with the connected account that produced it, so account becomes a dropdown filter with one option per connected handle. New accounts appear as new filter values automatically once their first send lands.

Yes. The recycle flag is a column on the queue and log rows, so a single filter narrows the table to recycle activity. Useful for confirming the recycle rule is producing the expected volume without scrolling past fresh-post sends.

Inline edits in SleekView route through the same update path Tweetly Pro uses internally, so the plugin's hooks and scheduler fire the same way they would from its own admin screen. Changing a status or reassigning a schedule rule keeps the plugin in charge of the actual send.

No. Queries hit indexed columns on Tweetly's queue table (status, account, sent_date) and on the joined wp_posts rows. Filters compose into a single SQL query, so even multi-year send history paginates fast.

No. The table reads the queue and log Tweetly Pro already maintains. Sending stays the plugin's job through its own scheduler and API client, and SleekView is a read-only surface over the data Tweetly already wrote.

Yes. Any filtered view can be exported to CSV with the same columns the table shows, including account, status, recycle flag and sent timestamp. Social ops typically use this for the weekly distribution report or to brief an external agency.

No. Tweetly Pro still owns the scheduler, the API client, the per-post tweet template metabox and the send path. SleekView adds a site-wide audit table on top of the data Tweetly already writes, so the plugin keeps doing the scheduling work and the table view handles the cross-queue reporting.