Connection is not authority.
A connection can supply evidence without granting action authority. Enterprise Hub resolves the principal, registered operation, account, target, and verification path separately.
CONNECTORS
Connect broadly. Govern deeply.
Enterprise Hub connects approved systems for scoped evidence, events, and operation-specific actions. Access, provider binding, read-back, and certification remain separate.
Capability matrix
Connector capabilities remain independently governed.
Evidence access, events, actions, provider binding, and read-back are enabled separately for each connector and deployment.
| Connector group | Evidence | Events | Governed actions | Read-back | Status |
|---|---|---|---|---|---|
| Microsoft 365 | Supported where configured | Scoped by source | Operation-specific | Supported where bound | Deployment-specific |
| Google Workspace | Supported where configured | Scoped by source | Operation-specific | Supported where bound | Deployment-specific |
| Jira | Supported where configured | Scoped by source | Operation-specific | Supported where bound | Deployment-specific |
Swipe or scroll horizontally to inspect all capability columns.
Where supported, provider acceptance is followed by read-back before completion is recorded.
Bring one connected action path.
Compare evidence access, action depth, account binding, and read-back for one connected path.
Source-linkedExact approvalVerified outcome
Detect
Plan
Authorize
Verify
Capabilities are enabled and certified by operation, provider, tenant, and deployment.