No. RCP's Reports remain the right place for the canonical rollups. SleekView Charts adds a free-form dashboard layer that reads the same custom tables, so the team can build the non-canonical charts that the operational workflow actually needs.

Yes. rcp_memberships has a recurring flag column. Filter or group any card by that flag to split the dashboard into recurring versus one-time cohorts, which usually reveals different retention curves and different revenue patterns.

Add an Area or Line card grouped by date with the payments filtered to status equals failed. The card plots failed-payment count or summed amount per day, surfacing the trend month over month for finance reviews.

Yes. A dashboard-wide filter on object_id (the level ID) applies to every card on the canvas, so a per-level view becomes one toggle. Individual cards can also override the dashboard filter where needed.

Yes when the add-on uses standard SQL columns. SleekView reads any registered table as a generic data source, so add-ons that follow RCP's storage conventions appear as additional chart sources without extra configuration.

Yes. Chart aggregations use RCP's existing indexes on date, customer_id, and gateway. A payment history with hundreds of thousands of rows aggregates in under a second for typical groupings, and saved layouts cache results across reloads.

Yes. Click a Donut segment, Bar column, or Area band to open the matching filtered Table view. The drill-through preserves any dashboard filters, so the resulting row-level view is the same slice that the chart segment represented.

Yes. Each subsite has its own RCP tables (or the network-wide tables when configured network-wide), and SleekView reads the current subsite by default. Network-wide chart dashboards are configurable when the membership data legitimately spans subsites.