Use caseContract management software

An embedded viewer for contracts

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 viewerOpened on page 1 of 214

The agreement displays in the browser, inside Clauseway. No download, no local copy, no desktop reader.

source · MSA Northwind Logistics v4.docx
Actions on this contract
What this user may do

Annotate, print and download · set by the customer admin

01

Why it drags today

At a glance

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.

Clauseway · Contract 58213Viewer
One page, no download. The agreement opens inside the contract page, on page one, whatever its length.
Clauseway · Contract 58213 · TodayWorkspace
Four hops per review. This is the round trip users make now, every time a contract needs a comment.

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.

02

The integration

Marcus Lindqvist, lead developer, wants one real contract open inside a Clauseway page before Friday.

Step 1Conversion

Send a real contract to the conversion API

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.

Word bodyExcel annexScanned signature page
Conversion requestDeveloper portal
The viewer works on its own rendition. Clauseway keeps the original file.
Every format goes through one callMore than 200 formats are converted on the server. Clauseway writes no format code of its own.
Step 2Viewer

Place the viewer in the contract page

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.

Clauseway · Contract 58213Viewer
Pages load as the reader scrolls. Nothing is downloaded to the device.
A real contract opens on day oneThe first milestone is a file users actually have, inside a page they already know.
Step 3Permissions

Pass the user's rights with each display

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.

Display settings · Ahmed RahimiDeveloper portal
The rights come from Clauseway on every display. The viewer stores no user list.
Ask your architects this: should the rule about who reads a contract live in the product your customers pay for, or in a component they never see?
The host product stays the authorityClauseway decides who sees what. The viewer follows the rights it receives, and nothing more.
03

The product fit

The viewer works. Now Nadia Okafor, head of product, and each customer admin shape it: tools, roles, and a masked copy for outside counsel.

Step 4Configuration

Keep the tools legal users need

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.

Viewer configuration · ContractsAdmin console
Functions and menus are set per use case. No code change in Clauseway.
The viewer looks like the jobUsers see the five tools they use. The rest stays out of the way.
Step 5Permissions

Each customer admin maps their own roles

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.

Counsel: annotate and downloadParalegal: comment onlyBusiness owner: read only
Halden Pharma · SettingsWorkspace
Roles live in Clauseway. Grace changes them without a support ticket.
A customer request is a settingWhen Bexley Foods asks for print rights for its counsel, Grace's counterpart there changes one cell. No release.
Step 6Redaction

A redacted version for outside counsel

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.

MSA Northwind Logistics v4 · Annex BViewer
The mask travels with the export. The original file is unchanged.
Sharing stops meaning a second fileThe lawyer shares a masked version from the same screen. Nobody edits a copy by hand.
04

The daily use

At Halden Pharma, Ahmed Rahimi reviews renewals all week without once leaving Clauseway.

Step 7Viewer

Search, highlight and comment in place

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.

Clauseway · Contract 58213Viewer
Annotations are stored apart from the original file.
The review happens where the contract livesNo download, no desktop reader, no new copy to upload. The comment is on the page.
Step 8Compare

Version 5 arrives, and the changes are on one screen

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.

Compare · v4 and v5Viewer
Additions, deletions and changes, with a synchronized display.
Three changes in a 214-page agreementThe lawyer reads what moved instead of rereading everything. The assistant explains, the lawyer judges.
Step 9History

Every action stays on the contract

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.

Clauseway · Contract 58213 · ActivityWorkspace
The activity feed is Clauseway's screen, fed by the viewer's record.
The trail is part of the productWho opened, commented, redacted and shared, and when. Clauseway shows it without storing a second copy.
05

The outcomes

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.

Read

View and search

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.
Annotate

Comment and highlight

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.
Full rights

Print, download, redact

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.
What the viewer does not do

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.

06

The payoff

One agreement, Northwind's, and one customer, Halden Pharma, gave these counts. Your formats and your permission model will give you yours.

0 downloadsto read and comment on a contract. It opens inside the contract page.
1 componentin Clauseway's page, for more than 200 formats, with no format code to maintain.
4 rolesset by the customer admin in Clauseway's settings, with no release.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

What makes these gains possible

One product on screenProduct experienceThe viewer runs inside the host page. Users see Clauseway and its contract, nothing else.
Rights stay with the hostSecurityThe host product passes view, annotate, print and download on each display.
Same call, same rightsIntegrationWhat the viewer's interface does, an API call does too, with the same rights.
07

For your teams

An embedded viewer ships when the product lead, the engineers and the lawyers using it all agree. What each of them takes away:

Product leadership

Heads of product

Users leave your product every time they need to read a file.

  • Documents open inside your own pages.
  • The toolbar shows the functions your users need.
  • Comparison and redaction come with the viewer.
  • Your customers' admins manage their own roles.
CIO and architecture

CTOs and lead developers

A viewer is a product of its own, and not the one you sell.

  • Documented REST APIs, SDKs and web components.
  • Conversion runs on the server, display in the browser.
  • Your back end drives the display and passes the rights.
  • Runs on your servers, in a private cloud or as SaaS.
End user

Your customers' users

Download, open elsewhere, comment, upload again: that is your morning.

  • A long agreement opens on its first page.
  • Search, highlight and comment in place.
  • Two versions compared on one screen.
  • A masked copy shared without editing a file.

How to begin

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

See it inside your own product

Bring the files your users struggle with and tell us how your product handles permissions. We will walk your developers through the first display.

The screens on this page are drawn to show one step at a time, with example data. Clauseway, Halden Pharma and the people named are fictional.

Uxopian Software gives software companies the content building blocks behind their products, through APIs, so their teams can spend their time on what their customers pay for.