HELP CENTER

Digital signature

Upload a PDF, define signing areas and collect signatures with auditable evidence.

Electronic PDF signature

Digital signature

Description

Service for preparing a PDF, placing fields, and requesting signatures from one or more people while retaining process status and evidence.

Use cases

  • Request acceptance and signature of agreements or authorizations.
  • Collect signatures in a defined order.
  • Place signature, date, and data fields on specific pages.
  • Track progress and obtain the completed PDF.

How to create the service

Open Cloud > New item and select Digital signature. Upload or choose the PDF, enter a name and folder, and create the request. Add signers and place fields before sending.

Interface and controls

The preparation view shows PDF pages, thumbnails, a signer list, and a field palette. Fields can be dragged, resized, and assigned. Tracking actions show status, deliveries, and evidence. Header actions save, preview, send, and download once complete.

Full workflow

  1. Select a final PDF and review every page.
  2. Add signers, contact data, and order where required.
  3. Place and assign all mandatory fields.
  4. Configure available access, messages, and expiry.
  5. Preview as a signer and send requests.
  6. Monitor status and resend only when necessary.
  7. Download the final PDF and available evidence.

Supported files or data

The source must be PDF. The service stores signers, fields, positions, states, and audit events. Available fields can include signature, initials, name, text, date, checkbox, or configured alternatives. Encrypted, damaged, or non-renderable PDFs may be rejected.

Configuration options

Options include signer order and details, field assignment, page, position, size, required state, available access or authentication methods, subject, message, reminder and expiry where enabled, visibility, and Cloud settings.

Output and export formats

The main result is a signed PDF with status and audit evidence. Signature does not convert it to other formats. Use File Transformer before starting or, where policy permits, after completion.

Saving, downloading and sharing

Saving retains preparation without sending. Sending creates signer access. Once completed, download the final PDF and evidence from tracking. Users grants administrative access and does not replace individual signature links.

Limits and technical requirements

Requires PDF rendering and configured email and queues for communications. Size, signer, credit, and storage limits apply. Legal value depends on identification, integrity, evidence, and jurisdiction; the service alone does not guarantee a particular legal level.

Common errors

  • Pages cannot be rendered: check PDF integrity, encryption, Poppler, and system paths.
  • The request cannot be sent: a signer, contact detail, or required field is missing.
  • A link does not work: check expiry, status, completion, or revocation.
  • Email is not delivered: check address, provider, queue, and delivery logs.

Privacy and data processing

Documents, signatures, identifiers, and events may contain sensitive personal data. Define legal basis, retention, and access, use HTTPS, and limit administrators. Do not publish signature links or download evidence to uncontrolled devices.

Frequently asked questions

  • Is it always a qualified electronic signature? No; this depends on the implemented method, provider, and applicable law.
  • Can the PDF change after sending? It should not; changes require a new request.
  • Does Users allow someone to sign? Not necessarily; it grants service access, while each signer uses an assigned flow.

Related services

PDF document with metadata for archiving, File Transformer for preparation or conversion, and Document for authoring the source.