If the client program is smart enough user won't even notice that the document is retrieved from a different server. Setting Up User Authentication and Document Protection Documents are protected by Protect and DefProt rules. Any document matching the template is associated with protection setup-file. The documents are not yet taken to be protected, but they may become protected by an existing access control list file in the same directory as the requested file, or by later matching a Protect rule. If that Protect rule doesn't specify setup-file , the one from the latest DefProt rule is used.
Any document matching template is protected.
The type of protection is defined in finer detail in setup-file. If setup-file is not specified the one from previous matched DefProt rule will be used. If none have matched access to the file is forbidden. Setup file can be omitted from Protect rule, but it is obligatory in DefProt rule. If setup file is omitted it is not possible to give the uid.gid part, either.