No. SleekView only reads wp_posts rows and _wordhero_* postmeta that WordHero already wrote. Every WordHero generation still goes through the plugin with the account login and per-user limits the plugin 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 wp_posts joined to wp_postmeta on the _wordhero_* keys. The reads happen in milliseconds and stay out of WordHero's way.

Yes. Every WordHero draft is a wp_posts row with a post_author column. SleekView Charts can group by post_author and resolve it against wp_users to rank editors by draft count or by total _wordhero_tokens across any date range.

Yes. WordHero stamps the active template name into _wordhero_template on every draft. SleekView Charts reads that postmeta directly, so the donut and bars include any custom templates your team made, alongside the built-in ones.

Yes. SleekView dashboards have a role scope. Save the WordHero 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 look at draft titles.

Only if the plugin renames the postmeta keys SleekView is reading. The _wordhero_template, _wordhero_tokens, and _wordhero_run_id keys have stayed stable across releases, and SleekView shows a clear error and lets you re-map a key 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 WordHero numbers without ever logging into the WordHero plugin or web app.

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