SOPS Setup Navigation

Overview

This page is a navigation guide for SyncSign On-Premise Server (SOPS) projects. It helps you determine:

which setup steps are shared across most SOPS deployments
when to add Hubs and Displays
how to verify the SOPS >> Hub >> Display communication path
which calendar data source you are using
which extra steps are required only for specific data sources
which document to open next for detailed instructions

If you are deploying SOPS for the first time, it is recommended to read this page first, then continue with On-Premise Server (SOPS) Setup.

Step 1: Deploy and Initialize SOPS

Start with the basic SOPS installation flow:

Deploy and initialize the SOPS server.
Confirm that the SOPS client can connect to the SOPS server.
Check the network path between SOPS and the local device network.

For the basic SOPS installation flow, see On-Premise Server (SOPS) Setup. For network planning, see Firewall Configuration for On-Premise Server (SOPS).

Step 2: Add Hubs and Displays First

Adding Hubs and Displays is not determined by the calendar data source you plan to use. Whether your final data source is Microsoft 365 / Exchange Online, Exchange Server, Google Calendar, NextCloud, CalDAV, or CSV URL, you can add Hubs and Displays before completing the data-source integration.

After adding the Hub and Display, open the SOPS client, go to the Display management page, and click Test to verify that the SOPS >> Hub >> Display communication path is working.

Use the following documents as needed:

Hub setup: SyncSign Hub H1
Hub H2 setup: SyncSign Hub H2
Display setup overview: Installation Guide for Displays
WiFi-only display setup: WiFi Mode Setup for SyncSign Displays

If you use the SyncSign Provisioning App for Hub or Display deployment, make sure the target device is in Setup mode and placed near the phone during Bluetooth pairing.

Step 3: Choose Your Data Source

Use the following guide to find the correct integration path:

Microsoft 365 / Exchange Online

Use this path if your calendars are hosted in Microsoft 365. This integration requires SOPS to be reachable through a valid public domain and HTTPS before you start calendar authorization, but this can be configured after the Hub and Display chain has been tested. Continue with Using Microsoft 365.
Exchange Server (On-Premises)

Use this path if your organization runs Microsoft Exchange Server inside your own LAN or VPN. In most deployments, you do not need to prepare a public domain just for the Exchange integration itself. Continue with Using Exchange Server.
Google Calendar / Google Workspace

Use this path if your calendars are hosted by Google. This integration requires SOPS to be reachable through a valid public domain and HTTPS before you start Google authorization, but this can be configured after the Hub and Display chain has been tested. Continue with Using Google Calendar / Google Workspace.
NextCloud / CalDAV / CSV URL / Other self-hosted sources

Use this path if your data source is hosted by your organization or provided through a custom endpoint. The main requirement is that SOPS can reach the data source over the required network path. Continue with Using CalDAV on NextCloud or Using CSV URL.

Step 4: Follow the Recommended Order

For most SOPS projects, the recommended sequence is:

Deploy and initialize the SOPS server.
Add Hubs and Displays to the SOPS project.
In the SOPS client Display management page, click Test to verify the SOPS >> Hub >> Display path.
Confirm which calendar data source will be used.
If the selected data source requires it, configure the SOPS domain name, DNS, and HTTPS certificate.
Complete the calendar integration for the selected data source.
Bind calendars, rooms, templates, and devices.
Verify that synchronization works as expected.

Step 5: Check What Is Shared vs. What Is Different

Common steps in most SOPS deployments

The following work is common across most SOPS projects:

prepare and install the SOPS server
verify network communication and firewall rules
add Hubs and Displays
test the SOPS >> Hub >> Display path from the Display management page
select the target calendar or room resources
bind devices to the correct room or data source
test data synchronization after setup

Data-source-specific differences

Data Source Differences
Data Source	Public Domain / HTTPS	When to Add Devices	Notes
Microsoft 365 / Exchange Online	Required before integration	Before or after data-source planning	SOPS must be reachable externally for the authorization and callback flow, but devices can be added and tested first.
Google Calendar / Google Workspace	Required before integration	Before or after data-source planning	SOPS must be reachable externally for the authorization and webhook flow, but devices can be added and tested first.
Exchange Server (On-Premises)	Usually not required for Exchange access itself	Before or after Exchange setup	Focus on LAN or VPN connectivity, service account permissions, and room configuration.
NextCloud / CalDAV / CSV URL	Depends on where the data source is hosted	Before or after the data source path is verified	Focus on endpoint reachability, polling, and mapping.

Step 6: Prepare Domain and HTTPS Only When Needed

Public domain and HTTPS are especially important for cloud-hosted calendar sources such as:

Microsoft 365 / Exchange Online
Google Calendar / Google Workspace

In those scenarios, you can still add Hubs and Displays first and use Test in the SOPS client Display management page to confirm the SOPS >> Hub >> Display path. If you plan to integrate with external resources such as Exchange Online later, you can configure the trusted certificate, public domain name, and HTTPS access after the device path has been verified.

Typical preparation tasks:

prepare a public domain name
create the correct DNS record
ensure port 443 can reach the SOPS portal
install a valid SSL/TLS certificate on SOPS

Step 7: Complete Calendar Integration

After the SOPS server and network path are ready, continue with the document that matches your data source:

Microsoft 365 / Exchange Online: Using Microsoft 365
Exchange Server (On-Premises): Using Exchange Server
Google Calendar / Google Workspace: Using Google Calendar / Google Workspace
NextCloud: Using CalDAV on NextCloud
CSV URL: Using CSV URL

This is the stage where you should finish account authorization, API settings, service account setup, polling configuration, or resource mapping required by that specific source.

Step 8: Bind Rooms, Calendars, and Devices

After the device path is tested and the data-source integration is complete, continue with project-specific binding work:

assign the correct room calendar or data source record
select the template or display layout
bind each device to the intended room or source ID
confirm that the room information shown on the display matches the source data

Step 9: Final Verification

Before handing over the project, verify the following:

the SOPS portal is accessible as expected
the SOPS >> Hub >> Display path passes the Test check in the SOPS client
the selected calendar source is connected successfully
the required rooms or calendars are visible in SOPS
Hubs and Displays appear online
each device is bound to the correct room or source
calendar updates can sync to the display successfully

Common Mistakes

The following mistakes often cause confusion during SOPS projects:

assuming Hub and Display setup must wait for the selected data source
skipping the Display management Test check before troubleshooting calendar synchronization
treating Exchange Online and Exchange Server as the same deployment type
assuming a LAN IP is enough for Microsoft 365 or Google authorization
overlooking firewall or DNS requirements before testing external calendar integration
starting Bluetooth-based setup when the Hub or Display is not in Setup mode