Table of contents:

TV dashboards often need a little adjustment to work and look their best on screen.

This guide covers simple best practices for setting them up in Fugo, along with a few checks to run if something is not displaying or refreshing as expected.

Before connecting the dashboard, make sure you know what kind of login flow it uses. Some dashboards use a standard username and password, while others rely on Google, Microsoft, Okta, or another SSO provider.

Knowing this up front makes it easier to complete setup and troubleshoot authentication errors later.

For secure dashboards, a dedicated service account is usually the most reliable option. In most cases, we recommend using a service account with read-only access and TOTP-based 2FA enabled.

It helps avoid interruptions caused by password changes, employee access changes, or prompts tied to a personal user account.

Fugo signs in to your dashboard automatically, on a repeating schedule, with no one at a browser to approve anything - so it can only use authentication methods that don't need a human to respond in the moment. Two currently work: TOTP-based 2FA and Passkey login.

If the dashboard account uses two-factor authentication, it must be configured to use time-based one-time passwords (TOTP). Fugo generates a fresh code from your account's secret key every time it refreshes the dashboard.

As an alternative to a username, password, and secret key, you can now add a passkey directly to a dashboard from its Home tab:

You don't need an existing passkey; Fugo creates its own the moment you set one up on the dashboard. Some services let an admin restrict passkey registration to device-bound credentials only, which blocks Fugo from adding one.

The feature just launched and is still being refined - see Dashboards Overview for the full walkthrough.

Everything else - push notifications, SMS codes, device-bound hardware keys, or Microsoft's "Stay signed in?" prompt left to chance - needs a human to respond and will interrupt the login flow, preventing the dashboard from refreshing reliably.

Some dashboard platforms restrict access by IP address or only allow logins from approved networks. If that applies to your setup, make sure Fugo will be allowed to access the dashboard before you begin configuration.

If your organization uses network restrictions, firewalls, or VPNs, you may need to allowlist the domains and services Fugo uses in order for dashboards to load correctly.

Before setting a refresh interval in Fugo, check how often the source data actually changes.

Fugo displays dashboards by loading the dashboard URL and capturing a screenshot of what appears on the page. Each refresh interval tells Fugo when to reopen the dashboard and capture a new screenshot.

If the underlying data only updates every hour, for example, there is no benefit in capturing screenshots more frequently than that.

Most dashboards are designed for desktop viewing. That's normal.

In many cases, you can make the dashboard work better for screens inside Fugo by adjusting the capture size, cropping the view, or building a cleaner layout in Design Studio.

We'll cover this below.

Set the screenshot refresh interval to something sensible for the dashboard from the dashboard's Home tab. The default is 1 hour.

This will be on for most dashboards by default, but enabling this setting will allow Fugo to preemptively handle and adjust its login flow when the login flow changes at the source level for your dashboard.

For example, if you use Fugo to access a Salesforce dashboard, and Salesforce changes your login flow so that you now have to click through an additional step, Fugo can automatically pick up on that change and adjust its authentication behavior to account for that new step.

Some dashboards are more resource-intensive than others. If a dashboard is struggling to render reliably, try switching the Memory setting from Low to High - those are currently the only two options. You'll find it under the Legacy settings dropdown:

If the dashboard platform is sensitive to repeated login attempts, enabling Re-use cookies can help maintain access between captures:

If the dashboard does not connect successfully, common causes include:

If setup fails, first confirm that the dashboard URL, credentials, and login flow all work outside Fugo.

If the dashboard feels too tall or too dense, start by changing the aspect ratio or resolution of the capture dimensions first from the dashboard's Settings tab:

Once the dashboard is being captured in a better shape, it is much easier to fine-tune the view later in the Design Studio.

If screenshots are capturing loading spinners, incomplete content, or partially rendered data, increase Pause duration (seconds) so Fugo waits longer before taking the screenshot:

If your dashboard screenshot has uneccessary sidebars, popups, or tooltips in it, use the Declutter setting to tell Fugo which of those elements to remove before taking the screenshot:

The Scroll Distance setting scrolls the page down by a set number of pixels before Fugo takes its screenshot. It can help with long dashboards, but it works best as a small adjustment. You'll find it in the dropdown under Legacy settings:

Want to crop a dashboard down to just the chart you need, or combine it with other apps, text, or media on the same slide?

Add it to a Design Studio canvas instead of publishing it directly: open (or start) a Studio design, find your saved dashboards under the Dashboards panel, and click or drag one onto the canvas.

From there you can crop, resize, and combine it with other elements like any other Studio content, then publish that design to a playlist the same way described above.

👉 Learn more about dashboards & the Design Studio here

A TV screen should not try to show everything at once. It is usually better to show fewer charts clearly than to squeeze an entire dashboard into one view.

Dashboards only continue updating when they are published to a screen through an active playlist. If a dashboard is not refreshing, this is one of the first things to check.

Open the dashboard's Playlist tab to confirm it has been assigned to an active screen:

A green status usually means the dashboard is connected and updating correctly. A red status indicates an error and should be investigated:

If a dashboard was working and then stops updating, check whether:

If you need more control over refresh timing or want dashboard access to stay within your own environment, use the On-premise or local-player settings to enable Fugo to access & render your dashboard from inside your own network (or on your device at the screen endpoint):

🔗 Learn more about on premise dashboards

If a dashboard is not displaying or refreshing as expected, check the following:

This guide is still being updated. If you don't see your issue or you're still having issues after following this guide, please don't hesitate to drop a message to our support team in the chat box or at support@fugo.ai - they're always happy to help!

Want to try Fugo first? Start a free trial - no credit card required.