Salesforce has started requiring multi-factor authentication for all users logging directly into a Salesforce org, rolling out gradually across customers through September 3, 2026. If you haven't seen any change yet, you likely will as the rollout reaches your org.

👉 See the announcement

The part that affects Fugo: when an account has no MFA method registered, Salesforce now defaults to prompting for a passkey — a Face ID, Touch ID, Windows Hello, or security-key credential tied to one device. Fugo can't authenticate with passkeys yet, so if the account your Salesforce dashboard uses gets steered into that flow, its automated sign-in will get stuck and the dashboard will stop refreshing.

The good news: this is easy to avoid. If you (or the service account you use for Fugo) see a "Create a Passkey" screen, click Choose Another Verification Method and register a TOTP-based authenticator app instead — that's the same secret-key method Fugo already supports today.

👉 More details are in our Salesforce Dashboard App Guide.

If you sign into Salesforce via Okta or Google SSO, you may not be affected at all. We're actively working on adding passkey support to Dashboards, so this workaround for Salesforce (and other apps that adopt passkey-based MFA) won't be necessary going forward.

Need help adjusting or creating your Salesforce dashboards? Reach out to us in the support chat or via support@fugo.ai.

On September 2, we'll retire the legacy ("Classic") Fugo CMS. From that date onwards, CMS 2.0 will be the only version of Fugo available.

Most customers have already been using CMS 2.0 as their default experience over the past few months, so for many of you this won't be a significant change. If you've still been using the legacy CMS, though, now's a good time to get familiar with the new experience before the cutover.

The good news is that there's nothing you need to migrate. CMS 2.0 uses the same Fugo account, so your screens, playlists, media, dashboards, users, and settings are already there waiting for you.

ℹ️ You'll find updated support docs covering the new CMS in this Help Center collection

Join us for a live walkthrough

We're running three live CMS 2.0 walkthrough webinars before the cutover:

• Wednesday, August 12 — 3:00 PM BST
• Wednesday, August 26 — 5:00 PM BST
• Monday, August 31 — 6:00 PM BST

We'll walk through the new CMS, answer questions live, demonstrate some of the newer features, and give a preview of what we're currently building.

What's new in CMS 2.0?

Since launching CMS 2.0, we've continued adding capabilities that aren't available in the legacy CMS, like:

Email Triggers that let Fugo turn incoming emails into screen-ready content automatically. Many CRMs, monitoring tools, ticketing systems, and other business applications already send email notifications when something important happens. CMS 2.0 can receive those emails, extract the important information, and publish it to your screens without requiring a custom integration.

TV Dashboards have seen some of the biggest improvements, including a new live streaming engine on supported hardware and Dashboard Declutter, which automatically removes browser UI from captured dashboards for a cleaner presentation.

Floor Plans make it easier to organize and manage screens based on where they're physically installed, giving you a clearer picture of larger deployments across offices, retail stores, campuses, and other multi-site environments.

Get support

If you have any questions before September 2 - or if something doesn't behave as you'd expect in CMS 2.0 - just reach out to us via support chat or email us at support@fugo.ai.

We'll be happy to help!

When we announced that Fugo was available on the Amazon Signage Stick back in May, it was only available through Amazon.com in the US.

The Amazon Signage Stick is now available to purchase in Germany, Spain, France, Italy and the United Kingdom, making it easier for customers across Europe to deploy Fugo on purpose-built signage hardware.

If you've been considering replacing older Fire TV deployments or starting a new signage rollout, now's a good time!

• Eligible customers can receive 20% off a full year of Fugo when deploying the Amazon Signage Stick through the end of 2026.
• US customers can also save 10% on the Amazon Signage Stick by using code FUGOAMZN at checkout on Amazon.com. This hardware offer is available through July 28, 2026.

Purchase the Amazon Signage Stick here:

• United States (Amazon.com) - $99.99
• Germany (Amazon.de) - €151.99
• Spain (Amazon.es) - €151.99
• France (Amazon.fr) - €151.99
• Italy (Amazon.it) - €151.99
• United Kingdom (Amazon.co.uk) - £151.99

If you missed our original announcement, you can read more about the Amazon Signage Stick, how it works with Fugo, and how to redeem both offers here.

