1. Connect a process, not just a product
Integrations reduce repeated data entry and help teams relate employee, device, licence and purchasing information. Their value depends on whether they support a specific operational decision or action. Reading a device record does not imply permission to manage that device, and an employee lookup does not imply every HR field can be updated.
Define the intended process first. Identify required objects, fields, read operations and write operations separately. Lojycal has endpoint-management dispatch paths, identity integrations and employee-system lookups and writes, but these do not establish a live connection in your workspace.
- Confirm each required operation for your provider, plan and workspace.
2. Assign authority at field level
A source system supplies information; an authoritative source is the agreed reference for a particular fact. HR might own employment status while endpoint management owns device state. Neither should automatically overwrite unrelated fields simply because it synchronised most recently.
Document field mappings, formats, identifier rules and conflict handling. Use stable identifiers where possible; names and email addresses can change. Duplicate records need investigation before merging, since two similar names may represent different people or separate accounts.
- Define authority separately for each important field.
- In a fictional case, investigate two records for Alex before linking either to a laptop; a matching display name is insufficient.
3. Treat synchronisation and freshness as separate questions
Synchronisation transfers or updates data. Freshness describes how current that data is for the decision being made. A recently completed import can still contain older source information. Distinguish source event time, last successful retrieval and verification time.
Reconciliation compares expected records or outcomes with observed ones. For a consequential write, verify the resulting source state rather than relying solely on an accepted request. Lojycal's Personio and BambooHR employee operations include preflight confirmation and re-read verification; do not assume identical behaviour across every integration.
- Set acceptable freshness thresholds for each workflow and flag stale or unknown states.
4. Integration status table
The table lists providers with established operational paths. Requires configuration means provider credentials, permissions and workspace settings must be confirmed; it is not a statement that a visitor's connection is enabled. Exact actions can differ by provider and are subject to plan and role gates.
Provider | Status | Established operational scope Jamf | Requires configuration | Endpoint-management dispatch paths Kandji | Requires configuration | Endpoint-management dispatch paths Intune | Requires configuration | Endpoint-management dispatch paths Personio | Requires configuration | Employee lookups and writes with preflight confirmation and re-read verification BambooHR | Requires configuration | Employee lookups and writes with preflight confirmation and re-read verification
- Request the supported action list before committing to a workflow.
- Identity integrations also exist; confirm the specific provider and operations separately.
5. Design permissions and failure handling together
Use the minimum provider permissions needed for the agreed scope. Lojycal organisation membership and roles restrict operations; an external provider credential does not replace those controls. Separate read requirements from write requirements and nominate an owner for permission reviews.
Failures may arise from expired credentials, rejected fields, missing permissions or source limits. Establish who investigates failures and whether retries could repeat an action. A partial synchronisation must not be presented as a complete inventory.
- Test a permission-denied response and an invalid mapping in a controlled pilot.
- Preserve unresolved exceptions and reconcile them before accepting the result.
6. Evaluate with a representative pilot
Choose a small, approved scope that includes a normal record, a duplicate, a stale record and a rejected update. Define expected outcomes before connecting systems. Compare retrieved fields with source records and require read-back for consequential changes where supported.
Judge suitability by coverage, clarity of failures and the effort needed to reconcile results, not by the number of provider logos. Confirm open requirements with the team through /contact and consult /pricing for current commercial options.
- Document unsupported operations and manual review steps.
- Approve broader use only after owners accept the pilot findings and remaining limitations.