Dedicated rights for users in administration
Some partners manage the stores for their customers. Therefore it would be great if it is possible to give users more specific rights.
Example A: a user should be able to update the homepage with the shopping experiences, but not the content of the imprint.
Example B: a user is able to edit Flow A of the Flow Builder but not Flow B.
If it is not really comfortable to edit this in the administration, maybe it could be done over a config file, Yaml or Json.
Not enough interest
We’re closing this idea because it has not received significant interest or activity over the past 24 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Florian Averkamp
commented
A customer currently has the goal of activating the "Discount promotions" field in an order in the admin. However, this is not easily possible with the privileged rights.
There is currently only the option of activating order.editor, but this activates the entire editor and not just individual fields, resulting in a situation where employees have too many rights, some of which are unnecessary.