When working with a system that receives files from PIXERA file distribution, those files will be placed in the RX-Cache folders by default.
While reliable, this mechanism can make it difficult to directly manage files on the receiving system’s disk — especially if that system is also being used for editing, such as when it serves as a Manager (typically a Director) in a multi-user session.
The custom asset root feature specifies a path that serves as the root of the cache on the receiving system.
In effect, this replicates the source file system structure under the custom root on the destination system. As a result, a user familiar with the source file layout can work on the destination in the same way, without needing to understand or navigate the RX-Cache’s internal subfile structure.
This setting can be found here:
Using a Custom Asset Root is particularly beneficial when working in a multi-user setup without a shared NAS. In such cases, the assets can exist locally on both System A and System B simultaneously.
If your setup already includes a NAS, then this configuration is unnecessary and should be avoided.
Without a Custom Asset Root, assets transferred in a multi-user environment are stored in the RX cache. With a Custom Asset Root defined, they are instead stored in the specified Custom Asset Root path.
Warning
If a Custom Asset Root is set but files are imported from outside this path, they will still be transferred into the RX-Cache folder.
Without Custom Asset Root

This can quickly lead to confusion about where files are located, as they may appear under different path abstractions.
With Custom Asset Root
In this example, a Custom Asset Root is used and also configured on different drives.

Warning
If a Custom Asset Root is set but files are imported from outside this path, they will still be transferred into the RX-Cache folder.
Pixera 25.1 RC 3 | 19. May 2025 | J.B