[WORKAROUND] How to properly commit/apply ACL changes in OMV (Yellow Bar Fix)

Hi everyone!

I wanted to share a specific issue I recently encountered with Access Control Lists (ACLs) in OpenMediaVault, along with a reliable workaround for it.

🛠️ The Issue: ACL Changes Are Not Triggering the Apply Confirmation Bar

When configuring permissions inside the ACL menu under Shared Folders, you set detailed and specific permissions. However, after clicking Save, OMV sometimes does not display the yellow notification banner asking you to apply/confirm the changes.

Because the configuration isn't actually committed to the system, the ACL permissions are never applied effectively, leading to permission failures and broken access rights across the network.

💡 The Workaround: How to Force OMV to Apply ACL Changes

To force OMV to generate the yellow confirmation bar and commit all your previous ACL adjustments, follow these steps:

Step 1: Configure your ACLs

Open Storage > Shared Folders.

Select your folder, and open the ACL menu.

Make your desired permission changes, and click Save.

Step 2: Open standard Permissions

Return to the Shared Folders main list. Select the same folder and click the Permissions icon (the folder with a padlock).

Step 3: Trigger a temporary toggle

Check any permission box (Read, Read/Write, or No Access) for any user or group, and then uncheck it back to its original state.

_____________________________________________________________________________________________________________________________________________

Step 4: Save standard Permissions

Click Save. This action forces OMV to register a pending configuration change.

_____________________________________________________________________________________________________________________________________________

Step 5: Confirm and Apply

The yellow confirmation banner will now appear at the top of the screen. Click the checkmark to Apply. This will commit both your standard permission toggle and all your previous ACL modifications.

Now, all the permissions configured in the ACL menu will take effect properly.

📌 Notes on a Permanent Fix

As for a definitive fix, I believe that clicking Save in the ACL submenu should directly trigger OMV's yellow confirmation banner. That way, any adjustments made there would be committed immediately without requiring this entire workaround.

I am new to the forum, so I hope I haven't posted this in the wrong place or format. I noticed a post by a moderator recommending the use of chmod and chown, so I assume this behavior might already be on the radar for a future fix.

👋 About Me

I'm a long-time advanced Windows user dipping my toes into the Linux world. Before starting with OMV, my Linux experience was pretty basic—just installing distros like Ubuntu or Kurumin back in the day and setting up basic software via GUI.

I used to have a real aversion to long terminal commands like:

sudo mkdir -p /srv/dev-disk-by-uuid-a9041b89-224f-4c67-b08d-294b853a8009/ServLocFiles/folder_name

...let alone configuring network shares manually! However, setting up OMV has been a blast, and I'm really enjoying learning more about how Linux handles storage and networking along the way.

Hope this tip helps anyone stuck with silent ACL issues!

Quote from votdev

When you set ACL permissions on a shared folder, NO yellow bar is triggered because the changes are applied instantly.

I tested this here at the company, and the permissions to create and delete any type of file within the folders only became valid after performing this procedure. Before that, the user logged in via Windows could not perform the actions imposed by the ACL. For example, I gave permission for the user Kevin to create a folder or access a directory using windows //192.168.0.135/a/b

he simply couldn't, it always said he didn't have permission for certain actions, and after changing it via the ACL, he remained the same. However, when performing the procedure to display the confirmations, this was accepted. I can make a practical video with my cell phone.

Quote from votdev

Permissions to the shares have to set with the privileges action button in the shared folder page. Share privileges and ACL are different concepts in OMV.

Based on your problem description it sounds to me that you mixed up those concepts.

I'm not sure if I actually did this wrong, but the fact is that with normal permissions, I can't say that a user can read, write, and execute. In the case of my main folder, the user can read and execute, but the folder inside it can only be read, written, and executed. Therefore, if I don't configure the root folder to allow read and execute, a folder inside the root cannot be modified. In this case, all my users can see the root folder, but cannot create folders inside it. However, they can create folders inside the folders that are in the root. The structure would be like this:

Root folder>

Everyone can see it, but cannot write, create folders, or delete files inside it. However, a user in the ADMINISTRATIVE group, for example, can access the root folder, but cannot create anything inside it. However, inside the Administrative folder, they can access, create, or execute things. That's why I used ACL for this.

Quote from votdev

Permissions are ONLY used to configure services like Samba, FTP, ... The ACL page is used to fine tune the user permissions on filesystem level. All depends on how you created the shared folder. The basic permissions are set there.

I think I didn't explain it correctly, so I must have created the post incorrectly. What I meant was exactly this: the users created in OMV are used to log in via Windows. So I use \\192.168.0.135\Root, which maps the main network drive. Each user I created only has permissions on certain folders, but since the root folder also needs permission to access it, I wanted to limit it to read-only. However, the folders inside it could be edited in some way. In other words, some users could access their folders defined in the ACL without necessarily going through the shared folder, since I have more than 40 folders inside the root, and mapping them one by one to add the groups would be very laborious. I found it easier to do it with the ACL and give permissions to the groups. And as I said, group members can only execute the changes when I perform the procedures I described, saving them through the yellow warning and applying the modifications.