Holy ResourceHoly Resource
Core Concepts

Offline & Sync

How Holy Resource handles data synchronization across devices.

Holy Resource is designed to work offline first.

  • When you save something, it saves to your device immediately.
  • Sync (if you enable it) shares those changes with your other devices.
  • If you lose internet (or Wi‑Fi), you can keep working. Sync will catch up later.

This page explains what sync does, what happens when you’re offline, and how to connect devices in a non‑technical way.

The Sync Lifecycle

When sync is enabled, Holy Resource keeps a small “to‑send” list of changes on your device and delivers them when possible.

You can choose one of these sync targets from the sync controls under Settings → General. In practice, Holy Resource uses the Database tab for the underlying storage setup and the dedicated Sync tab for connection, pairing, and conflict work when sync is available:

  • No sync (local‑only): Everything stays on this device only.
  • LAN sync (same network): Sync with devices on the same Wi‑Fi/Ethernet network.
  • Server sync (internet): Sync through your organization’s hosted sync server.

In Holy Resource, a branch usually means a campus/location (for example: “Main Church” and “Downtown Campus”). Sync is set up per branch.

If you don’t see these settings or can’t change them, ask your administrator to grant the right permissions.

In free mode, sync management UI may be limited or hidden depending on your current license state.

Local Save (Works Offline)

You record an entry (for example: a member update, attendance check‑in, or donation). It is saved instantly to your local database.

Change Queue

If sync is enabled, the app adds that change to a queue (a list of changes waiting to be shared).

Background Sync (When Possible)

  • With LAN sync, the app can sync when your trusted devices are on the same network.
  • With Server sync, the app can sync when your device can reach the sync server.

If you’re offline, the queue stays on your device and will send later.

Connecting Devices (What You Actually Do)

Most teams should not type “tokens” or long settings.

Server Sync (Internet)

Your administrator provides a connection code (often as a QR code) for your church/organization.

  1. Go to Settings → General → Database.
  2. Choose Server sync (internet) as the sync mode.
  3. Open Settings → General → Sync.
  4. Under Connect this device, choose one:
    • Scan QR code
    • Paste connection code

Holy Resource will fill in the server details automatically and store the credentials encrypted on your device.

LAN Sync (Same Wi‑Fi / Ethernet)

LAN sync uses a one‑time pairing step, so you only sync with devices you trust.

  1. Go to Settings → General and choose LAN sync (same network) as the sync mode.
  2. Open Settings → General → Sync.
  3. In LAN Sync, press Start.
  4. Pair devices using Pair and verify the safety code on both devices.

For the full walk‑through, see the LAN Sync guide.

Conflict Resolution

If two devices edit the same item before they’ve had a chance to sync, a conflict can happen.

When this happens, Holy Resource will:

  • Keep both versions
  • Show a conflict count in Settings → General → Sync
  • Let an authorized user review and resolve the conflict

Recommended team practices:

  • Sync regularly on shared devices.
  • Avoid parallel editing of the exact same records during high-traffic events.
  • Train admins to review post-sync anomalies quickly.

You typically choose which version to keep (for example: “use this device” vs “use the other device”).

During import/recovery workflows, Holy Resource also supports conflict policy choices:

  • Abort (stop on conflict)
  • Skip (keep existing, import what is safe)
  • Overwrite (replace conflicting records where supported)

Privacy in Sync

  • Sensitive fields are encrypted on your device before syncing.
  • Sync credentials are stored encrypted on-device.
  • Sync is branch‑scoped. Sync applies to the branch you’re working in.

If Sync Target is set to local-only, pending sync operations are not sent until sync is re-enabled.

Note: Sync is not a replacement for backups. Backups are still recommended for disaster recovery.

For a deeper look at how we protect your data, see the Security Model.

Last updated on

Was this helpful?

On this page