A True Story
On July 6, 2026, corrupt-settings protection was added: the server now refuses to start on a broken configuration file, instead of running wrong quietly.
Curated Sync Guide · Your Control Panel
Curated Sync Guide · Your Control Panel
Connections, schedule, performance, images, notifications. Guarded so a bad setting cannot do harm.
This guide explains the Settings screen in the Curated Sync control panel. Written for admins. Three minutes to read.
CURRENT AS OF JULY 16, 2026The link to IntelliEvent. Credentials themselves never display; the screen only says configured or missing.
When the nightly sync fires. Default: 2:00 AM.
How hard the sync works: page sizes, worker counts, time budgets.
Photo download behavior and retry limits.
Where alerts go when a run needs attention.
Everything tunable lives here, grouped by what it affects, described in words not codes.
Settings are validated, snapshotted, and reversible.
Every change is checked before it saves. An invalid value is refused with a plain message, not stored. Every accepted change is snapshotted, with the last 20 versions kept, so any change can be rolled back.
Protective features follow a careful rollout convention: they ship watching-only first, then enforce once proven. Current behavior never changes by surprise.
On July 6, 2026, corrupt-settings protection was added: the server now refuses to start on a broken configuration file, instead of running wrong quietly.
Validated on the way in, snapshotted once in, refused at boot if broken. Settings cannot rot silently.
By design. Credentials live outside the interface entirely. The screen reports configured or missing, never the value.
Admins only. Viewers see the screen but every edit is refused. Each change lands in the Activity log with the admin's name.
Roll it back. The last 20 configurations are kept as snapshots.
Powerful controls, safe rails. Change with confidence; undo is built in.