Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Granular permissions not behaving correctly #18517

Open
arminmacic00 opened this issue Feb 28, 2025 · 1 comment
Open

Granular permissions not behaving correctly #18517

arminmacic00 opened this issue Feb 28, 2025 · 1 comment

Comments

@arminmacic00
Copy link

arminmacic00 commented Feb 28, 2025

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.2.2

Bug summary

I have a User group in which deleting nodes is enabled, but if I disable deleting a node in Granular permissions, it also disables deleting its children. It shows the option to delete, but when I try to do it, I get a message saying the user doesn't have access. Also if I disable creating nodes, but enable it for a node in Granular permissions, its children won't have the option to create nodes. In one case the children inherit the parent's permissions, but in the other they don't. I'm pretty sure at least one of these is a bug.

Specifics

No response

Steps to reproduce

User group permissions:

Image

Permissions for a specific node:

Image

If I try deleting its child:

Image

And there is no option to create a node inside of the node's children, I can only create it directly inside of that node.

Expected result / actual result

I want to disable deleting a node, but enable deleting its children.
I also want to disable creating a node in the root, but enable creating nodes inside of the node's children.
Instead, the opposite happens in both cases.

Copy link

Hi there @arminmacic00!

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 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants