# Install the app

[Video: Installing SignPlus for Confluence, in 25 seconds, no sound](/images/videos/signplus/install-light.f4390091.mp4)

What the video shows:

1. Open the SignPlus for Confluence listing on the Atlassian Marketplace and select Try it free.
2. Choose your site and select Install app. The dialog lists Confluence as the Atlassian app the trial installs on.
3. In Confluence administration, open SignPlus global configuration under Apps.
4. Open the Dokobit token tab. Test is the active signing mode.
5. Select Your own token, then Set token, enter the token and select Save token. A flag says new signings will use it.

SignPlus is an Atlassian Forge application for Confluence Cloud. Nothing is deployed to your own
infrastructure: Atlassian hosts and runs it, and the one party outside Atlassian that receives
anything is Dokobit, which is what makes the signature qualified.

**Confluence Cloud only.** There is no Data Center or Server version, and none is planned.

## Requirements

- Confluence Cloud
- A site administrator to install it and choose the signing mode
- For real signatures: a Dokobit account and its API token, unless your site uses **Managed by
  Oktul**
- Jira Cloud on the same site is **optional**. It is needed for three things, all described under
  [connecting Jira](#connecting-jira)

## Install it

<Steps
  items={[
    {
      title: 'Open the SignPlus listing on the Atlassian Marketplace',
      body: 'Or, in Confluence, Apps, then Explore more apps, and search for SignPlus.',
    },
    {
      title: 'Select Try it free and choose your site',
      body: 'A site or Confluence administrator installs it. Anyone else can request it, and an administrator approves the request.',
    },
    {
      title: 'Approve the permissions',
      body: 'Atlassian shows what SignPlus may read and where it may send data. Each is explained in privacy and data handling.',
    },
    {
      title: 'Choose the signing mode',
      body: 'Settings, SignPlus global configuration, Dokobit token. Until you do, every signing is a test.',
    },
  ]}
/>

The permissions it asks for, and why each is needed, are listed in
[privacy and data handling](../privacy/#6-permissions). A Forge application can take up to a
minute to become available across a site after it is installed.

<Aside type="note" title="No Marketplace listing yet">
SignPlus is in beta and is not on the Marketplace yet. [Ask to join the pilot](/contact/) if you
need it before the listing appears.
</Aside>

## 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 |

<Aside type="caution" title="A new installation signs in test mode">
Until a site administrator chooses otherwise, every signing goes to Dokobit's test environment.
Documents come back watermarked and have no legal effect. Choose the signing mode before anyone
signs anything: see [signing mode](../configure/#signing-mode).
</Aside>

## Connecting Jira

SignPlus installs into Confluence, and Atlassian does not connect it to Jira by default, even on a
site that has Jira. Connecting it adds:

- **The automation actions.** *Start a SignPlus signing* and *Export a page as PDF* appear in Jira
  automation. See [automation and webhooks](../automation/).
- **Jira Assets tables in the document.** A page's Assets table stores only its query, so without
  Jira the exported document carries a notice where the table would be.
- **Work Item Selector fields in a work items table.** A table that shows an Oktul Work Item
  Selector field prints each selected work item as a card. Without Jira it prints the keys.

An organisation administrator connects Jira in Atlassian Administration. Until then, the top of
the SignPlus settings screen says SignPlus is not connected to Jira and links there. A site that
does not use Jira can dismiss the notice with **This site does not use Jira**. Everything else
works the same on a Confluence-only site, and adding Jira later needs no reinstall.

## Language

SignPlus follows each person's Atlassian profile language. **English and Estonian** are
included, on every screen. Any other language shows English.

A signed document's own wording, such as the placeholders on its first page and Dokobit's
invitation email, follows the site and Dokobit rather than the reader.

## Licensing, and what happens when it lapses

Paid and licensed per installation through the Atlassian Marketplace. A Marketplace free trial
counts as a licence.

With no active subscription:

- no new signing can be started from a page, and the byline stops reporting the page's signing
  state;
- the site and space settings can neither be read nor changed, and say why;
- the REST API answers `402`, and the automation actions refuse to run;
- the webhook for an edited signed page is not sent.

<Aside type="note" title="What a lapsed licence leaves alone">
**A signing already out for signature still completes.** When the last signer signs, the signed
document is attached to the page as usual, and the completion webhook is sent if you configured
one. Refusing it would lose a document real people signed.

**Nothing is deleted.** Signed documents stay on their pages, the signing records stay in
storage, and everything works again the moment the subscription is active.
</Aside>

## Removing the app

<Aside type="caution" title="What uninstalling leaves on your pages">
Uninstalling removes SignPlus's Forge storage: the signing records, the settings, a Dokobit token
you entered and the site's activity log. **The byline then has nothing to compare against**, so
no page shows its signing state any more.

**Signed documents stay**, because they are ordinary page attachments.

**A page SignPlus locked stays locked.** The edit lock is a Confluence page restriction, and it
outlives a completed signing on purpose. A space administrator removes it from the page's
restrictions.

**Dokobit keeps its copy** of each document under Dokobit's own retention. Cancelling a signing in
SignPlus before you uninstall removes the document from Dokobit for every signer. See
[privacy and data handling](../privacy/#7-retention).
</Aside>

## Related

- [Configure SignPlus](../configure/)
- [Sign a page](../sign-a-page/)
- [Automation and webhooks](../automation/)
- [Privacy and data handling](../privacy/)

---

A problem or a question? Write to [support@oktul.com](mailto:support@oktul.com) or open a request in the [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals). Both reach the same service desk, so either way the request gets a reference and an SLA measuring the response.