Electronic document signing in GLPI with DocuSeal

Equipment handover forms, quote approvals, contract closures: documents born in the ticket that need a signature. The Digital Signature module connects GLPI to DocuSeal without taking anyone out of the workflow.

The document is born in the ticket — the signature should not leave it. Laptop handover forms, quote approvals, internal policy acknowledgements: GLPI already holds the whole context, yet collecting the signature ends up happening over e-mail, outside the ticket trail.

The problem

The typical cycle goes like this: the technician generates the document, downloads the file, attaches it to an e-mail, sends it to the requester, waits, follows up, receives the signed PDF back and — if they remember — attaches it to the ticket.

Every manual step is a chance to lose something. The signed document sits in someone's inbox instead of the system; nobody knows who has already signed without opening the e-mail thread; and the audit, months later, cannot find the evidence where it should be.

How Digital Signature works

The module connects GLPI to DocuSeal, an open-source electronic signature platform you can host in your own environment — a relevant point for anyone restricted from sending documents to a third-party service.

  • Documents straight from GLPI — generated from tickets, contracts and assets, carrying the record's data.
  • Multiple signers — requester, manager and technical owner on the same document.
  • Real-time status through webhook — GLPI is notified as each person signs, with nobody polling for updates.
  • Evidence in the right place — the signed document comes back attached to the record that produced it.

How to enable it

  1. Have a DocuSeal instance available (self-hosted or cloud).
  2. Install NexTool on your GLPI 11 and enable the Digital Signature module.
  3. Enter your DocuSeal URL and API key in the module settings.
  4. Configure the return webhook so GLPI receives status updates.
  5. Generate the document from the ticket, contract or asset and send it for signature.

Who it is for

IT teams that hand out equipment and need a signed acknowledgement; operations that depend on formal approval before doing the work; and companies under audit that must prove, with a trail, that the document was accepted by the right person.

If your case requires notarised or ICP-Brasil certificate-level legal validity, review the specific legal requirements first — the module delivers the collection workflow and the traceability, while the level of validity depends on your DocuSeal setup and on the nature of the document.

Compatibility

  • GLPI: 11.0+
  • Plan: Licensed
  • Plugin: NexTool 6.x+

Next step

Digital Signature is part of NexTool, an ecosystem of modules that extends GLPI without code customisation. Visit the module page or book a call to see it running in your environment.


Reviewed by the NexTool Solutions team.

Frequently Asked Questions

No. The module connects GLPI to either a self-hosted or cloud DocuSeal instance. You only need to configure its URL, API key and return webhook in the Digital Signature module.

Besides tickets, the module can link documents to contracts, computers, monitors, phones, printers, peripherals, network equipment and knowledge base articles. A standalone signature can also be created without a prior link.

DocuSeal sends webhook events when a form or submission is completed. The module updates the status, keeps the document linked to its source record and adds automatic followups to tickets; the status can also be refreshed manually.

Yes. Templates may define several signer roles, and the module provides tags for ticket, requester, technician, entity, location and asset data. Individual fields can also be made read-only for the signer.

The module provides the sending, tracking and evidence-linking workflow inside GLPI. Legal validity depends on the DocuSeal setup, the identification method and the requirements that apply to the document; the module itself is not an ICP-Brasil certificate.

Need help?