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

[Feature]: Disable object update from grid #16909

Open
prunepal3339 opened this issue Apr 7, 2024 · 2 comments
Open

[Feature]: Disable object update from grid #16909

prunepal3339 opened this issue Apr 7, 2024 · 2 comments

Comments

@prunepal3339
Copy link

Feature description

While now, it's possible for a user to make changes from grid, which is quite handy in some scenarios like (publishing multiple data objects, in our case, for example).
It will be a nice addition if a new feature is added to disable making changes to objects from grid, it might be selected folder wise to disable grid per user / role basis or set by admin if needed.
Folder-wise disabling the grid:
image

-- This feature will be similar to how we can lock the grid to prevent the user deleting the objects.

@prunepal3339
Copy link
Author

In our use case, what we need is to disable grid editing to all the roles except the master data and product owner, what are your views on this?
I think it also makes sense to add a new user permission (grid_editing) or similar (grid_disable_update) which when enabled/disabled, makes sure grid editing is allowed or not ( can be set by admin, to which specific role these privileges can be granted or revoked)

Copy link

github-actions bot commented May 3, 2024

Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.

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

1 participant