On 1/21/2026 at 11:46 AM, Frank1940 said:

One more observation. There is no link to the built in Unraid File Browser. Let me give you examples.

For User and Disk Shares (Oval shows link to File Browser) :

For Mounted Shares:

For Array Devices:

I have no idea how difficult it might be to add in the link to the Unraid File Explorer but it would be a very nice addition if it could be done.

It shouldn't be too hard to implement that, I'll check how it's done in those other components.

[EDIT] I've added the File Browser link in v2026.02.10. You'll now see a browse icon next to each share's path that opens Unraid's built-in File Browser.

Edited February 10Feb 10 by zapbranagann

On 12/14/2025 at 8:23 PM, zapbranagann said:

Create shares for any folder under /mnt/

I haven't read this whole thread, but ...

Is it possible for this plugin to create a folder under /mnt? Maybe by somehow specifying a path at /mnt that doesn't already exist?

That must not be allowed.

5 minutes ago, trurl said:

I haven't read this whole thread, but ...

Is it possible for this plugin to create a folder under /mnt? Maybe by somehow specifying a path at /mnt that doesn't already exist?

That must not be allowed.

Interesting 🤔 can you explain a use-case for this? For a folder directly under /mnt/ I assume it would be controlled by unraid's shares but it might be possible to create it. Not sure how unraid's custom filesystem layer (she's) interacts with /mnt/.

Edited January 29Jan 29 by zapbranagann

1 minute ago, zapbranagann said:

Interesting 🤔 can you explain a use-case for this? For a folder directly under mount I assume it would be controlled by unraid's shares but it might be possible to directly create it. Not sure how unraid's custom filesystem layer interacts with /mnt/.

There isn't a valid use case.

If you create a folder directly under /mnt, it is not mounted storage and so it is created in rootfs, where the OS lives. If a user writes to a folder in rootfs, it can fill up the OS space, making it unstable.

I am just trying to make sure the plugin can't let it happen.

Just now, trurl said:

There isn't a valid use case.

If you create a folder directly under /mnt, it is not mounted storage and so it is created in rootfs, where the OS lives. If a user writes to a folder in rootfs, it can fill up the OS space, making it unstable.

I am just trying to make sure the plugin can't let it happen.

Oh okay I misunderstood, currently the plugin doesn't create the share folder so unless samba service would this shouldn't happen. I'll double check to confirm what happens if you specify a non-existent path (I think I put error checking in).

@zapbranagann, Nice update to add in the link to the Unraid File Browser:

Everything seems to work fine.

Any progress on getting it added to the APPS store? That would increase its visibility.

Edited February 16Feb 16 by Frank1940

On 2/16/2026 at 6:33 AM, Frank1940 said:

Any progress on getting it added to the APPS store? That would increase its visibility.

I filled out the form a few weeks back but I haven't heard back, I'll have to review the plugin publishing docs to see if there is something else I need to do (perhaps some debugging since it's now a semi-automated process).

It's in CA now.

But, I also did https://github.com/cslemieux/unraid-custom-smb-shares/pull/13 as pretty much the only things disallowed in SMB is leading / trailing spaces and [ ] " / \ : ; | < > , ? * =

First, I want to Thank you For making this. This HAs helped in may areas for others!

Now onto a small complaint...
The only additional requirements / warning I would have is that you add the smb conf to the smb extra.

# Custom SMB Shares plugin

include = /boot/config/plugins/custom.smb.shares/smb-custom.conf

Installing this plugin seems to purge the exising smb-extra file...
It would be nice if you kept the data...
root@BMM-Tower:~# cd /boot/config

root@BMM-Tower:/boot/config# ls

(I had nonsence in here of using overwride as a note to myself and found that oh, this says the smb file the plugin makes now instead...)

In testing This plugin will overwrite any exising data.

further you limit the share where I'm forced to click the folder paths.

Where I want to copy and paste the long list instead of click click click to get to the sub folder...

Other then theses 2 side complaints This is a Awesome Plugin. But I think I will stick to my override and overwrite...
https://forums.unraid.net/topic/178033-bmartino1-user-scripts/#findComment-1478661

On 3/29/2026 at 2:18 PM, bmartino1 said:

First, I want to Thank you For making this. This HAs helped in may areas for others!

Now onto a small complaint...
The only additional requirements / warning I would have is that you add the smb conf to the smb extra.

# Custom SMB Shares plugin

include = /boot/config/plugins/custom.smb.shares/smb-custom.conf

Installing this plugin seems to purge the exising smb-extra file...
It would be nice if you kept the data...
root@BMM-Tower:~# cd /boot/config

root@BMM-Tower:/boot/config# ls

(I had nonsence in here of using overwride as a note to myself and found that oh, this says the smb file the plugin makes now instead...)

In testing This plugin will overwrite any exising data.

further you limit the share where I'm forced to click the folder paths.

Where I want to copy and paste the long list instead of click click click to get to the sub folder...

Other then theses 2 side complaints This is a Awesome Plugin. But I think I will stick to my override and overwrite...
https://forums.unraid.net/topic/178033-bmartino1-user-scripts/#findComment-1478661

Hey bmartino1 thanks for the feedback!

I've updated the plugin to allow you to paste paths in so you aren't restricted to click only browsing. I also checked the current plugin code and I don't see how it could erase/overwrite your existing smb-extra file, however the older versions of the plugin did do that and there was a left over script 'generate-config.sh' which I've removed. Would you be able to check if the problem is still happening with the latest version? If so, I'll need some more details so I can reproduce it and come up with a fix.

On 3/16/2026 at 10:41 AM, Squid said:

It's in CA now.

But, I also did https://github.com/cslemieux/unraid-custom-smb-shares/pull/13 as pretty much the only things disallowed in SMB is leading / trailing spaces and [ ] " / \ : ; | < > , ? * =

Thanks I've merged it in.

5 hours ago, zapbranagann said:

Hey bmartino1 thanks for the feedback!

I've updated the plugin to allow you to paste paths in so you aren't restricted to click only browsing. I also checked the current plugin code and I don't see how it could erase/overwrite your existing smb-extra file, however the older versions of the plugin did do that and there was a left over script 'generate-config.sh' which I've removed. Would you be able to check if the problem is still happening with the latest version? If so, I'll need some more details so I can reproduce it and come up with a fix.

I will retest and share data. Thank you.

The plugin won't allow me to rename a share. Literally can't type anything in the Share Name field. Tried disabling the share first, but it made no difference. What am I missing?

Delete and recreate it with the new name?

On 4/3/2026 at 9:15 AM, benfishbus said:

The plugin won't allow me to rename a share. Literally can't type anything in the Share Name field. Tried disabling the share first, but it made no difference. What am I missing?

I'll take a look, some of my other changes might have broken this. Are you on the latest plug-in version from CA?

@benfishbus I've published a new release that allows shares to be renamed.

Edited April 6Apr 6 by zapbranagann

Thanks! (yes, I was running 2026.04.01d)

I'm not able to get this to work. Any tips for troubleshooting?

I have share /mnt/user/Emulation/ that gives:

• read/write access to user bruceyunraid

• read-only access to user publicunraid

I've installed the plugin and under the smbshares tab, I have created a share for /mnt/user/Emulation/RetroArch that gives read/write access to user publicunraid, but when accessing /mnt/user/Emulation/RetroArch/ through a mapped drive on a windows PC that is assigned user publicunraid, I still don't have write access (I cannot create a new file in the directory).

For troubleshooting, if I update my /mnt/user/Emulation/ share (from the "shares" tab) to give the publicunraid user read/write access, then I do get write access to the /mnt/user/Emulation/RetroArch/ from the same windows PC.

For troubleshooting, I've also tried updating my smb share (from the smbshares tab) to give user bruceyunraid read-only access to /mnt/user/Emulation/RetroArch/, but when I do that the user still seems to have write access rather than read-only.

I cannot tell that the share I've set up from the smbshares tab is having any effect at all, and permissions for /mnt/user/Emulation/RetroArch/ still seem to be respecting my main share permissions at /mnt/user/Emulation/ from the shares tab.

I suspect that you are not setting up the mapping properly. I have a share setup using This plugin as shown in the screenshot.

Now to use this share, I have to click on the "Edit" (which is off to the right of the above screenshot. That gives me this screen:

I have to export this share (# 1) and set the permissions for the various users (# 2).

Then I set up the mapped drive as shown below:

Notice that I can see all of the shares which have been exported by this Unraid server and the one (CustionSymLink) created by this plugin is one of the ones listed. If you don't see this share, you can not map to it...

Edited April 14Apr 14 by Frank1940

Thanks, yes I do see the RetroArch folder (which is the one created from this plugin) available to map to a drive in windows. So I would have to map the RetroArch SMB Share (/mnt/user/Emulation/RetroArch) as a network drive or location in windows and then when I access the share through that drive specifically it will use the permissions defined for the SMB Share.

But if I have a share called Emulation for the parent directory (/mnt/user/Emulation/) mapped to a separate drive in windows and I access the share through that drive and then navigate to the RetroArch subdirectory, my permissions will be based on the permissions of the Emulation share, not the RetroArch SMB share.

I didn't realize I had to map the SMB share to its own network drive and was hoping it would just allow me to grant write permission to the RetroArch subdirectory for a user under their existing mapped drive X:\ to the Emulation (parent directory) share. I actually don't mind having a separate share in Unraid for RetroArch and taking it out from being a subdirectory of /mnt/user/Emulation/, but within Windows specifically I was hoping to see the RetroArch folder/share as a subdirectory to the X:\ drive mapped to /mnt/user/Emulation/. I will look into that, but I think I misunderstood the use case for this plugin.

17 minutes ago, BruceyMatt said:

So I would have to map the RetroArch SMB Share (/mnt/user/Emulation/RetroArch) as a network drive or location in windows and then when I access the share through that drive specifically it will use the permissions defined for the SMB Share.

YES!!! All the permissions are 'attached' in that share that you setup using the Custom SMB Shares plugin. The permissions in the other share/path remain unchanged.

I realize that it is bit hard for most of us to get our heads wrapped around what is going on in this situation. Let me point you off to another thread which has a bit more information about what is happening behind the scene.

https://forums.unraid.net/topic/137806-creat-a-user-share-containing-a-portion-of-another-user-share/#comment-1251067

Edited April 14Apr 14 by Frank1940
'share/path' was 'path'

Can I accomplish this with this plugin?

/mnt/user/MainSharedFolder (all unraid users Admin1, User1, User2, User3, etc can see this folder along with the subfolder listing below but cannot read or write to them)

--> /mnt/user/MainSharedFolder/Subfolder-User1 (only User1 & Admin1 can read/write to this subfolder)

--> /mnt/user/MainSharedFolder/Subfolder-User2 (only User2 & Admin1 can read/write to this subfolder)

--> /mnt/user/MainSharedFolder/Subfolder-User3 (only User3 & Admin1 can read/write to this subfolder)

20 minutes ago, remati said:

/mnt/user/MainSharedFolder (all unraid users Admin1, User1, User2, User3, etc can see this folder along with the subfolder listing below but cannot read or write to them)

No. Viewing = Read. Read Permission on any Unraid share means you are reading if you are seeing.

EDIT: A bit of clarification. You will be able to see the name of this share (MainSharedFolder) but not able to see the contents of it. Obviously, any user with read permissions will be able to see the various /MainSharedFolder/Subfolder contents.

Most of the time, The Admin1 login would have read privileges to the MainSharedFolder share and all of the sub-folders beneath it. That is the reason why most people setup Admin accounts!

Edited May 12May 12 by Frank1940

52 minutes ago, Frank1940 said:

No. Viewing = Read. Read Permission on any Unraid share means you are reading if you are seeing.

EDIT: A bit of clarification. You will be able to see the name of this share (MainSharedFolder) but not able to see the contents of it. Obviously, any user with read permissions will be able to see the various /MainSharedFolder/Subfolder contents.

Most of the time, The Admin1 login would have read privileges to the MainSharedFolder share and all of the sub-folders beneath it. That is the reason why most people setup Admin accounts!

For the share names we cannot create subfolders like this: MainSharedFolder/Subfolder-User1 ?

1 hour ago, remati said:

For the share names we cannot create subfolders like this: MainSharedFolder/Subfolder-User1 ?

Yes. I can't see why you would be prevented from creating with that naming scheme.

(It was probably my fault for using "/MainSharedFolder/Subfolder". It might have been more clear if I had used "/MainSharedFolder/sub-folder" Where "sub-folder" represents any folder.)

On second thought, Let me clarify a bit more. If you are creating and naming a Custom SMB share using the plugin, why would you want to use a path descriptor as the name? Most of the time, you are trying to restrict access to a user to only a section of the 'Mother' Share. (And in many cases, you want to hide the rest of the share from that user.) Why not name it "User1-Data' of some other descriptor that is meaningful to the User1?

Edited May 13May 13 by Frank1940