The app can only be configured by Nextcloud administrators. To do so, go to Administration Settings → signotec signoSign Settings.
1. Connection data
In the first section, the login credentials for the signoSign/Universal instance are entered.
|
Field |
Description |
|---|---|
|
URL |
Base URL of your signoSign/Universal instance. Default: |
|
Username |
Username for the API connection. |
|
Password |
Password for the API connection. This field can be left blank when editing again to keep the existing password. |
Click Save. The app will automatically check the connection.
Connection status
After saving, the connection status is displayed:
-
Connection successful (green) – The login credentials are correct and the server is accessible. The remaining configuration sections will be displayed.
-
Error message (red) – The connection could not be established. Possible causes:
|
Error message |
Cause |
|---|---|
|
Invalid credentials ... |
Your username or password is incorrect. |
|
Invalid URL ... |
The URL you entered does not lead to a signoSign/Universal instance. |
|
Could not connect ... |
Server not available (network issue, firewall). |
|
SSL certificate error ... |
The server's SSL certificate is not accepted. |
2. Webhook-URLs
To ensure that Nextcloud is automatically notified once a signing process is complete, two webhook URLs must be entered in signoSign/Universal.
Important: The Nextcloud server must be accessible over the network from the signoSign/Universal server for webhooks to work. Make sure that no firewall or network configuration is blocking incoming traffic from signoSign/Universal to the Nextcloud webhook URLs.
The app displays the expected URLs and their current status:
|
Webhook |
Purpose |
|---|---|
|
Webhook URL for signature updates |
Called when a document has been signed. |
|
Webhook URL for rejected sharing cases |
Called when a remote signature request has been rejected. |
A green checkmark indicates that the URL is already correctly configured in signoSign/Universal. A gray 'X' means that the URL has not yet been configured or is configured differently.
Set webhooks automatically: Click “Set Webhook URLs in signoSign/Universal” to automatically enter the webhook URLs in your signoSign account. A confirmation dialog will appear, as this will overwrite any existing webhook configurations. The button is disabled if both webhooks are already set correctly.
3. SMS-Configuration
This section shows whether an SMS key has been saved in signoSign/Universal:
-
Green checkmark – SMS messaging is enabled. For remote signatures, the "TAN via SMS" authentication method is available.
-
Gray 'X' – No SMS key has been configured. The "TAN via SMS" option is not displayed in the user interface.
You can enable the SMS feature directly in the user settings of your signoSign/Universal account, not in the Nextcloud app.
4. Signature fields
Signature fields are automatically inserted into documents as soon as a signing process is initiated. The app searches for configured keywords in the PDF text and places the signature field at the corresponding location.
In signoSign/Universal, you can also use digital signature fields that already exist in the document.
Add signature field
Click “Add Signature Field” to create a new row in the table.
|
Parameters |
Description |
Default |
|---|---|---|
|
Signer |
Name or identifier of the signatory (must be unique) |
– |
|
Search text |
Keyword in the PDF where the field is positioned (e.g., |
– |
|
Width |
Width of the signature field in pixels (must be greater than 0) |
180 |
|
Height |
Height of the signature field in pixels (must be greater than 0) |
60 |
|
Offset X |
Horizontal offset of the search text in pixels (can be negative) |
0 |
|
Offset Y |
Vertical offset of the search text in pixels (can be negative) |
0 |
|
Required |
The signature field is required For remote signatures, the recipient must sign the required fields. |
No |
Actions per field
|
Button |
Function |
|---|---|
|
Duplicate |
Creates a copy of the field on the next line |
|
Remove |
Removes the field from the list |
Finally, click Save to apply the changes to all fields.
5. Processing in Nextcloud
In certain situations, the app can automatically add comments and tags to files. All fields in this section are optional.
Comment
A comment can be added for each workflow status. Placeholders are automatically replaced with current values.
|
Setting |
Time |
Available placeholders |
|---|---|---|
|
Comment when sending a request for signing |
When a remote signature request is sent |
|
|
Comment after signing |
When a document has been successfully signed |
|
|
Comment when rejected |
If a remote signature request has been rejected |
|
Placeholder reference:
|
Placeholder |
Description |
|---|---|
|
|
Username of the Nextcloud user who initiated the process |
|
|
Recipient's email address (for remote signatures only) |
|
|
Selected authentication method (for remote signatures only) |
|
|
Reason for rejection (only for rejected requests) |
Sample comments:
Sent to @mailto@ via @authtype@
Signed by @mailto@, Sent by @userid@
Rejected by @mailto@: @reason@
Comments are prefixed with [signotec signoSign] and displayed in the Nextcloud file overview.
Tags
A Nextcloud tag can be defined for each workflow status. Tags are mutually exclusive—when the status changes, the previous tag is automatically removed.
|
Setting |
Time |
|---|---|
|
Tag when sending a request for signing |
When a remote signature request is sent |
|
Tag after signing |
When a document has been successfully signed |
|
Tag when rejected |
If a remote signature request has been rejected |
Tags are automatically created in Nextcloud if they do not already exist.
With local signing, no tags are set when the document is opened; this happens only after the document has been saved.
6. Reset settings
Clicking the "Delete all Settings" button will permanently delete all saved configuration data. A confirmation dialog will appear before the action is carried out.