What is an online dashboard and what should it do well?
An online dashboard is a hosted browser-based reporting surface that reads data from a source system and renders KPIs, charts, lists, and funnels for a role. A good online dashboard reads live data (not a stale snapshot), supports interactive filters at view time (team, geography, product, date range), drills through to the underlying records on click, defaults to the right view by role (rep sees pipeline, manager sees team, leader sees organization), produces shareable URLs that encode the filter state, and respects the record-level permissions of the viewer. A dashboard that falls short on any of these dimensions typically produces screens that get built once and abandoned.
How is a CRM-native online dashboard different from a Tableau or Looker dashboard?
The CRM-native dashboard reads from the CRM database directly at view time, while the hosted BI dashboard reads from a warehouse that was populated by a pipeline on a schedule. The lag difference is seconds versus 15 minutes to an hour. The CRM-native dashboard inherits CRM record-level permissions automatically, while the BI tool has a separate permission model that either overshares or requires parallel configuration. The CRM-native dashboard drills through to the source record naturally, while BI tools often lack drill-through to the CRM record detail page. The CRM-native dashboard knows CRM concepts (stage, amount, forecast category) natively, while a BI tool depends on an analyst modeling those concepts in the warehouse.
What dashboards ship as defaults in Strkr?
Six role-keyed dashboards ship as production-grade defaults. The sales rep view shows pipeline, quota, activity, and top-of-mind deals. The sales manager view rolls up the team pipeline, quota, activity density, and risk signals. The RevOps view shows full-funnel conversion, velocity, data hygiene, and automation health. The marketing view shows attribution, campaign ROI, lead quality, and content performance. The customer success view shows account health, renewal pipeline, churn risk, and expansion opportunities. The executive view rolls everything into a one-page summary with ARR, NRR, pipeline coverage, win rate, and sales cycle. The tenant admin clones and customizes any of them.
Can non-admin users author dashboards?
Yes. The dashboard builder is a drag-and-drop surface available to any user with the reports author permission. The RevOps lead or operations manager builds new dashboards without an engineering ticket or an analyst in the middle. Field selectors read directly from the CRM schema, so a new field in the CRM is immediately available in the dashboard. The permission model prevents a user from authoring a dashboard that exposes records they cannot see; the builder respects the authoring user permissions as the floor for any shared dashboard.
How do permissions work on a Strkr dashboard?
Every dashboard respects the record-level permissions of the user viewing it. A rep sees their records on the dashboard; a manager sees the team records; a leader sees the organization records. The dashboard governance matches the record-list governance exactly; there is no parallel permission model to maintain. A dashboard shared via URL respects the recipient permissions; a viewer who cannot see the underlying records sees an empty dashboard rather than unauthorized data. Field-level permissions (restricted fields, PII-masked fields) also apply; a viewer who cannot see a field on the record detail does not see it on the dashboard.
When is a separate BI tool still the right call?
A dedicated BI tool (Looker, Tableau, Mode, Metabase, Power BI) earns its subscription when the reporting target spans three or more source systems (CRM plus product telemetry plus finance plus support data), when the analyst team is sophisticated enough to model warehouse semantics meaningfully, when the dashboard audience includes non-CRM users (data science team, finance team, executive team that would not sign into the CRM), or when the analytics patterns (cohort analysis, retention curves, custom statistical modeling) exceed what a CRM-native dashboard supports. For CRM-shaped reporting the Strkr dashboard surface is typically sufficient; for broader analytics the BI tool complements rather than replaces the Strkr dashboards.
