Feature · Dynamic Dashboards

Dynamic dashboards that reshape to the viewer without admin sprawl.

Dynamic dashboards are what a static dashboard becomes when it actually earns the "dynamic" label. That means role-keyed layouts, per-user filter overlays, live record reads, drill-through to the underlying rows, and aggregation that honors CRM permissions, all without turning into a sprawl of 400 hand-maintained copies. Strkr ships dynamic dashboards where admin keeps the base template and users layer their filters on top. The dashboard reshapes to the viewer, not to the admin's most recent panic request.

Start free trial See pricing
What dynamic actually means

The eight axes along which dashboards flex.

A dashboard called "dynamic" because the user can change the date range is static with one bonus knob. Real dynamic dashboards flex along multiple axes, and the axes below are the ones real teams need. A dashboard that covers all eight stops being a BI project and starts being a daily tool.

Viewer axis

Different roles see different panels.

The rep sees their open deals, today's activity, and this quarter's quota. The sales lead sees pipeline health, forecast variance, and rep ranking. The CFO sees committed revenue, discount flow, and ARR. One dashboard template, four materialized views, zero duplication.

Filter axis

Per-user filter overlay on the base.

The base layout belongs to admin. Each user layers filters on top: territory, segment, product, date range. The user's overlay persists on their session, does not leak to other users, and does not corrupt the base. The common failure where a rep applies a filter and the VP sees the filtered view does not happen.

Time axis

Last-N windows, period compare, YTD.

Time filters support last-7-days, last-30-days, QTD, YTD, custom range, and period-over-period compare. Period compare is a toggle that overlays prior-period on the current chart. The common failure where "compare to last quarter" requires a one-off report does not happen.

Record axis

Panels filter by account, deal, project.

Panels can scope to a record. A dashboard on the Account record shows deals, activity, tickets, and health scoped to that account. The dashboard template is the same for every account; the record ID is the filter.

Drill-through

Click the number, open the rows.

Every number on the dashboard drills to the underlying rows. A rep clicks the "12 open deals" tile and the opportunity list opens filtered to those 12. A CFO clicks "committed Q3 ARR $4.2M" and the opportunities roll up visible, inline, with the deal owner.

Permission axis

Aggregation honors CRM permissions.

The aggregation respects the viewer's CRM permissions. A rep sees pipeline for their deals; the sales lead sees pipeline for their reports; the CFO sees everything. The common failure where a rep sees aggregate numbers that include deals they cannot see does not happen because the aggregation runs under the viewer's permission context.

Refresh axis

Live reads, no sync lag.

Panels read live from the record. A deal that moves to Closed-Won at 10:14 AM shows on the forecast tile at 10:14 AM. The common failure where the dashboard shows yesterday's data and the sales lead is debating with the rep about numbers from different snapshots does not happen.

Comparison axis

Overlay this quarter vs last.

Comparison overlays this period against prior periods on the same chart. A trend line of pipeline velocity shows this quarter and last quarter overlaid for pattern-matching. The common failure where "did velocity get better" requires a one-off report does not happen.

Where dashboards differ

Six axes that separate dynamic from "fancy static".

Dashboards that call themselves dynamic in the product literature often ship a date-range selector and little else. The axes below separate real dynamic dashboards from marketing-page dynamic dashboards. A buyer who scores on these axes avoids the shelfware tier.

Template vs copy

One template, many materialized views.

Platforms with a template-and-overlay model let one template serve 50 roles with no copy sprawl. Platforms where "dynamic" means "the user clones the dashboard and edits it" end up with 400 hand-maintained copies by month six. The template model is the only sustainable approach.

Permission model

Shared with CRM vs invented.

Dashboards that share the CRM permission model avoid the whole class of bugs where aggregate numbers leak data a user cannot see. Dashboards that invent their own permission layer end up with "the chart said $8M but my records only sum to $2M" problems. The authorization is the design.

Refresh model

Live reads vs batch snapshot.

Dashboards that read live from the record stay in sync with the deal that moved five minutes ago. Dashboards that batch-snapshot the data every N hours lag behind the record. The lag question matters when the sales lead and the rep are debating the forecast in a live meeting.

Drill depth

Row-level drill vs chart-only.

Dashboards that drill to the underlying rows let the viewer answer "which deals are in that bucket" in one click. Dashboards that stop at the chart force a tab switch to a report builder. The drill depth is the single biggest driver of the "do people actually use this" question.

Scope

Record-scoped vs org-scoped only.

Dashboards that can scope to a record (account, deal, project) are useful on the record detail page. Dashboards that only work at the org level force users back to the report builder for record-specific views. Record-scoped is a prerequisite for being a daily tool.

Pricing shape

Flat seat vs per-user-view meter.

Flat-seat dashboards let the ops lead ship role-keyed layouts for every team without a budget conversation. Per-view or per-dashboard-user meters penalize the teams that get the biggest ROI from the dashboard surface. The pricing shape predicts the vendor relationship.

What Strkr ships for dynamic dashboards

The dashboard surface, in detail.

Template-and-overlay model. Role-keyed layouts. Per-user filter overlay. Record-scoped and org-scoped templates. Live reads with sub-second refresh. Permission-aware aggregation. Drill-through on every number. Period compare. Flat $50 per seat with no per-query meter.

Template engine

Admin owns the base, users overlay.

Admin ships a dashboard template. Users layer their filters on top. The admin can update the base template without blowing away user overlays. The common failure where admin changes break every user's saved view does not happen because the overlay model is additive.

Role keying

Rep, lead, VP, CFO layouts in one template.

