Integrations
Connect your sources to the discovery workflow
Bring employee records, device information and preservation activity into Discovery Hub. Choose reporting, native holds or collection capabilities to match the systems your organization uses.
What each connector does
The right approach for each source
Reporting, native holds, local collection and group workflows serve different purposes. The connector determines which capabilities are available.
Reporting
Import source metadata such as accounts, devices, backup status and hold memberships. Use it to review coverage and investigate exceptions.
Preservation in place
Use supported source-system legal-hold APIs to manage custodian coverage from Discovery Hub and audit returned hold information.
Collection to preserve
Copy available Claude and ChatGPT Enterprise records into your environment for retention, legal-hold protection, review and export.
Group workflows
Manage Jamf static computer-group membership for policies defined by your team. Group membership alone does not preserve device files or prevent a wipe.
Connector capabilities
Compare reporting and preservation
Availability depends on Discovery Hub licensing, supported source plans and API permissions. Validate source coverage during implementation.
Scroll horizontally to compare all columns.
| Source | Reporting | Preservation or collection |
|---|---|---|
| Microsoft 365 | Mailbox and OneDrive usage, plus supported Purview eDiscovery metadata. | Supported Purview holds for mailbox and OneDrive data, and mailbox litigation holds. |
| CrashPlan | Devices, backups, archives, cold storage and legal-hold event history. | Native legal holds using a shared Legal Hold Bucket or one hold per Discovery Hub hold. |
| Slack | Legal-hold policies and custodian memberships. | Supported Slack legal-hold policies and custodian assignments. |
| Google Workspace / Vault | Workspace accounts and Vault matters, holds, custodians and export metadata. | Gmail and Drive preservation through Vault, with holds corresponding to Discovery Hub holds, and optional Gemini app holds where the Workspace uses Gemini. |
| Jamf Pro | Computer inventory and static or smart group information. | Static computer groups for your legal-hold policies: one shared bucket or one group per hold. This is a group workflow, not native file retention. |
| Microsoft Intune | Managed devices, ownership, compliance, encryption and check-in health; optional CrashPlan backup comparisons. | Reporting only. |
| Box | Enterprise accounts, legal-hold policies and assignments with observed history. | Native Box legal-hold policies and custodian assignments, organized by Discovery Hub hold. |
| Dropbox | Team members and legal holds with observed history. | Native Dropbox legal holds, one per Discovery Hub hold, for teams with the Dropbox legal holds add-on. |
| Claude Enterprise | Available organization conversation metadata. | Local collection of available chats, messages, files and artifact versions, projects and their documents, Claude Code sessions, code artifacts and, optionally, the Activity Feed, through the compliance API. |
| ChatGPT Enterprise | Available conversation-message log-file metadata. | Local collection of native workspace events, recognized messages and downloadable attachments, plus any further log event types you configure. Verify event mappings and file coverage against the workspace before enabling cleanup. |
Reporting and preservation are licensed separately where supported. AI collection uses each provider's Collection / Preservation license and Preservation Manager. Collection coverage is limited to records available through the source API.
Included HR data feed
Keep custodian records aligned with employee data
The HR data feed is included with every Discovery Hub license and configured from its connector card.
Choose how data arrives
Upload a CSV file, poll a configured server folder or receive CSV and JSON through an authenticated API.
Control matching and mapping
Map source columns to employee fields and choose a matching key, such as Employee ID. Review new fields and missing-column behavior before applying an import.
Monitor the result
Review import history and choose completion or issue notifications for designated recipients.
Implementation and control
Configure access, validate coverage and monitor results
Evaluate source reporting
Supported unlicensed connectors offer a manual import of up to ten source metadata records into separate demo storage. Source credentials and API permissions are required. Licensed connectors use their configured production workflows.
Review exceptions
Use preservation-audit warnings, configurable CrashPlan backup checks and collection history to identify issues. One recent completed backup across a custodian's devices satisfies the CrashPlan custodian freshness check.
Connect your internal systems
Directory lookups, configurable Active Directory group synchronization, authenticated REST APIs, signed webhooks and SIEM feeds support integrations managed by your administrators.
Validate AI collection
Confirm provider API access, custodian matching, original dates and attachment coverage before enabling cleanup. Unrecognized events remain preserved for review. Source-deleted or expired records cannot be recovered by collection.
Plan the integrations your team needs
Review source access, deployment requirements and the appropriate reporting or preservation licenses in a guided demonstration.