SOPS Setup Navigation

Overview

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

  • which calendar data source you are using

  • which setup steps are shared across most SOPS deployments

  • 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: 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. 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. 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 3: 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

  • select the target calendar or room resources

  • add Hubs and Displays

  • 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

After calendar integration

SOPS must be reachable externally for the authorization and callback flow.

Google Calendar / Google Workspace

Required before integration

After calendar integration

SOPS must be reachable externally for the authorization and webhook flow.

Exchange Server (On-Premises)

Usually not required for Exchange access itself

Usually after Exchange setup is confirmed

Focus on LAN or VPN connectivity, service account permissions, and room configuration.

NextCloud / CalDAV / CSV URL

Depends on where the data source is hosted

After the data source path is verified

Focus on endpoint reachability, polling, and mapping.

Step 4: 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, do not start by adding Hubs or Displays first. Finish the public access setup and calendar integration first, then continue with device setup.

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

Related documents:

Step 5: Complete Calendar Integration

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

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 6: Add Hubs and Displays

Hub and Display setup is a shared deployment step in most SOPS projects. In other words, this is usually not a data-source-specific task, but a later-stage deployment step after the SOPS and calendar side are ready.

Use the following documents as needed:

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 7: Bind Rooms, Calendars, and Devices

After the integration and device setup are 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 8: Final Verification

Before handing over the project, verify the following:

  • the SOPS portal is accessible as expected

  • 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:

  • starting Hub or Display setup before completing the cloud calendar integration

  • 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 integration

  • starting Bluetooth-based setup when the Hub or Display is not in Setup mode

Suggested Reading Order

If you are starting a new SOPS deployment, the recommended reading order is:

  1. SOPS Setup Navigation

  2. On-Premise Server (SOPS) Setup

  3. Open the detailed guide for your chosen data source

  4. Open the Hub or Display setup guide required by your hardware

  5. Review Firewall Configuration for On-Premise Server (SOPS) if there are connectivity issues