Every refusal in SignPlus says what was refused and why. Refusals are in English whatever the reader’s Confluence language.

Starting a signing

You see	What to do
SignPlus is not set up for this space yet	A space or Confluence administrator has to open the SignPlus settings once. See configure SignPlus
Starting a signing needs permission to edit this page, or You need permission to edit this page to start a signing on it	Ask for edit access, or ask someone who has it to start the signing
SignPlus is not allowed to edit this page, so it could not attach the signed document once everyone has signed	The page’s restrictions leave SignPlus out, and nothing was sent. Let SignPlus edit the page, or ask whoever restricted it or a space administrator, then start the signing again
This page already has an attachment with that name. Choose another name.	Change Document name. Confluence refuses two attachments with the same name
This space requires a message to signers, or a signing deadline	Fill in the field under Show additional settings
This space does not allow…	The space’s settings rule that option out. Remove it, or ask a space administrator
The signing deadline must be in the future	Pick a later due date or time. The time is read in the zone the information icon names
Every signing method is turned off in this space	An administrator has disabled every method under Disabled signing methods. At least one has to stay on
Not sent for signing, with a reason	Nothing was sent to anyone. The reason says what to change; then start it again
Dokobit could not be reached, so nothing was sent for signing	A network problem between Atlassian and Dokobit. Try again in a few minutes
Dokobit did not accept the token this site signs with, so nothing was sent for signing	A Confluence administrator replaces the token under Dokobit token in SignPlus global configuration
The Dokobit token is not configured	A Confluence administrator enters it under Dokobit token, or chooses Test
Test signing is not configured on this SignPlus release	Choose Your own token in SignPlus global configuration to sign with your own Dokobit account
Live signing is not configured on this SignPlus release	Nothing on your site can fix it. Write to support@oktul.com

While a signing runs

You see	What to do
The signed document never appears on the page	SignPlus checks with Dokobit itself every hour, up to 1,000 pending signings a run, so a lost notice arrives later. If a day passes, open a support request naming the page and the document
A signer says they got no email	Check the address in View signing details. Dokobit’s email may be in their spam folder
A group member was not invited	Confluence gives out no email address for that person. View signing details shows how many members of each group were invited
Page modified during signing	Someone edited the page after it was sent. Cancel the signing and start a new one if the change matters

Signed pages

You see	What it means
Page signed but modified	The page was edited after everybody signed. compare shows what changed. The signed file still holds what was signed
The page cannot be edited after signing	The edit lock stays after a completed signing, on purpose. A space administrator removes it under the page’s restrictions
There is no Delete in the signing details	Deleting a finished signing is a Confluence administrator’s by default. See deleting signings
The signed document has a watermark	The site was in Test signing mode. That document has no legal effect: sign it again once the mode is changed

Exports

You see	What to do
PDF not generated	Try again. If it fails again, open a support request: the reason is in SignPlus’s logs, which Oktul can read without seeing your page
PDF not generated, with Confluence did not accept it as an attachment	Trying again will not change it. Write to support@oktul.com with the time of the export
An image is missing and its description is printed instead	SignPlus could not draw it, or ran out of time fetching images. See what the document contains
A Jira table shows a notice, or work item keys rather than cards	SignPlus is not connected to Jira. See connecting Jira

Administrators

You see	What to do
Could not save the token, with Dokobit did not accept this token, so it was not saved	Copy the live token from your Dokobit account again. A Dokobit test token is refused
Dokobit token saved, with Dokobit could not be reached to check it	The token is stored without a check. The first signing shows whether it works
Could not check the token	SignPlus could not read whether a token is stored. Refresh the page and open Dokobit token again
SignPlus needs an active licence	The subscription has lapsed. Signings already out still complete. See licensing
A webhook never fires	The address was not approved in Atlassian’s dialog, or the receiving rule is not published. See webhooks

What to put in a support request

The page, the document name and what you saw. From the REST API, the signing’s reference identifies it on its own and reveals nothing about its content. Logs, in the global settings, shows what SignPlus did for every API request, webhook and automation action on your site.

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