A dashboard site is the web-hosted version of your dashboards: a canonical URL, a stable bookmark, a shareable link that respects permissions. Strkr's hosted dashboards work in any browser, embed in any wiki, respect your identity provider, and never require an app download or a desktop plugin.
A dashboard site is not an app you launch. It is a URL you bookmark. Open the browser, type the first letter, hit enter. The dashboard renders in a few seconds with the current data and your audience filters applied. The web as a destination means the dashboard is one click away, not three app launches away.
Each dashboard carries a canonical URL. The URL does not change across edits, publishes, or audience changes. A bookmark saved in January works in December. The team's shared references stay stable.
The dashboard site runs in every modern browser without plugins or extensions. The organization's standard browser works. The dashboard respects the browser's native features: bookmarks, history, right-click, keyboard shortcuts.
The dashboard site renders anchor numbers in under a second after navigation. The browser caches the layout. Subsequent visits are instantaneous. The team does not wait for an app shell to boot.
Dashboard URLs carry filter state in the query string. A link to Pipeline filtered to the Southeast for Q3 opens exactly that view. The sender bookmarks a slice; the receiver lands on the same slice. No reconfiguration required.
The dashboard respects browser back and forward buttons. A reader who drills into a record and hits back lands on the dashboard with the filter preserved. The dashboard behaves like a native web page, not an SPA that fights its container.
Any URL pasted into Slack, email, or a wiki renders a preview card with the dashboard title and anchor numbers. The receiver clicks and lands on the dashboard with permissions enforced. Sharing is as simple as paste.
A dashboard site must respect the organization's identity provider. Strkr's site integrates with SSO providers, inherits group membership, and enforces session policies. The team logs in once and dashboards open with the right permissions. No second password. No forgotten credential ticket.
The dashboard site accepts SAML 2.0 and OIDC-based identity providers. Okta, Azure Entra, Google Workspace, Microsoft 365, OneLogin, Ping Identity. The provider lands the user into the site with the correct identity attached.
Groups declared in the identity provider map to roles in Strkr. The Sales group lands into the AE role. The Executives group lands into the leader role. The admin maintains the mapping once. Role changes propagate automatically.
The admin configures session timeouts, device limits per user, and re-auth prompts for sensitive dashboards. The policies enforce at the site level. The user experiences the policies as the organization intends.
Multi-factor authentication enforced by the identity provider carries into the dashboard site. The site does not re-prompt. The user authenticates once at the provider and inherits MFA into every protected page.
When a new hire logs in through the identity provider for the first time, Strkr provisions their account automatically with the right role based on IdP group membership. Onboarding does not require a manual Strkr setup.
When the identity provider deprovisions a user, Strkr immediately revokes dashboard access. Shared links the departed user generated expire. The organization's offboarding is a single action at the identity provider.
The dashboard site does not demand that readers come to it. Dashboards embed into the organization's intranet, wiki, customer portal, or internal landing page. The reader stays in the host site and sees the live dashboard rendered inline. Permissions enforce. Branding adapts. The dashboard travels where the reader already works.
The dashboard produces an iframe embed snippet. The admin pastes it into Notion, Confluence, SharePoint, WordPress, a custom CMS. The dashboard renders live inside the host page with permissions honored.
Embedded dashboards wear the host organization's brand: logo, accent color, type scale. The reader does not experience a context switch. The embedded surface reads as part of the host, not as an obvious third-party frame.
The iframe embed resizes to fit its container with no scroll bars. A dashboard embedded in a narrow sidebar compresses to a single column. The host page controls the frame; the dashboard adapts.
Embedded dashboards can inherit the host site's authentication through SSO cookies or signed JWT. The reader logs into the host once; the dashboard reads their identity automatically. No separate login flow.
Dashboards embed into client-facing portals so customers see their own data: usage, outcomes, next-step reports. Row-level security applies per customer. The product company offers a dashboard experience without building one themselves.
Admins see every embed in use with the host page, the dashboard, the first-render date, and the last-render date. Unused embeds retire. The organization's external surface stays mapped and governed.
A dashboard site with ten dashboards is readable. A site with a hundred dashboards needs navigation. Strkr's site organizes dashboards into collections, favorites, recents, and search. The team finds what they need in two clicks. The site remains navigable as the organization's dashboard count grows.
Dashboards group into collections: Sales, Service, Marketing, Finance, Product, Operations. Each collection carries its own landing page with the dashboards in the group. The organization's dashboard surface is browsable, not just searchable.
Each user pins favorite dashboards to the top of the site navigation. The reader lands on the site and sees their frequent dashboards first. Favorites persist across devices through the user profile.
A recents list surfaces the five most recent dashboards the user opened. For readers who follow a weekly cadence, recents are faster than favorites. The site remembers what the reader actually uses.
A global search box jumps to any dashboard by title or by metric. The reader types pipeline and sees every pipeline dashboard across every collection. Keyboard shortcut opens search from anywhere on the site.
Every dashboard carries breadcrumbs: Collection, Dashboard, Current filter state. The reader always knows where they are. Clicking a crumb returns them to the parent level. Deep navigation stays navigable.
Dashboards carry tags for business dimension (region, segment, product line), audience (AE, VP, exec), and cadence (daily, weekly, monthly). The reader filters the sitemap by tag. The organization's dashboard sprawl stays navigable.
A slow dashboard site is an unused dashboard site. Strkr engineers for speed: fast first paint, smart caching, incremental loading, and a CDN posture that serves dashboards from a region close to the reader. The reader opens the site and the dashboard reads in the time it takes to settle into a chair.
The site renders the dashboard shell in under a second. Anchor numbers appear immediately, with trend charts rendering as data arrives. The reader starts reading before every tile has finished loading.
The site caches dashboard layouts and static assets at the browser level. Return visits render instantly. Data refreshes against the server while the layout stays local. The reader never waits for the chrome.
Dashboards with many tiles render the above-the-fold tiles first. Below-the-fold tiles load as the reader scrolls. The initial read is fast; the full dashboard arrives as the reader needs it.
Static assets serve from a CDN with edges close to the reader's location. A reader in Tokyo gets the same experience as a reader in New York. The dashboard site respects the global shape of modern teams.
The site queries multiple tiles in parallel against the data backend. A dashboard with twelve tiles does not wait for twelve sequential round trips. The reader's total load time matches the slowest tile, not the sum of them.
A tile that fails to load renders a visible error state and the dashboard continues. The reader sees eleven tiles and one with a readable error. The maker gets a notification. The dashboard never becomes a blank page because one query failed.
A dashboard site that wears a vendor's brand feels like a third-party portal. Strkr's site wears the tenant's brand: logo, accent color, type scale, custom domain. The dashboard surface reads as the organization's own property. For enterprise customers surfacing dashboards to clients, the brand fit matters.
Each tenant uploads a logo that renders in the site header, the dashboard chrome, and the exported PDFs. The dashboard site reads as the organization's surface, not a vendor product with a borrowed logo overlay.
The tenant's brand accent applies to buttons, highlights, chart interactive states, and selected filter chips. The signal palette (green, amber, red for state) remains functional. Brand accent complements rather than replacing the signal palette.
The site respects the tenant's declared type pair. Headings use the brand's display font. Body uses the brand's body face. The reader experiences a consistent typographic voice across the dashboard and the rest of the organization's surfaces.
Enterprise tenants point a custom subdomain at the dashboard site: dashboards.yourcompany.com. The URL belongs to the organization, not to the vendor. Bookmarks and shared links wear the organization's domain.
Each tenant uploads a favicon that renders in the browser tab. The reader with ten tabs open spots the dashboard by its icon. Small polish; big impact on daily usability.
The site footer carries configurable lines: a compliance notice, a confidentiality stamp, a contact for data concerns. The admin configures once per tenant. Every dashboard page carries the organization's required footer language.
The web-hosted surface where dashboards live: a canonical URL per dashboard, browser-native rendering, SSO-backed identity, embed options for other sites, and a navigation structure that scales from ten dashboards to a thousand.
No. The dashboard site runs in any modern browser without plugins, extensions, or app downloads. The organization's standard browser is sufficient. Mobile users can save the site to their home screen for app-like access.
Yes. Enterprise tenants point a custom subdomain (dashboards.yourcompany.com) at the Strkr dashboard site. Bookmarks and shared links wear the organization's domain. The site also inherits the tenant's brand (logo, accent color, type scale).
The site integrates with SAML and OIDC identity providers (Okta, Azure Entra, Google Workspace, Microsoft 365, and others). Group membership in the IdP maps to roles in Strkr. MFA enforced by the IdP carries into the site. Just-in-time provisioning handles new users on first login.
Yes. Embed snippets drop into Notion, Confluence, SharePoint, WordPress, and custom CMS platforms. Dashboards render live with permissions honored, dynamic resizing, and optional pass-through authentication from the host site.
Yes. Strkr is HIPAA compliant with a BAA available, pursuing SOC 2 Type II with completion targeted through 2026-Q4, GDPR, and CCPA compliant. The site enforces row-level security, field masking, audit logs, session controls, and IP allowlists at the tenant level.
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.
