No. SleekView only reads rows from dcwp_logs and the DALL-E attachment postmeta the plugin already wrote. Every OpenAI or DALL-E call still goes through the plugin with the keys, models, and limits it manages, so the dashboard never adds usage.

No. SleekView caches each chart card for the duration you set on the source and runs indexed group-by queries against dcwp_logs and wp_postmeta. The reads happen in milliseconds and never block the plugin from writing new prompt or image rows.

Yes. dcwp_logs writes both feature types into the same table with the type column distinguishing them. SleekView can chart them on one dashboard, separate them with two cards, or filter a single card down to one type with a where clause.

Yes. The plugin records the prompt text and any preset identifier alongside the model on every row. SleekView can group by model or by preset name in the same way, so custom presets show up next to the built-in ones on the donut and the bars.

Yes. SleekView dashboards have a role scope. Save the AI dashboard for editor or content_lead and only users in that role see it, so writers don't see token costs and finance doesn't have to read prompt transcripts on the editor screen.

Only if the plugin renames the columns or postmeta keys SleekView is reading. The dcwp_logs shape and the _dcwp_prompt and _dcwp_model keys have stayed stable across releases, and SleekView shows a clear error if anything changes.

Yes. Every saved chart view has a shortcode and a block. Drop it on a frontend dashboard page, scope the page to a client role, and the client sees the AI numbers without ever logging into the plugin Logs screen or the Media Library.

Yes. Every SleekView chart card has a CSV export that pulls the same rows the chart was built on. Use it to hand finance a monthly token-spend file or feed an external BI tool directly, without touching the plugin tables by hand.