Clearlane
EN
Clearlane Controlled Documents · Confluence

Document control in Confluence, signed and provable.

When an auditor picks one of your SOPs, the first questions are always the same: who approved this version, and who has read it? Controlled Documents answers both on the page: approvals with electronic signatures, read and understood at every revision, periodic reviews, and an evidence file your auditor can read without you.

  • FDA 21 CFR Part 11
  • ISO 9001
  • ISO 13485

Designed to help teams meet their document control requirements.

Play the demo1:10 · subtitled
Freefor up to 10 users
Runs on Atlassianyour data stays in your Atlassian site
SHA-256each signature bound to the exact content
English · Français · Deutschfollows each person’s language
01

A signature covers what was read. Nothing else.

Each signature records the signer’s name, the date and time, and its meaning: Authored, Reviewed or Approved. Signers confirm with a personal signing password on top of their Atlassian login.

  • A SHA-256 fingerprint of the page as approved
  • Any edit during review cancels the signatures
  • Editing can be locked during review
Signatures of revision 3 with names, dates and meanings
02

Edited after approval? Everyone can see it.

If an effective document is edited later, it is flagged “Edited since approval”, with a link to the approved revision and a comparison.

  • A link to the approved revision
  • A comparison of the changes
  • A register filter for edited documents
A document flagged as edited since approval
03

Read and understood, at every revision.

Choose the people and groups who must read a document. They confirm each effective revision, and a new revision asks them again.

  • Reading progress on the page and in the register
  • CSV export for training records
A reader confirming revision 2
04

Everyone knows what to sign and what to read.

“My controlled documents” lists what each person has to sign, read or review, across all spaces. Each person gets at most one reminder a day, grouping everything they have to do.

My controlled documents: to sign, to read, reviews due
On audit day

What your auditor sees, in one click.

Download a PDF for any document. Add the document control block to a page, and its number, revision and signatures also appear in Confluence’s own PDF exports.

01

The signature manifest

Who signed, when, and with what meaning.

02

The revision history

Every effective revision, with its fingerprint.

03

The read confirmations

By person and by revision.

04

The full audit trail

Lifecycle, signature and read events, time-stamped, for space administrators. Signatures, reads and state changes are written one by one; beyond 30 of the same routine event on one document in an hour, the rest of that hour is grouped into one entry with their count. No one can edit or delete these entries in the app.

Register of controlled documents with status, revision, owner, next review and reading progress

Controlled Documents is designed to help teams meet the document control requirements of FDA 21 CFR Part 11, ISO 9001 and ISO 13485. Validating your system for your own intended use remains your responsibility.

How it works

Three steps, nothing to configure.

  1. Choose Document controlunder the title of any page. It gets a number, such as SOP-0012.
  2. Send the revision for approvalEach approver signs from the page.
  3. At the last signaturethe revision becomes effective and readers are asked to confirm.
Works with Rovo

Ask Rovo where a document stands.

Clearlane Controlled Documents adds a Rovo agent, “Clearlane Controlled Documents”. Ask it where a document stands (status, revision, read confirmations), what is waiting for your signature, or which documents in a space are overdue for review. It only shows pages you can open. It answers from the app’s own records, only with what you are allowed to see, and it only reads: it never changes anything. It works where Rovo is turned on for your Atlassian site; Clearlane adds no AI model of its own.

Permissions and data

The app runs on Atlassian Forge (Runs on Atlassian). It keeps the document records it needs, such as Atlassian account IDs, the names shown at signing, revisions, fingerprints and the audit trail, in Atlassian’s storage for your site.

Signing passwords are stored hashed, never in clear text, in Atlassian’s secret storage. Nothing is sent to our servers or to anyone else.

FAQ

Questions, answered.

Where do I find it?
On any Confluence page, choose Document control under the page title. The space register is in the space’s apps, and “My controlled documents” in Confluence’s apps menu.
Can someone approve without reading the final version?
No. A signature applies to the exact content fingerprinted when it was given. If the page changes during review, the signatures are cancelled and approvers sign again.
Who validates the system?
You do, for your own intended use. Our validation support gives the 21 CFR Part 11 mapping and an OQ test script.
Does it work in French?
Yes. The app follows each person’s Confluence language, in English, French or German, in light and dark themes.
Does it work with Rovo?
Yes. Its Rovo agent answers questions such as “Where does this document stand?” from the app’s own records. It only reads, and only shows what you are allowed to see.
Can approvals follow a set order, or need only some of the approvers?
Yes. Space administrators can define approval templates: who approves, people or groups, with which meaning, and whether everyone signs, one after the other, or at least a given number. The template is chosen at submission and kept with the revision, in the audit trail and in the PDF.
Is it available on Atlassian Isolated Cloud?
Yes. The app is listed on the Atlassian Marketplace for Isolated Cloud. It runs on Atlassian Forge there too, with the same permissions, and its data stays in Atlassian’s storage for your site.
Same family

Clearlane for Quality

Clearlane for Quality: controlled documents, read confirmations, corrective actions, test evidence and a risk register in Jira and Confluence — signed, traceable and kept in Atlassian.

Built and supported by Maxime Ragionieri, founder of Clearlane. Who’s behind Clearlane →

Free for up to 10 users.

Larger teams pay per user, billed by Atlassian on the Marketplace. No setup, nothing to install outside your Atlassian site. See the price for your team size →