github-actions[bot]
commented
9 months ago Hi there @KristofferEriksen!
Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.
We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
- We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
- If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
- We'll replicate the issue to ensure that the problem is as described.
- We'll decide whether the behavior is an issue or if the behavior is intended.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.
Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:
elit0451
AdamPrendergast
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.8.3
Bug summary
We have created a solution to a client, where we have a lot of custom granular permissions. The permissions is set codewise and reflected in Umbraco on the specific roles. The solution is a multisite solution with a lot of unique websites in the root. In the root we also have two shared folders and the recyclebin We have created a wizard for the client to be able to create subsites by a, of them, developed form-application, that interacts with a webservice we have created for them. We're using Umbraco standard functionality/code, for creating the content. When a new site is created, we create two new Umbraco Roles, and set specific granular permissions for each role, so they only have access for the new site in content-tree and media-tree. The Media-root is set to the newly created folder, and the Content-root is set to root, where when then limits the viewability and accessability to the new site, the two shared folders and the recyclebin. I can reproduce the same error in my local development-environment, and tried different setups, but either the roles have access to the entire content-tree (and option of sorting) or they just have the correct access for the new site (without the ability to sort).
Specifics
I've checked in Firefox and Chrome, but the issue is related to Umbraco, and not browserspecific.
Steps to reproduce
A video of the error can be seen at the Umbraco Support issue: https://support.umbraco.com/attachments/token/mv65GEidk5Sc2xGN0tT70MH9I/?name=Umbraco+-+gentofte10.local+%E2%80%94+Mozilla+Firefox+2024-01-16+15-18-20_min.mp4
Support Issue: https://support.umbraco.com/hc/requests/86366
Expected result / actual result
I would expect that when setting granular permissions on a node, it reflects on that specific node and children.