Skip to main content
Version: 4.1 (2026 H2)

Use cases

This chapter describes how primedocs is connected to specific third-party systems and services. While the other chapters describe the individual interfaces (Connect, Select, API, MCP), the use cases show how those building blocks work together for a particular system.

Embedding primedocs Web​

primedocs Web can be embedded as a user interface into other web applications. Ready-made integrations exist for the following systems:

  • CMI: Integration into CMI.
  • SharePoint: Integration into Microsoft SharePoint.
  • Teams: Integration into Microsoft Teams.

Embedding into your own web application​

Besides the ready-made integrations, primedocs Web can be embedded generically into a web application of your own. The route for this is via Connect Session Templates: the host system starts a session and embeds the URL returned by primedocs in an iframe. Feedback on the outcome of the document generation is delivered by the BrowserParentPostMessage command, which sends a message via window.parent.postMessage to the embedding window.

Processing generated documents further​

Not every integration embeds a user interface. A third-party system can also come into play only after the document has been generated:

  • Electronic signatures: Prepare documents for e-signature services such as DeepSign, Adobe Acrobat Sign, or DocuSign via placeholder texts in the templates.
  • ePost (digital letter): Deliver generated documents digitally or physically through the ePost Communication Platform.