About Customers Ideas Log in Book an RFP walkthrough
Works with your stack

Integration Documentation

Version 1.1 · Issued 18 August 2026

Keep the systems you already rely on. Yendou adds governed workflows without requiring rip and replace.

Where Yendou sits

Yendou connects to enterprise identity, email, collaboration, signature and content services while your CTMS, eTMF and document repositories remain systems of record. Interfaces are least privilege, tenant scoped and auditable.

DocuSign · Adobe Acrobat Sign · Veeva Vault · Outlook · Google Workspace · CTMS · eTMF

How to read capability status

Every capability on this page carries one of four labels, so you can tell a standard connector from an implementation pattern before you scope the work.

Available
Standard capability supported by current Yendou evidence.
Configurable
Supported through tenant configuration or an agreed implementation pattern.
Scoped
Connector or interface must be defined and accepted during implementation.
Customer validation
Customer procedures, intended use and validation remain part of compliance.

Integration principles

  • No rip and replace. Existing repositories and operational platforms can remain authoritative.
  • Least privilege. Every connector is limited to approved users, scopes, libraries, accounts and workflow actions.
  • Tenant isolation. Connected content inherits Yendou’s organization boundary, roles and row level security.
  • Controlled synchronization. Only workflow relevant information is ingested or updated, under explicit rules.
  • Portable outputs. Word, Excel, PDF and structured exports support downstream systems and exit requirements.
  • Human governance. Source visibility, SME routing, review and approval remain part of the workflow.

Capability matrix

Outlook and Microsoft 365
Available Microsoft Graph OAuth 2.0, webhooks, governed email sync and approved sending. Connection typically takes about two minutes.
Microsoft Teams
Available Notifications, task routing, SME review, approvals and links to Yendou workflows.
SharePoint
Available Microsoft Graph connection to approved tenant libraries under invoking user permissions.
Google Workspace and Gmail
Available Google OIDC and OAuth 2.0 for identity, email synchronization and approved sending.
DocuSign
Available OAuth 2.0 and webhooks for document e-signature workflows.
Adobe Acrobat Sign
Available Platform integration for e-signature workflows.
Veeva Vault
Configurable Customer specific migration and exchange pattern, tested in a Vault sandbox before production promotion. No standard prebuilt integration.
CTMS and eTMF
Configurable Vendor neutral API, file or controlled export and import pattern defined during implementation.
Available versus configurable

Outlook, Google Workspace, SharePoint, DocuSign and Adobe Acrobat Sign are available platform integrations and can typically be connected in about two minutes through provider authorization. Veeva Vault, CTMS and eTMF remain configurable implementation patterns.

Microsoft 365 and Google Workspace

Outlook and Microsoft Graph

  • OAuth 2.0 authentication. Access and refresh tokens are envelope encrypted and never stored in plaintext.
  • Webhook and synchronization services ingest only workflow relevant email using explicit matching rules.
  • Read visibility can be limited to participants, subject or full body. Delegated sending requires explicit authorization.
  • Thread specific approval overrides user and account defaults, and every email decryption records user and timestamp.
  • Provider authorization and rate limits remain in force.

Teams, SharePoint and Copilot

  • Teams supports notifications, task routing, SME review, approval and direct links to governed Yendou items.
  • SharePoint libraries are connected through Microsoft Graph and restricted to approved tenant libraries and the invoking user’s permissions.
  • An authenticated, tenant scoped MCP service can allow approved Microsoft 365 Copilot agents to query permitted Yendou content.
  • Microsoft Entra ID OpenID Connect is the standard enterprise single sign on method with just in time provisioning. SAML is not used in the standard integration. SCIM can be scoped when required.

Google Workspace

  • Google OpenID Connect supports identity and just in time provisioning.
  • Gmail integration uses OAuth 2.0 provider APIs and notifications for synchronized email and approved sending.
  • The same tenant permissions, encryption and relevance filtering principles apply to connected Google accounts.

E-signature and documents

DocuSign and Adobe Acrobat Sign are both available platform integrations. Provider authorization typically takes about two minutes. Envelope templates, signer routing, callback events, evidence return and retention responsibilities remain configurable.

Microsoft Word
Import, process, review and export while preserving the required output structure.
Microsoft Excel
Structured source ingestion and output for questionnaires, trackers and customer templates.
PDF
Source ingestion and controlled document handling. Editable output depends on the workflow.
Structured export
Content, metadata, users, approvals, RFIs, responses, available audit history, taxonomies and configuration.
Word add-in Scoped

A native Word add-in is not part of the documented standard configuration. If it is mandatory, define it as a production readiness requirement before contract signature.

