Integrations
What can connect, and what is involved.
For every connection we state what records are involved, which direction information flows, the timing limits, who is responsible for the data, and what support covers. We do not imply universal compatibility; a logo is not a commitment.
How we label a connection
Five statuses, stated plainly.
- Available
- Can be demonstrated in the offered environment; scope and limitations are stated.
- Configurable
- Supported through configuration within a stated scope.
- Custom scoped
- Built for an engagement, with its own stated boundaries and support.
- Pilot
- Limited access; eligibility and limitations are stated before use.
- Planned
- Not yet available. Never described as a present benefit.
The integration register, listing each named connection with its status, is published after verification. Ask about a specific system in your inquiry and we will answer with its current status.
Trust
Trust is specific.
We publish accurate descriptions of permissions, change history, data handling, and support commitments. Security certifications, uptime figures, and response guarantees appear here only with current evidence behind them.
- Identity and access: one sign-in across the ecosystem, with roles that are granted, revocable, and never inferred from an email domain.
- Data ownership: each application owns its defined operational facts; overviews interpret, they do not duplicate.
- Change history: who changed what, when, and on what evidence, kept with the work.
- Support scope: stated per connection and per application, not assumed.