Signatures, passwords and permissions problems
Summary
Security apps are strict by design, so their failures are usually correct behaviour. This page covers the realistic problems: a password that "does not work", a certificate the Sign app rejects, a signature that broke after a later step, and expectations the apps do not meet (per-permission locks, redaction, comparison). It is deliberately honest about what Documentize does not do.
Details
What the security apps really do (and do not)
- Protector adds one password. The same password is used to open the file and as the owner password, and every permission stays allowed. There are no switches to forbid printing, copying or editing.
- Unlock removes a password you already know. It does not guess or crack passwords.
- Sign needs a
.pfxcertificate and its password. It places the signature itself; you cannot choose its position, and it does not insert a handwritten-signature image. - Verify Signature checks only that a signature still matches the content it covers.
- PDF Redactor and Compare PDFs do not exist yet. Those pages explain the manual alternatives. If you see them mentioned in older material, ignore them. See also Protect & Prove.
Password problems
| Symptom | What it means | What to do |
|---|---|---|
| "Type the password, please." | You did not fill the password box | Type it, then run again |
| Unlock says "Exception during processing, try to set other password" | The password is wrong, or the file needs a different one. Nothing is produced | Check Caps Lock, trailing spaces and keyboard language. A file can have different open and owner passwords; use the one that opens it |
| I forgot the password | Documentize does not keep or recover passwords. The Protector chapter notes the site's FAQ only points to external recovery tools, to be used legally on your own files | Look in your password manager; ask whoever protected the file |
| The result is still restricted after Unlock | The restriction is not a password (for example DRM). Unlock does not remove DRM | None here |
| Merger refuses a file | Merger refuses encrypted inputs | Unlock first (PDF here; Office files via the CLI plugin) |
| Converter, Searchable or PDF/A check fails on a locked file | Encrypted files are not processed (and PDF/A forbids encryption) | Unlock, then run the app |
| Protector will not re-encrypt a locked file | A file already encrypted is not re-encrypted in the quick path | Unlock, then protect with the new password |
| I need to change a password | There is no "change password" | Unlock with the old one, protect with the new one |
| The password was emailed with the file | The lock is decorative | Send it through another channel |
Remember: the password cannot be read back from the result, and the Protector chapter states that Documentize does not keep it for you. Store it before you share the file.
Signature problems
| Symptom | Cause | Fix |
|---|---|---|
| "Select certificate, please." or "No certificate with .pfx extension provided." | Sign needs a PKCS#12 .pfx file |
Export your certificate with its private key as .pfx |
| Certificate rejected or an error with no output | Wrong certificate password, or the file has no private key | Check the password and that the file is a real .pfx |
| "Untrusted signer" in the recipient's viewer | A self-made certificate is untrusted by default | Use a certificate from a recognised authority, or have recipients trust yours |
| The signature was valid, now it is invalid | Something rewrote the file after signing: Compressor, Optimize, Protector, Unlock, any re-save or print-to-PDF | Redo the chain with Sign last. See below |
| Verify Signature says "not signed" but my viewer shows a signature | The mark is a picture of a signature, not a cryptographic one | Check in a full PDF viewer |
| Verify reports valid; may I trust the sender? | "Valid" means only "unchanged since signing" | Confirm the signer's identity separately; it also does not show the signer, expiry or time |
| Verify of a printed-and-scanned copy | A scan has no signature | Verify the original digital file |
| Several files uploaded to Verify | Only the first is reported | One file at a time |
| Sign refuses or behaves differently on a locked file | The quick signing path is for files with no open-password | Unlock first (verify on the live app) |
The success text of the verification worker is "Signatures are valid".
The order that keeps signatures valid
edit, flatten, compress, protect, sign. Sign is last. Protecting after signing breaks the signature, and so does compressing, optimizing or unlocking afterwards. If you must change a signed file, change the unsigned version and sign again. Details: Protect combos, Ordering rules.
Permission expectations that will not be met
- "I protected it, but anyone can still print." Correct: Protector restricts opening only.
- "Hide this paragraph." A password hides the whole file, not part of it. With no Redactor, treat any "redacted" PDF as unsafe until a text search and a metadata check show the content is really gone. Black boxes drawn with an annotation tool leave the text underneath (Redactor page).
- "Show me what changed between two versions." No Compare app. Extract text from both and compare outside, or ask an AI chat as a draft only (Compare page).
- "Remove the author." Extract Metadata only reads. Recovery with the Full policy strips metadata (Recovery).
Handling confidential files
Keep the unlocked or unredacted original somewhere safe and send only the finished copy. Remember that unlocking and sharing means anyone can read the result; re-protect if needed. For documents you may not upload at all, see Privacy and Self-host.