Helpful answers before you send your first request.

Yes. You can preview the signing experience for each recipient on desktop or mobile, including the documents they can see and the order of their required fields.

LulaSign checks the request before it is sent. If people, delivery details, document access, required fields or security information are missing, it explains what needs attention.

Yes. Put several PDFs into one ordered pack and decide, document by document, which recipient may view or complete it.

Yes. Invite everyone together for parallel signing, or set a sequence so the next person receives access only when the earlier step is complete.

PDFs, up to 20 MB each. Save a Word or other document as a PDF first. One request can hold several PDFs, up to your plan's limit, and each person sees only the ones assigned to them.

Yes. Each person on a request is a signer, witness, approver or viewer, and for every PDF you choose whether they must sign, only view or are not involved.

Yes. Choose New, then Sign it myself, and add your signature, initials, the date, text, tick boxes or a stamp. Nobody is emailed and it does not use a signing request from your plan. The signed PDF and its certificate wait under Self-signed for you to download.

On the paid plans you can keep stamps beside your signature: upload a scan of yours, start from a library of about seventy, or design one in the Stamp Studio. An organisation seal belongs to the workspace, such as a company seal, and only the members who hold it can apply it. Every stamp applied gets a serial that anyone can check on the verify page. A stamp records who applied it, with which words and when; LulaSign does not check the authority of the person applying it.

Yes. In Signing & access, tick the people who must stamp and choose which stamp: one of theirs, a library stamp or one of your organisation's seals. A recipient does not need a LulaSign account to stamp a document they were sent.

No for the normal signing journey. A recipient opens the secure link, completes any access check set by the sender and works through the documents and fields assigned to them.

Yes. LulaSign saves completed fields and the recipient’s place in the document pack, so they can return through the same secure link and continue later.

Yes. A sender can require a six-digit code by email, SMS or WhatsApp. SMS and WhatsApp codes use plan credits.

The sender can see what happened. Where a correction is allowed, LulaSign creates a new version and keeps the earlier history. A request that was already sent still counts towards the allowance.

Yes, if you choose to. Turn on Complete fields in bulk and LulaSign lists what it will fill, such as your initials, signature and dates, and what it leaves for you. Nothing is submitted: you still check your entries and finish as usual.

Under Received, once your email address is verified: what is waiting on you, what is due soon, what you completed and what closed. You can always sign from the link in the invitation email as well.

You receive the completed PDF, a signing certificate and verification details. You can review the finished document before it is shared, and authorised workspace users can inspect the supporting record.

Enter the code printed on the LulaSign badge or certificate. You can also upload the saved final PDF and LulaSign will tell you whether it matches the recorded file.

No. The sender can review the completed document before sharing it. If something is wrong, they can hold it back and create a corrected version without erasing the earlier history.

LulaSign seals every completed PDF itself, on its own servers, rather than through an outside certificate authority, so a reader such as Adobe Acrobat does not recognise the seal's maker until you trust LulaSign's root certificate, which the verify page offers. The seal still shows whether the file changed after completion, and the verify page checks the file without trusting anything.

Under Evidence in your workspace, the Signed documents page: completed PDFs, certificates and full document packages, while each file's download window is open. The window depends on your plan.

Yes, on Business. Once a request is complete and released, the final PDF can be handed to a connected Google Drive or OneDrive, and webhooks can notify your own systems.

A request is counted when a prepared workflow is sent. Drafting, adding people, placing fields and using public verification do not consume the signing-request allowance.

LulaSign is not registered for VAT, so no VAT is added: the price shown is the price you pay.

Paid plans are billed through PayFast. PayFast collects the card details for the recurring payment; LulaSign never sees or stores the full card number. Before you pay, checkout shows the amount, how often it is charged and when.

New requests pause and nothing is billed automatically. Professional and Business include a few free extra requests each month before that point. Drafts keep working, and you can upgrade at any time or wait for your next cycle.

Yes. An upgrade starts straight away with the full allowance of the new plan, and you pay its price less a credit for the unused part of your current plan. A downgrade takes effect at your next renewal.

Yes. A workspace owner or billing administrator can cancel future renewal from Billing, up to the renewal day. Your plan and allowance continue until the paid month ends. A 12-month deal can also be cancelled part-way, with the refund set out in the Terms.

South African law recognises electronic signatures in many situations, but not every document can use the same method. Some transactions are excluded or need an advanced electronic signature, witnessing, registration or another formality. Check the exact document and risk before you send it.

Your plan determines how long completed files remain available to download. LulaSign may keep essential verification, security and transaction records for longer; the retention policy explains the difference.

LulaSign runs on hosting and storage providers listed by category on the Subprocessors page. For the current provider names and locations that apply to your agreement, email support@lulasign.co.za.

It is built to support your obligations: recipients see only the documents assigned to them, public verification shows only what is needed to check a document, workspace access is role-based and completed records follow a stated retention period. As the organisation sending the documents, you still need a lawful basis to process your recipients' information.