PDF Security & Access Issues

How to Fix NotAllowedError When Adding Attachments to Signed LiveCycle Forms

John WilsonJohn Wilson Nov 10, 2026 869 views

Question details

Users are trying to resolve a NotAllowedError triggered when using Acrobat JavaScript to add file attachments to a signed PDF form.

Fixing NotAllowedError When Adding Attachments to Signed LiveCycle Forms
Product
Adobe LiveCycle Designer
Device & OS
not provided
Scenario
Attempting to attach files to a LiveCycle Designer PDF form that has already been digitally signed.
Observed behavior
A NotAllowedError is thrown because post-signature security restrictions block standard Acrobat JavaScript from modifying the document.
Before you start

Verify whether the PDF form was created using Adobe LiveCycle Designer and confirm if a digital signature has already been applied to the document.

Solution 1Recommended

Address LiveCycle Rights and Object Model Restrictions

Understand that LiveCycle forms use a distinct object model, meaning standard Acrobat JavaScript cannot bypass attachment restrictions once the document is signed.

LiveCycle Designer files require specific enterprise rights to allow file attachments. These rights cannot be applied directly through Adobe Acrobat; they require applications from the enterprise LiveCycle family.

Additionally, standard Acrobat JavaScript commands will often fail in LiveCycle Designer because it utilizes its own unique set of JavaScript objects and methods.

1
Identify the Form Origin

Open the PDF properties (File > Properties) to confirm if the 'Application' or 'PDF Producer' is listed as LiveCycle Designer.

2
Test Trusted Functions Before Signing

If you must use JavaScript to add attachments, ensure that any trusted functions are executed and thoroughly tested before the digital signature is applied to the form.

3
Apply Rights via LiveCycle Server

To legally and technically enable post-signature attachments on XFA forms, process the file through the dedicated LiveCycle application family to apply the necessary usage rights.

Address LiveCycle Rights and Object Model Restrictions
Signature Security: Do not assume that trusted Acrobat JavaScript functions can bypass post-signature security restrictions. Once signed, the document's structure is locked to prevent tampering.
Free Microsoft Office alternative

Manage Your Standard PDFs Efficiently with WPS Office

While complex LiveCycle XFA forms require specialized enterprise servers for attachment rights, WPS Office provides a lightweight, robust, and free alternative for managing, signing, and editing standard PDF documents.

Easily view, edit, and sign standard PDF forms without complex scriptingHighly compatible with Microsoft Office formats including Word, Excel, and PowerPointAdd and manage standard PDF attachments effortlesslyLightweight, fast, and free alternative for your everyday document needs
microsoft office alternative - wps office

Frequently Asked Questions

Why does Acrobat JavaScript return a NotAllowedError in my signed PDF?

This error typically occurs when standard Acrobat JavaScript attempts to modify a document, such as adding attachments, after it has been digitally signed. LiveCycle Designer forms enforce strict post-signature security that blocks these actions.

Can I apply attachment rights to a LiveCycle form using standard Adobe Acrobat?

No, Adobe Acrobat cannot apply the special rights needed to add attachments to a LiveCycle Designer file. Enabling these features requires specific enterprise-level applications from the Adobe LiveCycle family.

Are JavaScript commands the same in Acrobat and LiveCycle Designer?

No. LiveCycle Designer utilizes its own unique set of JavaScript objects and methods. Because of this separate object model, standard Acrobat JavaScript commands will often not work unchanged in a LiveCycle form.

How can I safely add attachments to a form using scripts?

You should ensure that any trusted functions or scripts designed to add attachments are executed before the document is digitally signed, as the signature locks down the document's object model and enforces security restrictions.