At a glance
Connections are planned or access dependent. Evaluate a defined source-to-destination workflow before relying on a provider name or logo.
01 / Current state
What is planned, and what still needs access.
No named provider connection is active on this public website. The table records the source product states, not availability commitments.
| Connection | State | Boundary |
|---|---|---|
| Microsoft 365 | Planned | Per-tenant connection is planned; no live connection is available on this website. |
| Google Workspace | Planned | Per-tenant connection is planned; no live connection is available on this website. |
| Accounting | Access dependent | A provider and authorised production credentials have not been selected. |
| Leica DISTO X6 | Access dependent | Capture depends on licensed SDK access and real-device validation. |
| iOS and Android | Planned | Native applications are a separate delivery stream and are not available here. |
02 / Define the job
Start with the handover you need to improve.
Describe the event, source record, destination and accepted result before selecting a provider. An approved invoice draft, a received email and a device reading have different data and authority needs.
Name the workflow owner, provider-account owner and data owner. Agree which fields may move and what happens when the connection is unavailable.
03 / Verify the result
A useful connection needs more than authorisation.
The production application must demonstrate the right account and scopes, tenant isolation, duplicate and retry handling, failure visibility, audit history and revocation. No external provider credentials are connected by a marketing example.
- Confirm the source of truth and permitted data direction.
- Test duplicate, timeout and provider-outage behaviour.
- Record who initiated the action and what changed.
- Test disconnect, export and deletion responsibilities.
04 / Next step
Bring one redacted source-to-destination example.
Use a workflow conversation to define a specific integration proof plan. Provider choice, delivery, pricing and operational commitments need separate agreement.