# Integrations overview

DoorOps integrations are tenant-scoped. Nothing leaks across organisations.

## Native connectors

Verified, first-party connections. Use these when they match the system you already run.

| Provider | Lite | Growth |
| --- | --- | --- |
| [Joblogic](/docs/integrations/joblogic) | Connect, import customers, send a reviewed PDF back to a matched job | Full historical import, encrypted archive, replay, event intake for already-imported jobs |
| [eWorks Manager](/docs/integrations/eworks) | Connect and import the customer directory | Full historical import and archive-first mapping |
| [BigChange](/docs/integrations/bigchange) | Connect, import contacts, optional JobWatch PDF handoff | Full REST historical import plus optional JobWatch |

Native does **not** mean live two-way sync. Historical import and reviewed one-way delivery come first. Live sync is called out as not available until a provider contract exists.

## If we do not have your system

That is the default path, not a gap you have to wait on.

Use [build your own integration](/docs/integrations/custom):

1. **REST API** for reads and safe writes
2. **Signed webhooks** so DoorOps tells your system when something changed
3. **Tenant MCP** if the consumer is an AI agent
4. **CSV / structured file import** for a one-off history dump
5. **Zapier, Make or Power Automate** on top of the webhook + API pair

Accounting (Xero, Sage, QuickBooks) and extra CRMs are on the roadmap. Until a native connector ships, the same public surfaces work.

## Rules that never change

- Exact provider IDs, never fuzzy name matching
- Encrypted source archive for anything we cannot map 1:1
- Stripe entitlements gate commercial access
- Tenant roles still apply on top