Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Setting Up allow_list.json for Remote Asset Access

Setting Up allow_list.json for Remote Asset Access Overview

When loading a WATCHOUT show onto a WATCHPAX from an external drive (USB, network share, etc.), you may encounter a remote access error requiring an allow_list.json file. This file tells WATCHOUT which directories are permitted for remote file access.

Symptoms

  • Error message about remote access when connecting an Asset Manager to a WATCHPAX

  • "Access denied" or similar errors when trying to load assets from external storage

  • Asset Manager cannot find or import media files

Solution

Step 1: Create the allow_list.json File

Create a file named exactly allow_list.json (not allow_list.json.txt).

Common mistake: Windows may hide file extensions. If you create the file in Notepad and save as "allow_list.json", it may actually save as allow_list.json.txt. Use Save as type: All Files (.) in the Save dialog, or verify in File Explorer with "Show file extensions" enabled.

Contents of the file:

{
   "allowed_paths": [
      "C:\\Users\\Public\\Documents\\Dataton",
      "D:\\",
      "E:\\"
      ]
}

Adjust the paths to include:

  • The working directory of your WATCHOUT project

  • The drive letter of any external storage (USB drives, etc.)

Step 2: Place the File

Place allow_list.json in the WATCHOUT installation directory on the WATCHPAX, typically:

C:\Program Files\Dataton\WATCHOUT\
Step 3: Import the Correct Assets

When transferring a show to a WATCHPAX from another computer:

Critical: Import the optimized asset database folder, NOT the original media files (.mp4, .mov, etc.).

The optimized assets are stored in the Asset Manager's database directory. Importing raw media files will fail because the WATCHPAX expects pre-optimized content.

Step 4: Restart and Verify

  1. Restart the WATCHPAX Asset Manager service (or reboot the unit).

  2. Open the project in Producer.

  3. Verify that assets are loading correctly from the allowed paths.

Troubleshooting

  • Error persists after creating the file: Double-check the file extension is .json and not .json.txt.

  • Assets still missing: Ensure you are importing the optimized asset database, not original source media.

  • USB drive not accessible: Add the USB drive letter (e.g. "E:\\") to the allowed_paths array.

Last updated: 30 March 2026 · Dataton Support