Controlled documents in Confluence. Register a page, get it approved, hand your auditor a watermarked copy and a full evidence trail.
Quick start
- Open any Confluence page.
- Find Seal Docs in the byline, next to the author and date. Click it.
- Click Register. We’ve filled in the document ID and title for you.
- Click Submit for review and pick your approvers.
- Approvers open the same panel and record a decision.
- Once approved, click Export copy for a watermarked PDF.
That’s it! Everything below is detail.
Concepts
Controlled document. A Confluence page Seal Docs is tracking. It’s got a document ID, a version, an owner, and a status.
Document ID. Your reference, like QMS-001. We suggest the next one in
the sequence. Change it if you like. IDs are unique within a space, so two
spaces can each have their own QMS-001. A quality system in one space and
an information security system in another number themselves independently.
Give each space its own prefix if you’d rather every ID be unambiguous on a
printed copy.
Version. Drafts start at v0.1. Approval bumps it to v1.0, then
v1.1, and so on. Reopening a document bumps the draft version.
Status. One of:
| Status | Byline shows | Meaning |
|---|---|---|
| Draft | Draft | Not approved. Freely editable. |
| In review | In review | Approvers are deciding. |
| Approved | Controlled | In force. Page may be edit-locked. |
| Obsolete | Obsolete | Withdrawn from use. |
The byline says “Controlled” rather than “Approved” on purpose. Approval is an event. Control is the standing condition.
Document type. Either Policy / procedure or Work instruction. This sets the controlled-copy layout. See Controlled copies.
Registering a document
Open the Seal Docs panel from the page byline and click Register.
We fill in:
- Document ID, the next unused number for the space prefix.
- Title, taken from the page title.
- Type, defaulting to Policy / procedure.
Change any of them before saving. The suggestion’s a starting point, not a reservation. If two people register at the same moment, the second one gets a clear duplicate-ID message rather than a clash.
Who can register
Anyone who can edit the page. You don’t need to be a space admin.
What can’t be registered
Live docs. Live docs are continuously edited by design, so there’s no fixed revision to approve. Convert the live doc to a page first.
Unpublished drafts. A page that’s never been published isn’t visible to us. Publish it, then register.
We explain both in the panel rather than failing when you hit save.
Automatic registration
Space admins can switch on automatic registration. Any new page created directly under a controlled document is then registered as a draft. It inherits the parent’s type and document-ID prefix, and belongs to whoever created it.
Off by default. Growing the controlled set automatically is a bigger decision than reacting to an edit.
Removing a document from control
Registered a page that should never have been controlled? Open the Seal Docs panel and click Remove from document control. Space admins can do the same from the register: space settings, Documents, then Remove… on the row.
The page goes back to being an ordinary Confluence page. Its status, version, owner and revision history are deleted, any edit restriction Seal Docs applied is released, and the document ID becomes free for another document in that space to use. Registering the page again starts a fresh document at v0.1.
This is not the same as marking a document obsolete. Obsolete is a status: the document is still controlled, still in the register, still holding its ID, and the record says it was withdrawn. That’s the right record for a document that really was in use. Removal is for a page that should never have been in the register at all, such as a meeting note swept up by a bulk registration or a draft registered by mistake.
When removal is refused
Once a document has issued a controlled copy, or anyone has confirmed reading it, it can’t be removed. Those records name the document ID, and a copy of it may be sitting on someone’s desk. Mark the document obsolete instead.
That rule is also why freeing the ID is safe. If no copy bearing QMS-001
was ever issued, nothing in the world is pointing at it, and the next
document can have the number.
Who can remove
The document owner, or a space admin. Registering only needs edit access to the page; removing needs one of those two.
Your distribution log and read confirmations are never deleted. They’re append-only, and they stay in your audit evidence exports whatever happens to the register.
The approval workflow
One path, always the same: Draft, In review, Approved. There’s no workflow builder, and that’s deliberate. One path means nobody can set it up wrong, and your auditor sees the same process on every document.
Submitting for review
From the panel, click Submit for review and pick your approvers.
Your space might have required approvers configured. They’re added to every round automatically. You can’t remove them, and anyone you pick is added alongside them.
Your space might also set a minimum approver count. If the round’s short, we’ll say so rather than letting it through.
Everyone on the round gets an @mention comment on the page.
Recording a decision
Approvers open the panel and choose Approve or Reject.
- A change summary is optional, and gets recorded on approval.
- A comment is required to reject. Why something was rejected is part of the audit record.
How rounds resolve
Approval is unanimous. Every assigned approver has to approve. One approval doesn’t advance the document. The round stays open until the last person decides.
One rejection ends the round straight away. The document goes back to draft and the round clears. No reason to wait for the rest.
On approval the version bumps, the effective date is set, the review-due date is worked out, and a revision entry is added.
After approval
Reopen for revision puts an approved document back to draft so you can edit and re-approve it. The previous approved state stays in the revision history.
Mark obsolete withdraws a document from use. The page stays restricted, and the document stays in the register under its own ID. That’s the point. If instead the page should never have been registered at all, see Removing a document from control.
Controlled copies
A controlled copy is a watermarked PDF. We generate it server side and record it in the distribution log at the moment the bytes are made.
Two ways to export:
- Export copy in the Seal Docs panel.
- Export controlled copy in the page’s
...menu.
Both do the same thing. The panel button’s easier to find.
What’s on every copy
- Document ID, title, version, status.
- Owner, approver, effective date.
- How long the printed copy stays valid.
- A render fingerprint and a content hash, so a copy can be tied back to exactly what was approved and how it was rendered.
- A status watermark. Drafts and obsolete documents get their own, so a stale printout can’t pass as current.
Layouts
Policy / procedure. Cover page, revision history, then the body. Plus a wet-ink signature page if you want one. The control block sits at the front, where an auditor looks first.
Work instruction. Compact header, the body, then revision history at the back. Content’s on page 1, because a work instruction gets read at the workstation.
Neither is more correct. No standard prescribes where revision history goes. ISO 9001 asks for the information, not the layout.
Edit drift
If an approved page gets edited, we notice. The byline and the panel both say the page has been edited since approval, and the controlled copy carries the same notice. The document stays approved unless your space is set to reopen on edit.
It’s the honest answer to “is this copy still what was signed off?”
Images
Images embedded in the page come through into the copy.
| Limit | Value |
|---|---|
| Per image | 1 MB |
| All images in one copy | 2.5 MB |
If a page’s images go over the total, we refuse the export rather than handing you a copy with pictures missing. A controlled copy is evidence, and an incomplete one is worse than none.
The panel warns you before you click Export, so it shouldn’t come as a surprise. A single image over 1 MB is skipped and marked in the copy.
Read confirmations
Approved documents can be acknowledged. Open the panel and click Confirm I have read this.
Confirmations are version scoped. A confirmation against v1.0 stops counting once v1.1 is issued, and the export marks it as no longer current. That’s what ISO 9001 clause 7.5.3 awareness actually needs.
The panel shows who’s confirmed. The full list exports as CSV or JSON.
Bulk registration
Space admins can register many pages at once. Space settings, then Bulk register pages.
- Choose a scope: this whole space, or a page and everything beneath it.
- Check the preview. Pages already controlled are marked and skipped. Live docs are flagged and can’t be included.
- Set the document-ID prefix, starting number, and owner.
- Apply.
Pages land in draft. This is bulk registration, not bulk approval. Every document still goes through a real approval round. There’s no shortcut that stamps historical approvals onto new records, because that wouldn’t be evidence.
A subtree preview lists pages in Confluence’s own tree order, so document numbers follow the hierarchy.
The preview caps at 500 pages. Register a smaller subtree and run it again if you hit that.
Registered more than you meant to? The Documents tab has a Remove… button on every row, so a too-broad run is undone from the same screen. See Removing a document from control. There’s no bulk remove to match bulk register. One request that empties a space’s register is a worse thing to have than the problem it solves.
Space settings
Space settings, then Seal Docs. Space admins only.
Control policy
| Setting | Default |
|---|---|
| Required approvers | none |
| Minimum approvers | 1 |
| Review period | 12 months |
| Copy validity | 24 hours |
| Print a wet-ink signature page | off |
| Notify approvers and owners | on |
| Restrict editing to the owner once approved | on |
| Reopen as draft when an approved page is edited | off |
| Automatically register new pages under a controlled document | off |
Restrict editing applies a Confluence edit restriction on approval, and releases it when the document is reopened. Space admins bypass Confluence restrictions, so they’re unaffected.
Reopen on edit is the more disruptive of the two edit responses. It changes workflow state rather than just a display, so it stays opt in. Turn both this and restriction off and anyone can edit an approved document while it stays approved. The settings screen will warn you.
Wet-ink signature page prints blank signature lines, on policy copies only. It isn’t an electronic signature record. ISO 9001 asks for evidence of approval, which the approval history already gives you.
Appearance
Pick a theme preset, font, accent colour, paper size (A4 or Letter), date format, and the “uncontrolled when printed” wording. Add your organisation logo and name for the cover.
Compliance fields are locked and only cosmetics are open, so you can’t configure yourself out of compliance.
Changing appearance changes the render fingerprint, so copies issued before and after won’t fingerprint-match. That’s correct, and it’s rather the point of having a fingerprint.
Audit evidence
Space settings, then the Exports tab. Space admins only.
Three files, each as CSV or JSON:
Document register. Every controlled document with ID, title, type, status, version, owner, effective date, review-due date, and the approvers of the current revision.
Distribution log. Every controlled copy ever generated: who exported it, when, the filename, the version and status at the time, the render fingerprint, the content hash, and whether any images were left out.
Read confirmations. Who acknowledged what, when, and whether that confirmation is still current.
Together they’re the bundle an auditor asks for. Generate them on the day, in front of them, if you like.
Notifications
We notify people through Confluence itself, as comments that @mention them. Confluence then handles the bell and email the way it does for any other mention. Seal Docs never sends email and never handles email addresses.
| Notification | When |
|---|---|
| Review requested | A round opens. Goes to every approver. |
| Reminder | Every 3 days, to approvers who haven’t acted. |
| Outcome | A round resolves. Goes to the owner. |
| Review due soon | 30 days before the review date. |
| Review overdue | Past the review date, repeating weekly. |
| Edited while approved | An approved page gets edited. |
| Reopened on edit | An edit automatically reopened the document. |
Cadences are fixed. No per-space reminder knobs, on purpose.
Space admins can switch notifications off entirely.
Permissions
| Action | Who |
|---|---|
| Register a page | Anyone who can edit it |
| Submit for review | The owner |
| Approve or reject | Assigned approvers |
| Reopen, mark obsolete | The owner |
| Export a controlled copy | Anyone who can view the page |
| Confirm reading | Anyone who can view the page |
| Space settings, bulk, exports | Space admins |
We check Confluence’s own permissions. Seal Docs doesn’t add a permission system of its own.
Limits
| Limit | Value |
|---|---|
| Per image in a copy | 1 MB |
| All images in one copy | 2.5 MB |
| Bulk preview | 500 pages |
| Document ID length | 30 chars |
| Title length | 200 chars |
| Audit export | 5000 rows |
Long documents are fine. A 180-page document with images exports in about 6 seconds. Image count matters more than page count.
What Seal Docs doesn’t do
Worth saying plainly, so you can rule it in or out quickly.
No electronic signatures. ISO 9001 clause 7.5 asks for control, approval, and versioning, not a cryptographic signature. If you’re FDA regulated and need 21 CFR Part 11, we’re not the right tool.
No workflow customisation. No branching, no conditional logic, no custom states. One path only.
No quorum approval. Every assigned approver has to approve. There’s no “any 2 of 5” option.
No template editor. Choose a layout and cosmetics. The audit-relevant structure is fixed.
Not a long-term archive. We store records in Atlassian’s Forge storage, which is a working store rather than a multi-year records archive. Export your evidence regularly and keep it wherever your retention policy says it belongs.
We don’t grant certification. Seal Docs supports your document-control practice. Your process earns the certificate. We just make it provable.
Troubleshooting
“This page is a live doc.” Live docs can’t be registered. Convert it to a page.
“This page has not been published.” Publish the draft, then register.
“That document ID is already in use.” Another document in this space has it. A document in a different space never clashes. Pick another.
“…cannot be removed because a controlled copy has been exported.” The document has produced evidence that names its ID, so it stays in the register. Mark it obsolete instead.
Export refused, images too large. The page’s images are over the 2.5 MB budget. Remove or shrink a few. The panel shows you the totals.
Export refused, copy too large. The rendered PDF came out bigger than a single response can carry. Usually the same fix: fewer or smaller images.
“You need space admin permissions.” Settings, bulk registration, and audit exports are space admin only. Ask a space administrator.
An approver can’t access the page. We refuse the submission if an approver can’t read the page. Grant access, then submit again.
Approval isn’t advancing. Approval is unanimous. Check the panel to see who hasn’t decided yet.
Your data
Seal Docs runs entirely on Atlassian’s infrastructure and is eligible for the Runs on Atlassian program. It makes no outbound network calls. Your data stays in Forge storage inside your own Atlassian environment. We operate no servers and hold no copy of your content.
Seal Docs records people by their Atlassian account ID only. Names are looked up from Confluence whenever they are shown, in the app, on controlled copies and in exports, and are never stored. Comments and revision summaries are stored as typed.
The app writes diagnostic logs through the Forge platform, which we can read to diagnose faults. They record account IDs, page and document identifiers, outcomes and timings, not page titles, comments or names. Atlassian keeps them available for 30 days.
Full detail is in the privacy policy.
Support
Email hello@ocupi.com.au.
Tell us your Confluence site, the document ID, and what you expected to happen. We can’t see your data, so we’re working from whatever you send us.
Ocupi Technologies