Oktul home
  • English
  • Estonian

The documentation is in English only.

Contact us

Install the app

Installing SignPlus into Confluence Cloud, choosing the signing mode, connecting Jira if you want it, and what happens when the licence lapses.

Installing SignPlus for Confluence, no sound.
What the video shows
  1. The title: Install SignPlus.
  2. On the SignPlus for Confluence listing on the Atlassian Marketplace, select Try it free.
  3. Choose your site and select Install app. The trial installs on Confluence.
  4. In Confluence administration, open SignPlus global configuration, then the Dokobit token tab.
  5. Choose Your own token as the signing mode, select Set token, enter the token and select Save token. A flag says new signings will use it.
  6. Oktul, Atlassian Marketplace Partner.

Install SignPlus from the Atlassian Marketplace into Confluence Cloud, then choose the signing mode. It is an Atlassian Forge app, so Atlassian hosts and runs it and nothing is deployed to your infrastructure. There is no Data Center or Server version, and none is planned.

What leaves Atlassian:

  • The page and each signer’s name and email address, to Dokobit, to create the signature.
  • A notification, to each webhook address your administrator approves.
  • A request for each picture from Atlassian’s own page templates, to Atlassian’s image library at dam-cdn.atl.orangelogic.com, hosted by Orange Logic. It receives nothing of the page.

Requirements

  • Confluence Cloud
  • A site administrator to install it and choose the signing mode
  • For real signatures: your own Dokobit account and its API token
  • Jira Cloud on the same site, optional: see connecting Jira

Install it

  1. Open the SignPlus listing on the Atlassian Marketplace

    Or, in Confluence, Apps, then Explore more apps, and search for SignPlus.

  2. Select Try it free and choose your site

    A site or Confluence administrator installs it; anyone else can request it.

  3. Approve the permissions

    Atlassian shows what SignPlus may read and where it may send data. Each is explained in privacy and data handling.

  4. Choose the signing mode

    Settings, SignPlus global configuration, Dokobit token. Until you do, every signing is a test.

It can take a minute to appear. Each permission is explained in privacy and data handling.

Confirm it worked

Where What
Under the title of every page Sign this page, with a signature icon. Selecting it opens the signing panel
Confluence Settings, under Apps SignPlus global configuration, for Confluence administrators
Space settings, under Integrations SignPlus space configuration, for space administrators
Confluence’s Apps menu SignPlus: your signings, every signing you have started
A new installation signs in test mode

Documents come back watermarked, with no legal effect, until you choose the signing mode.

Connecting Jira

Atlassian does not connect SignPlus to Jira by default. Connecting it adds:

  • Automation actions in Jira. See automation and webhooks.

  • Assets tables in the document. Without Jira, a notice stands in their place.

  • Work Item Selector cards in work items tables. Without Jira, the keys print.

  • Who connects it: an organisation administrator, in Atlassian Administration. Until then the SignPlus settings screen says so and links there.

  • No Jira on the site: dismiss the notice with This site does not use Jira. Everything else works the same.

  • Adding Jira later needs no reinstall.

Language

SignPlus follows each person’s Atlassian profile language: English and Estonian on every screen, English for any other language. Always in English:

  • the byline’s signing state and its tooltip, once a page has a signing;
  • a refusal, such as The signing deadline must be in the future;
  • the few words SignPlus prints in a document: Attachment:, Not available and +N more.

The rest of a signed document’s wording, and Dokobit’s invitation email, follows the site and Dokobit rather than the reader.

Licensing, and what happens when it lapses

Paid per installation through the Marketplace. A free trial counts.

Without an active subscription:

  • No new signings, and the byline stops showing signing state.
  • No cancelling or deleting signings.
  • Settings cannot be read or changed.
  • The REST API answers 402; automation actions refuse.
  • The edited-page webhook is not sent.
What a lapsed licence leaves alone
  • A signing already out still completes, with its attachment and completion webhook.
  • Nothing is deleted. Everything works again once the subscription is active.
  • A locked page stays locked. A space administrator can remove the restriction.

Removing the app

What uninstalling leaves on your pages
  • Removed: signing records, settings, your Dokobit token and the activity log. No page shows its signing state any more.
  • Kept: signed documents, as page attachments.
  • Still locked: pages SignPlus locked. A space administrator removes the restriction.
  • At Dokobit: its copy stays under Dokobit’s retention. Cancel or delete signings in SignPlus first to remove them for every signer. See privacy and data handling.

Common questions

Does SignPlus need Jira?
No. Jira on the same site is optional, and adds the automation actions, Jira Assets tables and Work Item Selector cards in the document.
What happens when the SignPlus licence lapses?
No new signing can start and the settings close, but a signing already out still completes and nothing is deleted.
What does uninstalling remove?
SignPlus's records, settings, Dokobit token and activity log. Signed documents stay on their pages, and a page SignPlus locked stays locked until a space administrator removes the restriction.
Which languages does SignPlus support?
English and Estonian, following each person's Atlassian profile language. Any other language shows English.

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