If your organization manages Windows devices with Microsoft Intune, you can now deploy Fugo directly through your existing device management workflows.

Instead of installing Fugo manually on each device, Intune lets you deploy the player silently across your fleet, assign it to device groups, and control exactly when new versions are rolled out.

It's a much simpler way to onboard new screens while keeping every device on an approved version.

Our new deployment guide walks you through:

• Packaging the Fugo Player installer for Intune
• Creating a Win32 app
• Configuring installation and detection rules
• Assigning Fugo to your Windows devices
• Managing future updates using Intune Supersedence

Follow the guide here:

📖 Deploying Fugo with Microsoft Intune

Need help getting started?

Reach out to support@fugo.ai or write to us in the handy support chat box!

If you're running Fugo on a Fire TV Stick, the Amazon Signage Stick is worth a serious look. It's $99.99 and it's built entirely for digital signage - not repurposed from a streaming device. That difference shows up in the day-to-day:

• It boots directly into Fugo, no home screen, no consumer apps in the way
• Kiosk mode is locked in by default, so displays stay on your content
• Firmware updates are signage-only. No more consumer Fire TV updates silently breaking your Fugo app overnight - the Signage Stick only receives updates relevant to signage use, so your displays stay stable
• It ships with a secure bootloader and encrypted storage
• You can provision and manage multiple sticks remotely via the Amazon Signage app, without touching each device

For teams managing more than a handful of screens, or anyone who's had to babysit a Fire Stick that wandered out of the Fugo app, it's a meaningful upgrade.

Use the Amazon Signage Stick & get 20% off your Fugo subscription for year

To help make the switch easier, eligible customers may qualify for 20% off their Fugo subscription for a full year when deploying the Amazon Signage Stick.

To learn more about eligibility and redeeming the offer, check out our eligibility & redemption guide, or reach out to sales@fugo.ai / your account manager.

Please note: this offer cannot be combined with existing discounts of equal or greater value, promotional pricing, or discounted enterprise agreements.

Get 10% off your hardware

You can also use code FUGOAMZN at checkout on Amazon to get 10% off your Signage Stick if you purchase by July 28, 2026 (US customers only.)

If you're currently evaluating Fugo, these offers apply to you too!

🔗 Get your Amazon Signage Stick

🔗 Learn more about the Amazon Signage Stick

🔗 Amazon Signage Stick Dicount Eligibility & Redemption

Hi there,

We're sorry for the disruption — we know unpaired screens are the last thing you need in the middle of your day.
​

Here's where we are right now and the steps that will help us get your screens back up.
​

Restart your players

Please restart all affected players. In many cases, they'll re-pair on their own once they come back online. This is the fastest path to recovery, so it's worth doing first before anything else.
​

BrightSign devices

We're seeing BrightSign players consistently come back online and re-pair after a restart. If you're running BrightSign, a restart should resolve it.
​

Samsung Tizen devices

Tizen players should be unaffected by this incident. If you're seeing any issues on Tizen screens, please let us know so we can investigate.
​

Players that don't recover on their own

For screens that stay unpaired after a restart, we can re-pair them on our end — but only if we can tell them apart. That means:

• Players on different IP addresses: We can re-pair these for you. Just get in touch and we'll handle it.
  ​
• Players sharing the same IP address (e.g. multiple screens on the same office network): Unfortunately, we can't distinguish between these players, so we can't re-pair them remotely. These will need to be added back to the CMS manually.

We know the manual re-pairing isn't what anyone wants to hear, especially at scale, and we're sorry for the time this will cost you. If you have a large estate affected, reach out and we'll work through it with you.
​

We'll keep this post updated as the situation evolves.

Thanks for bearing with us.
​

Hi there,

We've removed password login from Fugo. Going forward, all users will sign in using SSO (Google, Microsoft, or OKTA) or an OTP sent to your email.

​Why we made this change

Passwords are the most common entry point for account compromise. SSO and OTP are more secure, easier to manage, and align Fugo with the authentication standards expected by enterprise customers. Both options have been available in Fugo for several months, and the vast majority of our users had already moved away from passwords.

​What this means for you

Next time you sign in, choose either SSO or enter your email to receive OTP from the login screen. If your organisation already uses Google Workspace, Microsoft 365, or OKTA, SSO will be the fastest option. Otherwise, we'll email you a secure OTP — no password to remember.

