Table of contents

Fugo's TV Dashboards feature lets you display secure, login-protected dashboards and reports — from Salesforce, Tableau, HubSpot, an internal BI tool, or almost anything else — on a digital signage screen, even when they sit behind SSO, SAML, or multi-factor authentication.

Fugo doesn't "integrate" with your identity provider the way an SSO app marketplace listing would — there's no OAuth handshake, no SAML metadata exchange, nothing to register with your IT team's identity provider admin console. Instead, Fugo drives a real, automated browser session: it opens your dashboard's URL, fills in whatever username, password, and one-time code fields it finds on the page, and takes a screenshot once it's through. Because it works this way — by recognizing and filling in ordinary login fields rather than speaking a specific protocol — it doesn't actually matter whether the login underneath is SAML, OpenID Connect, or a plain username/password form. If the page has fields Fugo can fill in, the login works, regardless of the identity provider's brand name.

This guide explains what that means in practice: which login methods are compatible, how to choose the right setup method for your dashboard, and what the Secret Key field is for.

There are two different mechanisms behind the dashboards you can create in Fugo, and it's worth knowing which one you're using:

When you create a dashboard using one of Fugo's built-in app cards (Salesforce, Tableau, Looker Studio, HubSpot, Zendesk, Jira, and others) or the Custom URL card, you're given a simple form: the dashboard's URL, an authentication method, and your credentials. Fugo generates the login steps itself from what you type — there's no recording, no browser extension, and no live walkthrough of your actual login screen. This is the current default for essentially every dashboard type, including SAML and other SSO-protected ones, and it's what the rest of this guide focuses on.

A small number of logins are structured in a way the standard form can't handle automatically — an unusual multi-step flow, or a page that needs specific elements erased or isolated before the screenshot is taken. For those cases, Fugo still offers a Public URL option that uses our Chrome extension, the Dashboard Recorder, to manually record your login and screenshot steps once, which Fugo then replays going forward. This path supports fewer 2FA methods than the standard form (its two-factor handling is built around a narrower set of providers), so we'd recommend trying the standard Custom URL setup first, and only falling back to Public URL / the Dashboard Recorder if that doesn't work for your specific login.

Because Fugo works by filling in whatever login fields it finds — rather than speaking a specific identity-provider protocol — compatibility comes down to one question: can the login be completed with a password and, if needed, a time-based one-time code — with no push notification, SMS code, or other action on a physical device required?

Whatever identity provider your dashboard sits behind, here's what determines whether Fugo can sign in automatically:

If your platform has a dedicated card in Fugo's Create Dashboard screen — Salesforce, Tableau, Looker Studio, and HubSpot each do, along with several others — use it; it's pre-configured for that platform's specific login quirks. If it doesn't, use Custom URL, which offers the exact same setup form (URL, Authentication Method, credentials, Secret Key) for any login-protected page. Either way, this is the path that supports SAML, Okta, Google, and Microsoft sign-in, along with TOTP-based MFA.

If your login involves an unusual multi-step redirect chain that the standard form can't get through automatically, or you need to erase or isolate specific elements before the screenshot is taken, try Public URL instead. This opens our Chrome extension so you can record the login and capture steps manually, one time, for Fugo to replay afterward. Because its MFA handling is narrower than the standard form's, we'd only recommend this as a fallback — for most SAML and SSO logins, Custom URL will work on the first try.

When you turn on an authenticator app for two-factor authentication, that app is built from a secret key — a alphanumeric string that both your authenticator app and your identity provider know. Every 30 seconds, that shared secret produces a new 6-digit code — which is why the code you see on your phone right now will be different from the one you'll see in an hour.

Fugo asks for that underlying secret key, rather than a single code, because it needs to keep generating fresh codes indefinitely — every time it refreshes your dashboard, on whatever schedule you've set, for as long as the dashboard stays published. A one-time code would stop working within 30 seconds; the secret key doesn't expire.

For a full walkthrough of where to find your Secret Key for a specific provider, see our dedicated guide: What Is a Secret Key? — plus the provider-specific guides linked in the table above for Google, Microsoft, and Okta.

Once your account is ready — service account created, TOTP-based MFA turned on, other verification methods removed, and your Secret Key saved — you're ready to connect your dashboard in Fugo:

From there, add it to a playlist and publish it directly to a screen, or open it in the Design Studio first to crop it, add a logo, or combine it with other content.

If you're connecting one of these specific platforms, our dedicated guides walk through that platform's setup screen by screen:

Using a different platform? The steps in this guide apply the same way to any Custom URL dashboard — reach out if you'd like us to confirm compatibility with your specific tool first.

If Fugo can't complete the login and load your dashboard, it's almost always because the login flow includes a step Fugo can't answer — a push notification, an SMS code, or an unexpected "verify it's you" prompt. Here's how to fix it:

Create an account used only for dashboard display, with the minimum permissions needed (view-only where possible). This avoids interruptions from personal security settings and keeps your setup easy to audit. Set up a service account →

Most identity providers — including Okta, Microsoft, and Salesforce — let you enable a TOTP authenticator alongside or instead of push-based MFA. Set it up, and be sure to copy the secret key (not just a one-time code) during setup so you can paste it into Fugo.

Turn off backup methods like phone number recovery, email confirmation codes, and push-based MFA on the service account. This keeps the login flow consistent and predictable every time Fugo runs it.

If your dashboard still isn't loading correctly after trying the above, save your dashboard configuration in Fugo and reach out to our team at support@fugo.ai, start a chat with us from inside Fugo CMS, or book a setup call — we're happy to walk through your configuration and help figure out what needs adjusting.

New to Fugo? You can explore all of this yourself with a free 14-day trial.