Versioned terms, contracts and SOWs your customers actually sign — with evidence you can produce years later
Made and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.
PD Agreements lets a hosting company put its Terms of Service, Acceptable Use Policy, Data Processing Agreement or any statement of work in front of the right customers, have them sign it, and keep proof of exactly what each customer agreed to. You write the agreement once in Blesta and publish it as a numbered version. Customers sign inside their own client area, and every signature is stored with the version, a content fingerprint, the date and time, and the method used.
It is built for hosts and agencies who need more than a tick box. When a chargeback, an abuse complaint or a data-protection question arrives years later, you can produce the signed record and an evidence PDF instead of an argument.
Proof, not a tick box. Publishing freezes the text as a version with its own SHA-256 fingerprint, publisher, time and change note. Earlier versions stay exactly as published, so a customer who signed version 1 stays attached to what version 1 said.
Ask only the customers who need to sign. Aim an agreement at everyone, or at chosen packages, package groups, client groups or individual clients. A support addendum can go only to customers who ordered the support add-on package. Choose "any of these" or "all of these", and leave out clients who have a package or group you name. An exclusion always wins.
Changed terms, asked again. Publish a new version and, if you tick "everyone who signed an earlier version must accept this one", earlier signers are asked again. Customers already on the current version are never asked twice, and a customer is only shown agreements that apply to them.
No chasing by hand. An Awaiting signature list shows every customer who owes a signature and exactly what is missing. Email one customer, or everyone, their signing link in one click, or switch on automatic reminders, which email everyone outstanding at most every N days through a company email you can edit and translate.
Customers never leave their account. They review, sign and download their own signed copies inside the Blesta client area. There are no attachments to send and no chasing over email.
Evidence that stays yours. PD Agreements makes no outbound calls. The evidence PDF is generated on your own server, and your signatures live in your own Blesta database.
PD Agreements is one paid module with everything included. There are no add-on tiers. It installs into PD Modules in one click, updates itself, and adds its own tables without modifying Blesta files.
If your subscription ever lapses, the signatures you have already collected stay readable and downloadable. Managing agreements locks once the licence has expired, and asking customers to sign stops only if it is later suspended.
It replaces what that tick box is for. Blesta's order form links to a terms URL and records nothing; PD Agreements shows the document itself, records who accepted which version, and gives you a downloadable evidence record. You can leave Blesta's own terms setting in place or clear it — they do not conflict.
In most jurisdictions an electronic signature is capable of being binding, and what decides a dispute is the evidence that a specific person accepted a specific text at a specific time — which is exactly what is stored: the version, a fingerprint of the wording, the date and time, the IP address and browser, and the signature itself. Whether a particular method suits your contract type and country is a question for your legal adviser.
Publishing creates a new version; existing signatures stay attached to the version they signed. Tick "everyone who signed an earlier version must accept this one" and customers on older versions are asked again on their next visit to the client area. If you do not tick it, they are left alone and only new customers see the new version.
No, deliberately — the value of the record is that the text cannot be changed after the fact. Edit and publish again: you get a new version, and version history shows what changed and when.
Only if you choose that. By default an unsigned customer can still pay invoices and open tickets, so you never block a customer from paying you. You can tighten it to "nothing until signed" or loosen it to "everything except placing new orders". Logging out and password reset are always available.
No. PD Agreements makes no outbound calls. Agreements, signatures and evidence records live in your own Blesta database, and the evidence PDF is generated on your server using the PDF engine already bundled with Blesta.
Yes — by default they see their signed agreements in their client area and can download the same evidence PDF you can. You can turn that off in Settings.
You can revoke one, which records the reason and the time and asks the customer to sign again. You cannot delete it, because a record you can quietly remove is not evidence. Deleting an agreement removes it from your list and stops anyone being asked, but every signature keeps its evidence record, with the exact text that was signed.
Yes. The signing page is a standalone screen with its own styles, so it looks the same whatever your client-area theme, and the customer's agreements page sits inside your Blesta client area like any other page. You can override both, and your overrides survive updates.
Your customers are never locked out — the signing surfaces keep working and everything you have already collected stays readable and downloadable. Authoring new agreements and chasing signatures is what pauses until the licence is active again.
Nothing beyond the module subscription. PD Agreements runs entirely inside your Blesta and does not connect to a paid third-party service, so there is no usage bill, no per-message or per-GB charge, and no metered anything.
Yes. The agreement scrolls from the keyboard, the signature pad is labelled for screen readers, and a customer who cannot draw a signature can choose to type their name instead. The record shows the method actually used.
Yes. Target products, product groups, add-on packages, client groups or individual clients, and choose whether a customer is asked when they match any of your choices or only when they match all of them. You can also ask a single client to sign any published agreement.
Yes. Download the signatures or the audit log as a CSV for any period. A drawn signature appears as yes or no rather than the image, and the IP address and browser columns are left out when you have turned that recording off.
Yes. In the agreement, under "Except these customers", pick the add-ons, products, product groups or client groups to leave out. A customer who has any of them is not asked, whatever else you targeted, including an agreement for everyone. It is checked every time, so when a customer buys the add-on they stop being asked with nothing for you to remove, and if they lose it they are asked again. Signatures already collected are kept.
Yes. Open the agreement and press Remove beside the client in the list of clients asked by name, or press Remove on their page in your admin area. They are no longer asked because they were named, and anything they already signed is kept. If your targeting still reaches them they are still asked, and the screen tells you so.
Rich client, service & domain notes with reminders
Featured
Verify callers with a per-client Support PIN
Stop fake signups & order fraud before they provision
Featured
Automatic discounts, product bundles and free trials for Blesta — rule-based, no promo code needed
Terms and Conditions · Privacy Policy
PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.
