No searching for the right file.
Start from the relevant record. A guided process brings together the document, recipients and template.
Module · AgenticUltimateFrom quotation
From quotation
to signature.
Directly in your CRM.
Digital signatures in SuiteCRM 8: select documents, manage recipients, collect signatures — status and evidence stay on the record.
Product preview In development. This page describes the intended scope; details may change before release.
AgenticUltimate SignWorkflow preview
QUOTATION · DRAFTPDF
Good collaboration
starts with a yes.
Your signature field
✓ Review the document✓ Confirm explicitly
Stored on the CRM recordFinal PDF · Status · Evidence
✓ Native signing by default✓ Optional external providers✓ Sign without a CRM account✓ Traceable history
Fewer manual steps. More visibility.The agreement belongs
The agreement belongs
in your CRM process.
Quotations and contracts originate in the CRM. Signing should continue there, with a visible status and the right documents attached to the right record.
Know what is still outstanding.
Delivery, outstanding signatures, expiry and completion remain visible. Reminders support follow-up.
Keep the evidence with the transaction.
The final document and its history are returned to the record so your team can continue working with the result.
Your process. Your signing method.Start with native signing.
Start with native signing.
Connect providers when needed.
One CRM workflow with a native default option and optional provider integrations.
Native signature capture
Draw a signature or type a name, then explicitly confirm. The native workflow is designed to work without an external signature-provider account.
DocuSign
Use an existing provider account. Prepare the document and recipients in the CRM; return the status and result to the transaction.
Adobe Acrobat Sign
An additional option for companies already using Adobe signing services. The integration is intended to fit the same guided CRM process.
Native capture is not intended to provide a qualified electronic signature. The required signature level, identity checks and suitability for your documents must be established before use. External-provider methods and costs depend on the relevant contract.
Four steps instead of a wall of formsFrom the CRM record
From the CRM record
to a document ready to send.
The wizard shows the task that matters now. Additional settings appear where they are needed.
Select a document
Upload a PDF or use an approved CRM template. Unsupported or encrypted files are rejected before sending with a clear explanation.
Choose recipients
Select CRM contacts and verify their addresses. Define who signs in parallel or in sequence and who may receive a copy.
Place fields
Assign signatures, initials, dates, text fields and checkboxes to the appropriate recipients. Templates reduce repeated work; required fields are checked.
Review and send
Check the document, participants, expiry date and reminders. Sending creates a fixed document version. Subsequent changes require a new transaction.
Simple for your customers tooOpen. Review.
Open. Review.
Sign deliberately.
External recipients do not need a SuiteCRM account. The signing interface is designed for smartphones and desktops.
Personal access
An invitation leads to the relevant document. An additional access code may be configured for the process.
Take time to review
Recipients see the full document and the fields they need to complete. The next step remains clear.
Confirm explicitly
Draw or type, review the inputs and actively confirm signing. Simply opening a link does not sign anything.
Receive a copy
After completion, authorised participants can access the final version. The CRM transaction shows the updated status.
Planned protection against automated email link scanners: a simple link request should neither consume the invitation nor count as a deliberate opening by the recipient.
Traceability built inMore than a signature.
More than a signature.
A documented transaction.
Document versions and events are considered together. Integrity checks help detect subsequent file changes.
A fixed sending version
An unchanged source version and SHA-256 checksums provide the foundation for later reconciliation.
One shared timeline
Relevant actions receive UTC timestamps. Detailed evidence is accessible only to appropriately authorised roles.
PDF and evidence package
The final PDF, event report and file-checksum manifest are associated with the transaction and prepared for export.
Back where your team worksSigning status becomes
Signing status becomes
part of everyday CRM work.
Employees start and track transactions on the associated record. A central overview complements daily work.
CRM record→Signing transaction→Final PDF & evidence
Status instead of follow-up questions
Draft, sent, in progress, completed, declined and expired states are clearly distinguished.
Protect completed transactions
No further signing is intended after completion, rejection or expiry. Access to copies follows separate permission and retention rules.
Define follow-up actions deliberately
A signed document does not automatically mark a deal as won. Business follow-up actions are explicitly configured.
Plan costs deliberatelyA native route.
A native route.
Options for your infrastructure.
Native signing reduces dependence on external signing services. A meaningful comparison still includes all costs.
No separate signature-provider contract
No separate signing service is intended for the native workflow. The specific AgenticUltimate Sign licence scope will be defined at release.
Use existing contracts
DocuSign and Adobe Acrobat Sign remain optional additions. Their licence and usage costs must be considered separately.
Operations count too
Include hosting, email delivery, storage, rollout and support in your plan. We discuss your volume and workflow during the demo.
Good to know
Questions about AgenticUltimate Sign.
Key answers about the planned workflow and implementation.
Is AgenticUltimate Sign available now?
The add-on is in development. This product preview describes the intended scope. A demo clarifies the current status and which features can already be shown.
What signature level does native capture provide?
A simple electronic signature with a documented process is intended. This does not automatically constitute a qualified electronic signature. Requirements for your specific documents must be established before use.
Can we continue using DocuSign or Adobe Acrobat Sign?
Optional integrations are planned. Supported methods and account requirements will be defined for each integration; an existing contract does not replace that review.
Do customers need CRM access?
No. A separate signing interface accessed through a personal invitation is intended. CRM-data access and the external signing view remain separate.
What happens if someone does not sign?
Expiry dates and reminders are set before sending. Open, declined and expired transactions remain distinguishable in the CRM and can be followed up individually.
Can a sent document still be changed?
The sent version remains fixed. Content changes require a new document version and signing transaction; the previous history remains traceable.
Related modules
Works well together.
Help & documentation
Signature documentation
Preparation, sending and status — guides in the QOON Knowledge Base.
See signing
in your SuiteCRM?
In about 20 minutes we discuss your documents and show preparation, send-out and status tracking in SuiteCRM 8.
Request an e-signature demo ↗No obligation · Tailored to your processes · Includes a template review