There's a lot of documentation around the Legalesign platform - but if you're like me then
you'll want to send an example document as quickly as possible - because that's what makes
the magic happen. In this article we'll walk through how to use the new Document Viewer component in compose mode to create a seamless document preparation and sending experience for your users.
On the Legalesign system, an organisation has one or more groups with reusable templates that know a lot about the fields (including signature boxes) and roles of each recipient you want to send a document with a particular experience.
Each of these means a specific thing on the Legalesign platform, and generally in the e-signature industry. A firm grasp will help you use Console or the API, so let's explain what each of them means!
If you're building a CRM, customer portal, or line-of-business application, you've likely encountered the challenge of getting documents signed. The traditional approach—exporting PDFs, emailing them, and tracking signatures manually—creates friction for both your team and your customers.
The Legalesign Document Viewer's compose mode solves this by embedding document preparation directly into your application. Your users can add signature fields to pre-generated documents without leaving your system.
If you're building integrations today, you already know REST. It's reliable, familiar, and here to stay. GraphQL doesn’t replace it outright, but it does give you a different way to think about retrieving and shaping data. In the context of a Legalesign integration, we treat GraphQL as a first-class API, so every part of the platform is available through it. If your project starts asking for custom views, or more complex functionality, GraphQL is where you can find that capability.