Security & Compliance
Lynx Compliance - Connectors (External Data Sources)
Wires the shared Lynx connector framework into compliance evidence collectors, and gates the evidence connectors behind compliance.pro.
lynx_compliance_connectors
· v19.0.2.0.0
· Add-on
What this solves
Lynx Compliance - Connectors
Bridges the shared connector framework (lynx_connectors) into the compliance evidence collector path. The connector record, registry and REST client now live in lynx_connectors so any Lynx app can use them; this module adds the compliance-specific wiring and keeps the evidence connectors gated behind the compliance entitlement.
Most evidence lives outside Odoo: the IdP knows who has MFA, the cloud provider knows what storage is encrypted, the SIEM knows what logs were forwarded. An external_api collector names a saved lynx.connector and a resource type, and this bridge runs the pull and stores the rows as evidence.
Key Features
Collector wiring - external_api collectors call a registered connector through connector_id / connector_resource_type and receive a unified result shape suitable for evidence storage.
Shared connector reuse - builds on lynx.connector from lynx_connectors, so a connection configured once serves both compliance and other apps.
Entitlement gating - kept behind compliance.pro with the compliance.connectors quota, so evidence connectors remain a paid part of the compliance product.
Role access - grants the compliance officer and read-only auditor the matching connector permissions.
Integrates With
lynx_connectors - the shared connector framework this bridge builds on.
lynx_compliance_evidence_collectors - the channel for external_api collectors.
lynx_compliance_connector_patrii, lynx_compliance_connector_aws - provider-specific implementations.
Try Lynx Compliance - Connectors (External Data Sources) on your team.
Free trial, no credit card. Talk to sales when you're ready.