Reporting a problem
Include the app version and build, device model, operating-system version, affected screen, expected result, and observed result. If the issue involves sync, say which device made the change and which device has not received it.
Help with your operational workspace
For Operations Binder support, email support@operationsbinder.com.
For setup, macOS editing, iPhone/iPad lookup, private iCloud sync, packet transfer, and archive recovery instructions, start with the Operations Binder User Guide.
Include the app version and build, device model, operating-system version, affected screen, expected result, and observed result. If the issue involves sync, say which device made the change and which device has not received it.
Do not email passwords, tokens, private keys, recovery codes, raw environment files, credential values, or unredacted infrastructure exports. Describe the issue with the minimum safe context.
Operations Binder stores the workspace on your devices using Apple system persistence. Signed App Store builds use your private iCloud database to keep the same operator's Mac, iPhone, and iPad current. TeamAdler does not operate an application-data server.
The mobile companion is intentionally read-only. The Mac remains the authoritative place to create, edit, import, restore, and delete operational records.
CloudKit sync is eventually consistent. Save on the Mac, keep both devices online, and allow the Mac app to export the change. Switching away from the Mac app can prompt a queued export; then foreground the mobile app and wait for the change to arrive.
Yes. Previously synchronized records remain in the local device cache. New changes arrive after connectivity returns and private iCloud synchronization completes.
On the Mac, choose Data → Export Workspace Archive, then verify the archive with Data → Verify Workspace Archive. Keep the resulting file in a private, independently backed-up location.
Use the Mac app to delete systems, environments, or individual context records. Protected deletion creates an owner-only local archive first. Delete that backup and any exports separately when your retention policy allows.