PlatformConnector directory

Integrations + connectors directory.

TeamSync coexists. Connectors federate content + permissions + audit with the customer's existing systems of record, so TeamSync extends the stack rather than replacing it.

Identity

Identity providers.

Federation with the customer's IdP. Permissions are evaluated per request against the identity the IdP asserts — see AccessArc, or talk to an integrations engineer.

ProviderIntegration
Microsoft Entra IDSAML / OIDC / SCIM; conditional access pass-through
OktaSAML / OIDC / SCIM
Ping IdentitySAML / OIDC / SCIM
ForgeRock + OneLoginSAML / OIDC / SCIM
Federal — HSPD-12 / FIPS 201 / PIVNative
Customer-managed IdPsStandards-based
Content

Document management + collaboration.

Bidirectional federation with the repositories the content already lives in, permissions carried across the boundary.

SystemConnector
iManage Work + CloudBidirectional federation; matter view; permissions preserved
NetDocumentsBidirectional federation
Microsoft 365 + SharePoint + OneDriveFederation; Copilot scope coexistence
Google Workspace + DriveFederation
OpenText (Content Server, Documentum, eDOCS)Federation; phased migration
Hyland OnBase + PerceptiveFederation
BoxFederation
M-FilesFederation
ShareFileFederation
Vertical apps

Vertical applications.

The line-of-business systems each regulated industry runs on, federated at the content and object layer.

SystemConnector type
Veeva (Clinical, QualityDocs, Vault) — HLSAPI + content federation
Epic + Cerner / Oracle Health — HLSIntegrations per Epic / Oracle programmes
Salesforce Public Sector + Sales CloudObject + content federation
ServiceNow (Service + Public Sector + FSM)Workflow + content federation
WorkdayHR records federation
Procore + Autodesk Construction Cloud + Newforma — AECProject content federation
SLB Studio + Aveva — EnergyEngineering content federation
Tulip + iBASEt + Plex MES — ManufacturingShop-floor content federation
Guidewire + Duck Creek + Sapiens — InsuranceClaims content federation
Axon + Mark43 + Hexagon + Tyler — Law enforcementCase + evidence federation
Avolve EnerGov + Tyler — AEC permittingAHJ-side federation
Coexistence

Where an incumbent stays in place.

eSignature, eDiscovery and capture vendors already under contract keep running. TeamSync handles the regulated side and hands off at the boundary.

eSignature partners

ProviderCoexistence pattern
DocuSignFederation; TeamSync provides eSign for regulated agreements alongside
Adobe SignFederation

eDiscovery partners

ProviderCoexistence pattern
Relativity / RelativityOneTeamSync handles ECA + hold + collection at the source; Relativity hosts review
EverlawSame coexistence pattern

Capture + IDP partners

ProviderCoexistence pattern
ABBYY VantageSpecialist extraction alongside TeamSync IDP
HyperscienceSpecialist extraction

Hyperscaler ML

ServiceMechanism
AWS BedrockModel adapter; per-tenant model selection
Azure OpenAIModel adapter
Google Vertex AIModel adapter
Anthropic + OpenAI + Mistral directModel adapter
Security tooling

Security + observability.

Every platform event streams to the tooling the security team already watches. See Security.

CategoryExamples
SIEMSplunk, Elastic, Sumo Logic, Microsoft Sentinel, Chronicle
CASBPer customer requirement
DLPPer customer requirement
Secrets managementHashiCorp Vault, AWS KMS, Azure Key Vault, Google Cloud KMS, OCI Vault
Build your own

Open API + SDKs.

REST + GraphQL surface. Webhook + Kafka-stream for high-volume content events.

  • Python
  • TypeScript
  • Java
  • .NET
  • Go
  • REST
  • GraphQL
  • Webhooks
  • Kafka stream
API ReferenceREST + GraphQL surfaceDeveloper guidesImplementation patternsIntegration architectureHow federation is wired
Connector review

Map your stack in one session.

Bring the vendor list. An integrations engineer walks each system and tells you what federates, what migrates, and what stays exactly where it is.

Talk to an integrations engineer See the platform