Yes. The cards read from the rua_level custom post type and the user meta rows RUA writes per assignment. Each chart uses the same level slug, start timestamp, and expiry timestamp the plugin's own API exposes, so the dashboard reflects the live access model without an export step.

Yes. Each card supports a filter on the WordPress role or the level slug. A support-team view scoped to Gold renders the renewal-risk bar for Gold members only; an admin view shows the full level mix across the roster.

Yes. The same data source feeds both, so an inline assignment edit in the table view updates the charts the next time they render. The charts are a second presentation layer over the same RUA tables, not a separate dataset.

The expiry bar groups members by week relative to the current date. Week one covers expiries in the next seven days, week two covers eight to fourteen days out, and so on. The bucketing is configurable per saved view so retention teams can pick weekly or daily granularity.

Yes. Extension add-ons like the BuddyPress integration and the Meta Box restriction write their config to the level posts and to standard user meta. The charts read whatever fields are present, so add-on metadata can become its own chart card without configuration.

Yes. Each WordPress role keeps its own saved dashboard layout. Support sees the renewal-risk donut by default; admin sees the full level mix; auditors see the assignment timeline. Saved layouts ship per role without rebuilding the cards.

Charts query the live rua_level CPT and user meta on each render with paginated reads. The result is the same level mix RUA's own API would compute, refreshed every time the dashboard loads.

Yes. Queries use the indexed user_id column on user meta and the standard post type index on rua_level. Sites with tens of thousands of members across dozens of levels render the dashboard in well under a second.