Skip to content

Create permission is misleading #19286

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

Open
arknu opened this issue May 9, 2025 · 2 comments
Open

Create permission is misleading #19286

arknu opened this issue May 9, 2025 · 2 comments
Labels
affected/v15 affected/v16 state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@arknu
Copy link
Contributor

arknu commented May 9, 2025

Which Umbraco version are you using?

15.4.1

Bug summary

The create permission for a User Group is misleading

Image

From the description, you'd think the only affects whether the user can create new nodes.

But no, If the user group does not have Create permission, all content is opened is read-only mode and cannot be saved. Even though the user has the Update permission, which is what should actually decide whether existing content can be saved or not.

Specifics

No response

Steps to reproduce

Create some content.
Create a new user group with the following permissions:

  • Browse
  • Publish
  • Update

Create a user with this group and log in.
Try to update some of the existing content

Expected result / actual result

These permissions should be enough to update and publish existing content, but not create new content.

However, this configuration actually causes all content to open in read-only mode.


This item has been added to our backlog AB#53008

@arknu arknu added the type/bug label May 9, 2025
Copy link

github-actions bot commented May 9, 2025

Hi there @arknu!

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

@AndyButland
Copy link
Contributor

Reproducible also on 16, having verified that the property level permissions are set correctly.

@nielslyngsoe nielslyngsoe added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected/v15 affected/v16 state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

4 participants