Do I want to give a guided action with JavaScript access to the filesystem?

Hi @Dynamic_multitalent5984,

This message is triggered not directly by Acrobat, but by the JavaScript code being executed within it, especially when that script tries to access the file system (e.g., saving files, reading paths, or modifying locations outside trusted folders). Acrobat, acting cautiously, prompts the user for explicit permission.

Why This Message Appears:

“Do you want to give a guided action with JavaScript access to the file system?”

This warning is Acrobat’s JavaScript security sandbox kicking in. It’s designed to prevent malicious scripts from accessing local or network files without your knowledge.

The script is likely doing something like (as you know already):

• Saving a PDF automatically

• Accessing or writing to a specific directory

• Creating or modifying file names/locations dynamically

Since the script invokes Acrobat to perform these actions, Acrobat displays the prompt, but the root cause is the JavaScript instruction in the workflow.

How to Handle It (If You Trust the Script):

1. Add a Trusted Folder Location:

• Open Edit > Preferences > JavaScript > JavaScript Security

• Click “Add Folder Path.”

• Add the folder from which the script runs or writes files.

• This lets Acrobat run scripts without asking every time.

2. Digitally Sign the Action (for Guided Actions)(In case it is not designed by you):

• If it’s an Action Wizard/Guided Action, you can digitally sign and trust it.

• Go to Action Wizard > Manage Actions, select the action, and check its source and security.

3. Use app.trustedFunction() properly (for advanced users/developers):

• Developers writing the script can wrap file system calls inside app.trustedFunction() with proper trust policies. But this must be pre-approved and can’t override end-user security settings automatically.

Acrobat’s Security Philosophy:

Adobe’s Acrobat JavaScript environment prioritizes user safety. Any script that performs potentially invasive actions must be either explicitly trusted by the user or executed from a verified environment.