Calendar Data Source FAQ¶
How to Choose the Right Calendar Data Source?¶
SyncSign supports multiple calendar data sources. You can choose the appropriate one based on your environment and requirements:
Data Source Type |
Use Case |
Deployment Method |
Notes |
|---|---|---|---|
Google Calendar |
Personal or small teams |
Cloud (SaaS) / On-Premise (SOPS) |
Easy to configure |
G Suite |
Enterprise Google Workspace |
Cloud (SaaS) / On-Premise (SOPS) |
Supports organization management & resources |
Office 365 |
Microsoft 365 users |
Cloud (SaaS) / On-Premise (SOPS) |
Supports organization management & resources (Delegated & App auth) |
Exchange Server |
On-premise Exchange deployment |
On-Premise (SOPS) |
Requires SOPS server |
NextCloud |
Self-hosted CalDAV server |
On-Premise (SOPS) |
Requires SOPS server |
CSV URL |
Custom data source |
On-Premise (SOPS) |
Requires SOPS server |
Note
Cloud deployment (SaaS): Suitable for most users, simple configuration, no local server required
On-premise deployment (SOPS): Suitable for enterprises with special data security requirements, all data stays within the corporate network
General Questions¶
How to Trigger Display Synchronization and Refresh¶
When using a calendar as a data source, the Display will automatically synchronize and refresh (in Hub+Display working mode) under the following conditions:
Initial calendar binding: When you first bind a calendar (room resource) to a Display
Event changes: When events are created, deleted, or modified in the calendar (room resource) bound to the Display
Calendar status changes: When the status of the bound calendar (room resource) changes:
Room transitions from “no current activity” to “activity scheduled”
Room transitions from “activity in progress” to “activity ended”
Display Synchronization Refresh Failure¶
1. Check Microsoft 365 Account Permissions¶
The Microsoft 365 account used to authorize login in the SyncSign client may have lost management permissions for the calendar (room resource) bound to the Display.
Troubleshooting steps:
Go to the SyncSign client and navigate to the Display configuration page
Unbind the Display from the calendar
Re-bind the Display to the calendar
Expected results:
If binding succeeds: Observe whether the Display can synchronize and refresh the calendar information
If binding fails: Please contact us and provide error screenshots for further troubleshooting and analysis
2. Integration Failure Due to Client Secret Expiration (SOPS Deployment)¶
The most common reason is that the Client Secret for the Azure App has expired. Once this date is reached, Microsoft rejects connection requests from SyncSign, causing the synchronization to fail.
Fix (typically takes only 5 minutes):
Log in to the Azure Portal and locate the specific App
Generate a new Client Secret
Immediately copy the new Secret Value and update it in your SOPS system configuration settings
Once saved, the integration will be restored immediately
Event Title Shows Organizer Name Instead of Event Subject¶
By default, Office 365 room resources are configured to display the organizer’s name instead of the actual event title. This means SyncSign displays may show the organizer’s name rather than the meeting subject.
Solution:
Please refer to: Modify the Settings of the New Room Resource
This document provides step-by-step instructions on how to modify the room resource settings using PowerShell or Azure Cloud Shell to ensure event titles are preserved and displayed correctly on SyncSign displays.
Other Issues¶
If the above solutions do not resolve your issue, or if you need additional assistance, please feel free to contact us:
Website: https://help.sync-sign.com
Email: help@sync-sign.com