> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/request-and-secure-web-wallboard.md).

# Request and secure Web Wallboard

Request Web Wallboard enablement, secure public access with AnywhereNow Authentication, and understand update behavior.

Web Wallboard is an optional component of a UCC Service Bundle and is available as a web service per UCC service.

## Before you request Web Wallboard

Web Wallboard is for existing customers on Dialogue Cloud Neo (Connect) with an installed UCC service.

{% hint style="info" %}
Web Wallboard is in maintenance mode and no longer receives new feature development. Existing deployments remain supported for maintenance and critical/security fixes. Web Wallboard is not available for Dialogue Cloud Neo (Unify). Use [Dialogue Workspace](/use/monitor-and-report/dialogue-workspace.md) for Unify.
{% endhint %}

## Request Web Wallboard

If you are in the GoLive phase, ask your AnywhereNow partner or AnywhereNow direct contact to enable Web Wallboard.

If you are already live with a UCC service and have not yet enabled Web Wallboard, request enablement through your partner or your existing AnywhereNow support process.

The URL for your Web Wallboard is provided by your AnywhereNow partner, direct contact, or support ticket.

The URL is formatted like this:

```
https://<guid>-<service-number>.<region>.anywhere365.cloud/webwallboard/
```

Different UCCs and agent variables can be displayed or hidden depending on the URL parameters. For URL filters, see [Filter the Web Wallboard view](/use/existing-dialogue-cloud-neo-connect-apps/web-wallboard/filter-web-wallboard-view.md).

## Secure access before go-live

{% hint style="warning" %}
The default Web Wallboard endpoint is an open public web service over HTTPS. Without authentication, contact-center information, including sensitive customer and employee data, can be publicly accessible. Enable AnywhereNow Authentication before going live with Web Wallboard.
{% endhint %}

[AnywhereNow Authentication](/platform-administration/provisioning/provisioning/configurations/configure-authentication.md) enables users to sign in to Dialogue Cloud products using their Microsoft 365 credentials and supports additional security through multi-factor authentication.

## Shared authentication behavior

Snapper, Inflight Wallboard, and Web Wallboard use the same authentication method per UCC service. If AnywhereNow Authentication is enabled for one application, it is also enabled for the other applications that use that service.

Web Wallboard configuration is handled by Dialogue Cloud. If Snapper and/or Inflight Wallboard are also used, each client application must be configured for this authentication method. For the available application-specific notes, see [Configure Authentication — Configure application-specific settings](/platform-administration/provisioning/provisioning/configurations/configure-authentication.md#configure-application-specific-settings-if-applicable).

As of Bundle `DC2024.01f`, a new redirect URI and backend platform is required. See [Authentication Migration](/operate/maintain-and-change/authentication-migration.md).

## Authentication prerequisite

Before AnywhereNow Authentication can be enabled for Web Wallboard, create the required app registration and collect the authentication details for the UCC service. Follow [Configure Authentication](/platform-administration/provisioning/provisioning/configurations/configure-authentication.md).

## What users see after authentication is enabled

After Web Wallboard is enabled for AnywhereNow Authentication and the prerequisite setup is complete, users should see a Microsoft 365 login screen after accessing the Web Wallboard URL from a browser.

<figure><img src="https://2358142509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJymOXTAFZLWXmwvtHWu8%2Fuploads%2Fgit-blob-949254172e2c940aea41c3d1952187c7ccc3e3ff%2Fweb-wallboard-authentication-login.png?alt=media" alt="Microsoft 365 login screen for Web Wallboard"><figcaption></figcaption></figure>

After users sign in with trusted credentials, the agent UPN and a **Sign out** button are visible in the upper-right corner of Web Wallboard.

<figure><img src="https://2358142509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJymOXTAFZLWXmwvtHWu8%2Fuploads%2Fgit-blob-f666872bc0c0aa9c42b13661db238600719264ed%2Fweb-wallboard-authenticated-view.png?alt=media" alt="Authenticated Web Wallboard view with visible user identifier and Sign out button"><figcaption></figcaption></figure>

## Updates

When an upgrade of your UCC Service to a newer Bundle is requested, Web Wallboard is automatically upgraded to the version that belongs to that Bundle.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/request-and-secure-web-wallboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.