Client-server mode is no longer a side topic. For many teams, it is now the most important setup question: what should happen centrally on the host, and what should happen locally on each client?
This update gives you a compact workflow map you can use with your team right away.
The core rule: host is authoritative
In client-server mode, the host database is the source of truth for business data. Client devices work with a local replica for responsiveness, but important writes must follow host-authoritative paths.
In practice, this means:
- define one host instance with clear responsibility
- keep client screens in host-backed mode whenever available
- avoid “local sandbox habits” for productive data
What teams can safely do in client mode today
A strong baseline is already available for common day-to-day work, including:
- sales document list and core draft workflows
- customers, products, tax rules, text blocks, templates, number ranges
- payments and audit log list scenarios that are already host-backed
The key operational benefit is simple: people can work from different desktops while the host remains the authoritative state.
Where teams should still use clear guardrails
Not every workflow has identical remote depth yet. Some areas remain intentionally limited or require explicit host-side handling.
Your best rollout pattern is:
- create a short internal “allowed in client mode” checklist
- document exceptions per feature
- route ambiguous operations to the host owner role
That prevents confusion and keeps data handling consistent during adoption.
Suggested team SOP (30-minute setup)
Use this lightweight SOP for go-live week:
- Name one host owner per tenant or environment.
- Define mode defaults (who uses standalone, who uses client mode).
- Record critical workflows (draft, publish, payment, correction).
- Publish a one-page fallback protocol for connection interruptions.
- Review once per week for the first month.
This is usually enough to reduce accidental local-only behavior without creating process overhead.
Why this matters for compliance and quality
A clean host/client boundary improves two things at once:
- operational predictability in distributed teams
- cleaner evidence trails when you later review document history
If you want to go deeper, continue with:
And for a broader product overview, see Features and FAQ.
For most go-live scenarios, clear ownership plus a lightweight SOP and weekly review cycle is already enough.
Note: This article provides practical product guidance and does not replace legal or tax advice.