Displaying password-protected content on digital signs — dashboards, internal tools, analytics — requires authentication. Screenly provides several ways to handle this, depending on your use case.

Browser Extensions (Chrome & Firefox)

The easiest way to display authenticated web pages is with our Save to Screenly browser extension. Log into the page in your browser as you normally would, click the extension, and it captures your session so the screen stays authenticated.

• Save Authentication captures your current session cookies, so the player can display the page without needing your credentials
• Works with any website that uses session-based authentication
• Available for free on the Chrome Web Store and Mozilla Add-ons
• Open source on GitHub

For a step-by-step guide, see Use our browser extensions to add web page content to your digital signs.

Basic Auth

Screenly supports HTTP Basic Auth via the web interface, CLI, and API. If the service you want to display supports Basic Auth, you can provide the credentials directly when adding the asset — no extra tools needed.

JavaScript Injection

For more advanced authentication flows (multi-step logins, OAuth redirects, custom forms), you can use our JavaScript injector. When a web page loads on the player, your custom JavaScript executes to complete the login process automatically.

This is useful when:

• The service doesn’t support Basic Auth or session cookies
• You need to automate a multi-step login flow
• You want to interact with the page DOM before or after authentication

For more background on authentication approaches, see our blog post How to login to websites using Screenly.