Skip to content

Oktul SignPlus for Confluence

Oktul SignPlus for Confluence signs a page where it is:

  1. SignPlus renders the page to PDF inside Atlassian.
  2. Dokobit (opens in a new tab) collects qualified electronic signatures.
  3. The signed document is attached to the same page.

Afterwards, the byline says whether the page still matches what was signed. SignPlus stores a SHA-256 of the page’s space, id and version, and every edit moves the version.

A qualified signature, through Dokobit

Signers sign at Dokobit (opens in a new tab) with their own eID: Smart-ID, ID card, Mobile-ID or another supported method (opens in a new tab).

Dokobit’s trust status and data location are Dokobit’s statements, not Oktul’s commitments.

The level comes from the eID, not from SignPlus

E-signature levels is QES only by default. Choose QES and AdES in the settings to accept advanced signatures too. Test mode has no legal effect.

What it does

  • Signs from the page. Pick colleagues by name, partners by email, or a whole group.
  • Up to 25,000 signers. It runs in the background, so closing the page does not stop it.
  • Attaches the signed file when the last person signs.
  • Reports edits after signing in the byline, the panel, the REST API and a webhook.
  • Locks the page while it is out: editing to SignPlus, viewing to participants, if you choose.
  • Prints the page as Confluence shows it, including Jira and Assets tables, in your company’s font, logo, header and footer.
  • Starts from outside Confluence: Jira automation, a Confluence rule or the REST API.

What it does not do

  • It cannot sign for anyone. Each signer uses their own eID.
  • It cannot make a page unchangeable. A space administrator can always remove a restriction. SignPlus guarantees a change is detected.
  • It does not say what changed. It links to Confluence’s comparison of the two versions.
  • Test mode is not signing. New installations start there: watermarked, not binding.
  • Real signing needs your own Dokobit account. Oktul does not sell signing; your agreement with Dokobit sets volume and price.
  • Cloud only. No Data Center or Server version.

Common questions

Is a SignPlus signature legally binding?
A signature made with an eID that carries a qualified certificate is a qualified electronic signature (QES). Under Article 25(2) of eIDAS it has the legal effect of a handwritten signature in every EU member state. A signing in Test mode has no legal effect.
Which eIDs can sign with SignPlus?
Smart-ID, Mobile-ID, an ID card and the other methods on Dokobit's list of supported eIDs. The signer uses their own eID on Dokobit's page.
What data leaves Atlassian when a page is signed?
Dokobit receives the PDF and each signer's name and email address. Nothing else leaves Atlassian, and no Oktul server is involved. See privacy and data handling.
What happens when someone edits a signed page?
The byline says the page was modified after signing and links to Confluence's comparison of the signed and current versions. The REST API and an optional webhook report it too.
Do I need my own Dokobit account?
For real signing, yes. A new installation starts in Dokobit's test environment, which Oktul provides, where documents come back watermarked.
Does SignPlus work on Confluence Data Center?
No. SignPlus runs on Atlassian Forge, in Confluence Cloud only.

Where to start

If you are Start with
The administrator installing it Install the app, then configure SignPlus
Sending a page for signing Sign a page
Asked to sign What a signer sees
Checking a signed page After signing
Making the document look like your company’s Style the exported document
Building a flow or an integration Automation and webhooks and the REST API
Reviewing it for security or procurement Privacy and data handling

A problem or a question? Write to support@oktul.com or open a request in the Help Center (opens in a new tab). Both open a request with a reference and an SLA.