After updating to 4.5.0 users are no longer able to modify layouts created by other users within the same folder.
The way we have set up permissions is as follows:
We have a folder for each building
For each folder, we have a user group that is given full permission to only that folder. No features are set, only sharing permission to create, modify and delete.
All users are in a default group that determines which features they have access to.
Each user is added to one or more user groups that allows them to manage one or more buildings
Before 4.5.0 users were able to modify everything in that folder, including layouts made by other users and myself (Administrator), even if that item wasn’t shared with the user(groups)
Since 4.5.0 users only have permission to create, modify and delete the things they are the owner of within that group. Other users do not have the possibility to make any changes to it.
Requesting each user to share their lay-out every time they create a new one is not the way we would like to move forward.
Steps to reproduce
Boot up a fresh Docker installation
Create a new user group (TestGroup)
Create a new folder (TestFolder)
Share TestFolder with TestGroup, with create modify and delete permissions.
Create a new user (TestUser) and make it a content manager
Assign TestGroup to the TestUser
As an Administrator, create a lay-out in the TestFolder and publish it.
Sign-in as TestUser, head to layouts, and open the TestFolder.
Notice how TestUser does not have any permissions to your layout, despite having full access.
It looks like it may have been moved to a different place, but changing any permissions there appears not to be working.
Head to the users page
Select any user and open their user settings.
Navigate to the “Folder permission” tab
Give the user “Full access” to one or more folders.
Click save
However, the problem here is that changing these permissions actually does not get saved. When you repeat the steps above, you can see that all the checkboxes you checked, are unchecked.
My name is Jerry from one of the support team. I have replicated the steps you have provided on a CMS V4.5.1 and I can see that the folder permissions are working as expected. Could you please try the below steps and check if it works for you?
3. Create a new user (TestUser, with user type set as ‘User’). No features enabled for this user as it will be inherited from the TestGroup user group.
I have went ahead and made a screenrecording doing the same steps as I described earlier, on a new self-hosted docker installation on version 4.5.1 https://imgur.com/lr9Sz6k
The issue I’m experiencing appears to be the same as the following posted on GitHub, but instead of campaigns it’s for layouts:
On top of that, granting “Full Access” in the user’s folder permission tab, does not appear to save the checkmarks. https://imgur.com/jPd3cI4
Xibo Cloud CMS V4.5.1—both user folder permissions and user group shared forlder permission inheritance are working
Self-hosted CMS docker V4.5.1—unconfirmed
Xibo Cloud CMS V4.5.2—both user folder permissions and user group shared forlder permission inheritance are working
Self-hosted CMS docker V4.5.2—both user folder permissions and user group shared forlder permission inheritance are working
Confired Known Issue for escalation—user folder permission via user > row menu > edit > folder permissions > select a permission > save. The option for view, read and write, and full access tick boxes does not remain ticked when you select any them after saving it.
Confirmed Known Issue for escalation—user folder permission via user > row menu > edit > folder permissions > select a permission > save. The option for view, read and write, and full access tick boxes does not remain ticked when you select any of them after saving it. Confirmed on both CMS V4.5.1 and V4.5.2
Update:
This has already been escalated to our developers. When a public GitHub update is available, I will update this post. Thanks!
