- Issue created by @biancaradu27
- Status changed to Needs work
about 1 year ago 2:01pm 26 February 2024 - 🇺🇸United States markdorison
Could you update the issue title/description to provide more context for this change? This will help those trying to review.
Also, please convert this patch to a merge request so GitLab CI tests will run against it.
- First commit to issue fork.
- Status changed to Needs review
about 1 year ago 7:53am 5 March 2024 - 🇺🇸United States markdorison
I am unsure about the potential implications of this change. Why wouldn't we want to rely on the more specific permissions available?
At the very least this could add confusion in scenarios where a site admin is confident that a role has not been granted the "clone content" permission(s) but suddenly now has the ability because they have the "bypass node access" permission. I am tempted to say this works as expected, but I am happy to hear feedback.
- Status changed to Closed: outdated
about 2 months ago 7:21pm 19 February 2025 - 🇺🇸United States bluegeek9
If a user has the bypass node access permission, they are able to clone nodes.