Veeva Vault, CTMS and eTMF

Yendou is designed to sit beside regulated systems of record. The implementation selects the minimum integration needed for the target workflow while preserving ownership, auditability and the source system’s authority.

Veeva Vault Configurable

  • Yendou does not claim a standard prebuilt Veeva Vault integration.
  • The agreed migration or exchange pattern is configured and tested first in your Veeva Vault sandbox.
  • After sandbox migration testing and acceptance, the approved configuration and data flow are promoted to production.
  • Typical pattern: approved document or metadata exchange through available Vault APIs, controlled export and import, or a customer managed integration layer.
  • Vault remains the authoritative repository when required. Yendou manages the operational workflow and governed reuse around that content.
  • Implementation scope must define object types, document versions, metadata mapping, rendition handling, permissions, write back and error reconciliation.

CTMS and eTMF

Reference data
Controlled import or API retrieval for studies, countries, sites, personnel and identifiers.
Workflow handoff
Event or batch exchange for assignments, milestones, status and approved outputs.
Document filing
Approved export or package to the eTMF with source references, metadata and evidence as agreed.
Reconciliation
Deterministic identifiers, retry and error queue, exception reporting and acceptance thresholds.
Exit and portability
Structured export of Yendou content and metadata for customer controlled transition.
System of record rule

The interface specification must state which system owns each data element and which direction is authoritative. Bidirectional synchronization is not assumed unless it is explicitly designed, tested and accepted.

Integration security model

Authentication
OAuth 2.0 and OIDC where supported. No shared user credentials in the standard pattern.
Secrets
Connected service tokens use AES-256-GCM envelope encryption and are never stored in plaintext.
Authorization
Customer roles, invoking user permissions, approved accounts and libraries, and provider scopes.
Data minimization
Only workflow relevant content and fields are synchronized.
Network
TLS 1.2 or above in transit. Controlled egress and allowlisting can be scoped for partners.
Tenant isolation
Organization scoped transactions and PostgreSQL row level security.
Audit
Provider events, application actions, decryption events and workflow approvals are logged as applicable.
AI
Connected content is not used for model training, and inference can be disabled at tenant level.

Email relevance filtering

  • Synchronize messages sent from Yendou, messages that are part of an existing Yendou conversation, or messages explicitly configured for synchronization.
  • Synchronize when participants match an approved contact or research site record.
  • Do not synchronize all internal domain messages or unmatched messages by default.
  • Use deterministic matching rather than AI or fuzzy classification for relevance decisions.
Default deny

Connected accounts, delegated sending and elevated content visibility require an active account and the applicable owner, user or organization authorization. Requests without authorization are denied.

Implementation playbook

  • Confirm outcomes. Define the workflow, users, systems of record and measurable acceptance criteria.
  • Classify the interface. Select standard connector, configuration, file exchange, API or customer managed integration layer.
  • Map data and authority. Define identifiers, fields, versions, ownership, retention and write back rules.
  • Approve security. Review scopes, service accounts, libraries, encryption, transfer path, logs and incident contacts.
  • Configure and test. Use representative non patient data, negative tests, reconciliation and permission testing.
  • Validate and accept. Capture evidence, deviations, customer validation and production readiness approval.
  • Operate and change. Monitor failures, rotate credentials, review access and control connector and version changes.

Minimum interface specification

  • Business owner, technical owner, data protection and security contacts, and support route.
  • Source and target systems, environments, endpoints, authentication and network controls.
  • Data objects, field mapping, identifiers, direction, frequency, volume and latency expectations.
  • Authorization model, approved scopes, audit events, retention and deletion responsibilities.
  • Error handling, retry, reconciliation, monitoring, service levels and change notification.
  • Test data, acceptance thresholds, validation evidence, rollback and go live approval.

Responsibility and readiness

Yendou provides
The documented connector or the agreed interface, Yendou tenant, role, encryption and audit controls, monitoring of Yendou side failures, and release and change information for Yendou managed components.
You provide
API entitlement, tenant approvals, credentials and a test environment, approval of data fields, source authority, retention and permitted users, and notice of tenant, API, workflow or policy changes.

Pre-production readiness

  • Architecture and data flow approved.
  • Permissions and service ownership approved.
  • Representative data and volume tests passed.
  • Negative authorization and error path tests passed.
  • Reconciliation and support procedures accepted.
  • Customer validation and change control evidence complete where required.
  • Production credentials, monitoring and incident contacts active.

Evidence basis. Consolidated from Yendou architecture, email security, data protection, DPA and enterprise diligence materials reviewed through 18 August 2026. Customer specific commercial terms and named customer information are excluded.