​Need help?

If you run into any issues signing in, reply to this post or contact support and we'll get you sorted.

Release 2.3.3 brings a number of changes that affect day-to-day work. The headline is virtual screens - you can now play content in any browser without physical hardware. Alongside that, the dashboard creation flow has been rebuilt, screen pairing is more honest about license limits, and we have cleared out some long-standing rough edges.

Here is what changed.

New features

• Virtual screens - Run content in any browser without dedicated hardware. Each virtual screen gets a shareable URL and tracks viewers, which is useful for internal dashboards or temporary displays.
• Redesigned dashboard creation - The new modal puts common integrations (Looker, Power BI, Grafana, Google Sheets) and flows (Public URL, On-Premise, Local Player) front and centre, with a searchable grid for everything else.

Improvements

• Clearer screen license limits - Pairing a screen when you have hit your license cap now shows a proper limit screen with a usage bar and a path to add more licenses, instead of the old "Invalid PIN" error.
• Trigger setup - Creating a trigger now uses the same card-based picker as the rest of the product, with a dedicated configuration modal for HubSpot and Salesforce.
• Sidebar updates - Added a billing shortcut to the account dropdown, a "What's new" notice in the sidebar with a quick way to report a bug, and reorganised navigation for a cleaner hierarchy.

Bug fixes

• Screens page reliability - The screens page no longer crashes when monitoring data is unavailable, and offline screen counts display correctly even if monitoring fails.
• CMS version switching - Switching between CMS v1 and v2 is now more reliable, including across login and logout.
• General UI fixes - Dialogs scroll properly on shorter screens, active media cards are highlighted when their detail panel is open, and playlist content names no longer overlap the type label.

If you run into anything after updating, or want help with any of these changes, our support team is available.

Release 2.2.1 has two features worth knowing about. Fallback playlists let you set default content for your screens, so they never go blank when nothing is scheduled. And a new notification system gives you real-time visibility into what is happening across your workspace - screen changes, playlist updates, and more - without refreshing.

Here is what changed.

New features

• Fallback playlists - Screens can now have a fallback playlist that plays automatically during scheduling gaps. Set it once in workspace settings and your screens will always have something to show.
• Real-time notifications - Screen status changes, playlist updates, and other workspace events now stream in as they happen. A new event timeline on the home page gives you browsable history of recent activity.

Improvements

• Unpublish confirmation - Unpublishing a playlist now asks for confirmation first, preventing accidental disruption to live screens.
• Simpler join requests - Accepting or rejecting workspace join requests is now a single step with clear buttons, replacing a confusing multi-step flow.
• Smoother performance - Resolved animation-related slowdowns in screen grid and map views, particularly noticeable on accounts with larger deployments. Returning users should also see faster page loads.

Bug fixes

• Trigger creation - Fixed an issue that prevented new triggers from being created.
• Save and unpublish - The Save and Unpublish action was saving but silently skipping the unpublish step. It now works as expected.

If you have questions about fallback playlists or anything else in this release, reach out to our support team.

Release 2.1.1 covers a lot of ground. The headline is performance: if you manage a large number of screens, the screens page should feel noticeably faster. We have also tightened up playlist publishing, improved the AI assistant, and fixed a number of things that were causing day-to-day friction.

Here is what changed.

Improvements

• Faster screens page - The screens table has been rebuilt for better performance. Accounts with 100+ screens should see a real difference in load and response times.
• Smarter playlist publishing - The publish workflow is more predictable. You now get clear warnings when a publish will not reach any screens, or when saving changes could affect what is currently live.
• AI assistant - Responses are now formatted with rich text, making longer answers easier to read and follow.
• Sign-in - Logging in after entering your code is faster. We also fixed edge cases where the sign-in flow could get stuck or show a blank screen.

Bug fixes

• Playlist targeting - Property-based targeting conditions were not being sent correctly in some cases. This is now fixed.
• Screen status in playlists - Online and offline status now displays correctly when creating or editing playlists.
• General UI fixes - Resolved issues with overlapping menus, inconsistent tooltip behaviour, and dialogs stacking on top of each other.

If you run into anything after updating, or want help with any of these changes, our support team is available.