The template keys panels to roles. A rep layout shows deals and activity. A lead layout shows pipeline health and ranking. A VP layout shows forecast and variance. A CFO layout shows ARR and discount flow. All four materialize from one template, zero duplication.

Filter overlay

User filters persist per session.

Users apply filters to the base layout and save their overlay. The overlay persists per session, does not leak to other users, and does not corrupt the base. A user with multiple saved overlays can swap between them in one click.

Record-scoped

Dashboards on Account, Deal, Project.

Dashboards can scope to a record. The Account record shows an account-scoped dashboard with deals, activity, tickets, and health. The Project record shows a project-scoped dashboard with sprint burndown, deliverables, and budget.

Drill-through

Click number, open rows.

Every number drills to the underlying rows. A click on "32 open deals" opens the opportunity list filtered to those 32. The user sees the deal owner, stage, close date, and value inline. The drill is the dashboard's most-used interaction.

Period compare

Overlay this period vs last.

Comparison overlays this period against prior periods on the same chart. Pipeline velocity, forecast coverage, win rate, and deal size all compare period-over-period in one toggle. The compare is primary, not a BI add-on.

Where teams actually land

Four deployment patterns from real customers.

A 50-seat SaaS, a 180-seat services firm, a 350-seat healthcare company, and a global company with multi-geo pipeline each run dynamic dashboards. The template engine is shared; the role layouts flex to the business.

SaaS pattern

Rep home is a dashboard.

A 50-seat SaaS runs a rep-home dashboard with today's activity, open deals, this quarter's quota, and the top three deals at risk. The dashboard is the first thing the rep opens every morning. Admin ships template updates monthly; rep overlays persist.

Services firm

Project dashboard per project.

A 180-seat services firm ships a project-scoped dashboard on every project record. Burndown, deliverables, budget vs actual, and the account-level NPS all materialize from one template. The practice lead can see 40 project dashboards without 40 custom builds.

Healthcare company

PHI-safe aggregation on patient data.

A 350-seat healthcare company runs patient-cohort dashboards with aggregation that respects HIPAA permissions. A clinician sees cohort trends for their patients; the regional lead sees cohort trends for their region; the CMO sees everything. PHI never leaks across the permission boundary.

Global company

Multi-geo rollup, per-geo drill.

A global company runs a global forecast dashboard with per-geo rollup. The CFO sees global commit, regional VPs see their geo, country leads see their country. Each drill maintains the permission boundary. One template, five rollup layers, zero duplication.

Ops review ritual

Monthly dashboard review and prune.

Every month, ops reviews dashboard usage: which panels get viewed, which get ignored, which get drill-throughs. Unused panels get retired, high-use panels get promoted to the base template. The dashboard surface stays sharp instead of sprawling.

Exit posture

Dashboard config is portable.

Every template, every role mapping, every panel definition is accessible via the open API. A team that migrates can export the full dashboard schema and reinstate it on another platform. The exit cost is measurable.

Dynamic dashboards that reshape to the viewer, not the admin.

Strkr ships dynamic dashboards with role-keyed layouts, per-user filter overlays, live record reads, permission-aware aggregation, and drill-through on every number. Flat $50 per seat.

Start free See pricing
Common questions

What buyers ask about this feature.

What makes a dashboard dynamic versus just interactive?

Interactive dashboards let the user change a filter or a date range. Dynamic dashboards reshape to the viewer along multiple axes at once: role determines the panel set, record scope filters the data, user overlays layer on top of admin templates, and permission-aware aggregation ensures the viewer sees only what they are authorized to see. The dynamic label is earned by the number of axes the dashboard flexes along, not by a date-range selector.

How does Strkr avoid the sprawl of 400 hand-maintained dashboards?

The template-and-overlay model. Admin owns the base template; users layer filter overlays on top. One template can serve 50 roles with no copy sprawl because the role keying is a declarative rule on the template, not a copy of the template. Admin can update the base template without blowing away user overlays. The common failure where every rep clones the dashboard and the ops team is maintaining 400 forks does not happen because the fork is not necessary.

Does the aggregation leak data to users who should not see it?

No. Aggregation runs under the viewer's permission context, which is shared with the CRM. A rep who cannot read an opportunity cannot have that opportunity's value included in their pipeline total. The common failure where the chart shows $8M pipeline but the user's record access only sums to $2M does not happen because the permission is enforced on aggregation, not just on the record read.

How live is the data?

Panels read live from the record on dashboard load and refresh. A deal that moves to Closed-Won at 10:14 AM shows on the forecast tile when the dashboard refreshes next. Refresh is sub-second for the typical dashboard. The common failure where the dashboard lags behind the record by hours does not happen because the dashboard is not a batch export; it is a query against the live typed record store.

Can dashboards scope to a record?

Yes. Dashboards can be org-scoped (the global pipeline view) or record-scoped (the account dashboard on an account record, the project dashboard on a project record). Record-scoped dashboards use the record ID as an implicit filter. The template is the same for every account; the record ID filter is the thing that materializes different data per account.

How is this priced versus per-dashboard-user BI tools?

Strkr is flat $50 per seat on every tier. Dashboards do not meter per view, per query, per dashboard-user, or per panel. Teams with 200 unique dashboards pay the same per seat as teams with 5. The pricing shape matters because per-view BI meters penalize exactly the teams that use the dashboard surface the most, which is the behavior the tool should reward.

Related features

Pair this with...

Dynamic Dashboard Embedded Dashboards CRM Dashboard Dashboard Platform Dashboard Reporting Software Dashboard Software Business Performance Dashboard

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing