I have a parent folder with subfolders containing documents that are proprietary.

Each user has been granted access to their own folder containing proprietary documents.

However, when they go into the document library they don't see those folders. They only see them if I also grant them access to the parent folder.

I don't want to do that. They don't need to see the parent folder and it also seems to me to be a security risk--what if someone inadvertently checks "Unify Permissions on Children" on the parent folder?

It's also double work, I have to grant permissions in two places for no good reason that I can see.

Is there any way I can grant a user access to a subfolder and not a parent folder and they can still access the subfolder?

BTW: We've purchased DocX (version 6.0.3) and installed it on DNN community version 6.01.05. DNN is resident on a hosted server. We set up DocX to use Lucene Search provider.

It is very similar to the way you'd do it in Windows. Just as on your server's hard disk you can tweak permissions as you wish and either "widen" permissions as you descend or "narrow". Indeed, as a result, you can find yourself in a situation where a parent folder is invisible to a user while a subfolder is visible. Given the fact that you can instantiate DMX instances and point them to the lower folder, you can bypass the parent folder.

But your case is very similar to using User based folders in DMX. Was there a reason you didn't want to use the Root Folder pattern instead? If you can't use this, then I suggest you let the higher folder have visibility to all concerned users and use it as the root. They can't unify permissions on the folder unless you give them edit rights (which you won't). Nor can anyone edit that folder from the instance where it is selected as root folder.

Peter

OK. I just didn't want to have to grant the user access in both places (this is for a website we are developing for a client--they have LOTS user users with custom documents and I know they they are going to forget to give them access two both the parent folder and the client custom access folder and then there will be problems, etc.)

The reason the custom document folders aren't at the root is a menu thing.