Use caseContract management software
Lawyers on Clauseway download each agreement, mark it up elsewhere and upload a copy. Building a viewer in house would be a second product.
A 214-page agreement opens on page one, in the browserThe host product decides who may do whatLawyers never leave the contract page
The agreement displays in the browser, inside Clauseway. No download, no local copy, no desktop reader.
source · MSA Northwind Logistics v4.docxAnnotate, print and download · set by the customer admin
Ahmed Rahimi opens a 214-page agreement in Clauseway and gets a download button. That is the daily routine for the in-house legal teams who buy Clauseway: store the contract in the product, download it to read it, comment in a desktop reader, upload a new copy. Support tickets pile up about scans that do not preview and long agreements that freeze the browser tab. The product holds the contract but cannot show it.
Clauseway's answer is to call a component instead of writing one. Its back end calls the conversion API, its contract page hosts the viewer as a web component, and each user's rights travel with every display. Clauseway keeps its screens, its users and its permissions; the viewer renders what it is asked to render.
Keep one chain in mind while you read: the file is converted on the server, displayed inside the host product, and every action follows the rights the host product passes. The nine steps take it link by link, from Marcus's first test file to Ahmed's renewal week.
Marcus Lindqvist, lead developer, wants one real contract open inside a Clauseway page before Friday.
Marcus picks a hard test file: a 214-page master services agreement saved as a Word file, with a pricing spreadsheet as an annex and a scanned signature page at the end. Clauseway's back end sends it to the conversion API, documented as a REST API.
The viewer ships as a web component, with an SDK. Marcus adds it to Clauseway's contract page and drives the display from the back end: which document, for which user.
The agreement opens on page 1 and loads page by page. Display time does not depend on the weight of the file, so the 214 pages feel like 2.
When a user opens a contract, Clauseway decides what that person may do, then passes it with the display. The viewer applies it: view, print, download, annotate, transform or share, each one allowed or blocked.
The viewer works. Now Nadia Okafor, head of product, and each customer admin shape it: tools, roles, and a masked copy for outside counsel.
Nadia sets which functions and menus appear in the viewer for this use. Legal users get search, highlight, comment, thumbnails and comparison. Stamps and shapes are hidden.
At Halden Pharma, Grace Whitfield runs Clauseway for the legal department. In Clauseway's settings page she sets what each of her roles may do in the viewer. Clauseway turns her choices into the rights it passes on each display.
Halden needs outside counsel to review the agreement, without the pricing annex. In the viewer, Ahmed masks the prices and the bank details. A distributable version is produced, and the full internal version stays in Clauseway.
At Halden Pharma, Ahmed Rahimi reviews renewals all week without once leaving Clauseway.
Ahmed opens the Northwind agreement from his renewal list. He searches for limitation of liability, highlights clause 11.2 and leaves a comment for Lena Ortiz, the business owner. The comment carries his name and the time. The source file is untouched.
Northwind sends back version 5. Ahmed compares it with version 4 side by side. The differences show in the text and in the layout. He asks the assistant in the viewer to explain what changed, then checks each point against the page.
Document actions are recorded with their author and their time. Because every function the interface offers is also a call, Clauseway reads the comments back through the API and shows them in its own activity feed.
The viewer does not guess who a user is. Clauseway passes one of three levels with every display, and each level opens a different set of tools.
The business owner reads the agreement and searches it. No annotation, no download, no print.
After that: the contract opens in place, with the reading tools only.Paralegals and outside counsel leave comments. The source file is never modified.
After that: comments are stored apart and read back into Clauseway's feed.Counsel can take the file out of the product. That is why only the customer admin grants it.
After that: every download and every shared version is recorded.It decides nobody's rights. It keeps no user list. It changes no source file. Across the nine steps on this page, every permission comes from Clauseway, set by Clauseway's product team and by each customer admin.
The viewer converts, displays, annotates and compares. The assistant in the viewer explains a document and cites its page; the lawyer reads the page and decides.
One agreement, Northwind's, and one customer, Halden Pharma, gave these counts. Your formats and your permission model will give you yours.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
An embedded viewer ships when the product lead, the engineers and the lawyers using it all agree. What each of them takes away:
Users leave your product every time they need to read a file.
A viewer is a product of its own, and not the one you sell.
Download, open elsewhere, comment, upload again: that is your morning.
With the formats your support team hears about most. Take ten real files that do not preview today and run them through the conversion API in a test environment.
Then place the component in one page of your product, for one internal team, before any customer sees it.
Let's talk
Bring the files your users struggle with and tell us how your product handles permissions. We will walk your developers through the first display.