-
What is your original issue/pain point you want to solve?
I wanted to give the customer the option to set the notifications.
After some testing i checked google and found Customer cannot change and see his notification settings · Issue #1959 · zammad/zammad · GitHub
I red it and understand it.
-
Which are one or two concrete situations where this problem hurts the most?
Time loose because the settings clearly confuse and let the admin think it can give the notification settings to the customer.
-
What is your expectation/what do you want to achieve?
Disable it or grayout so it is obious that you cant select/use it.
Your Zammad environment: 6.3
- What roles/people are involved: customer
From a consultant perspective I can confirm that this led to some confusion the past. So, +1 for the FR because of the need.
But I don’t like the suggested solution. A quick win (and for me, the better solution) would be to just add a “(agent only)” to the description of that permissions.
My reasoning is, that this role might be something that you want to grand agents and customers and you should be able to do that.
Use-Case where “greying out” or disabling it, would be problematic:
- You want to create a LDAP-Group that grants your agents the permission to change their notification settings. But for safety-reasons you want the “agent” permission in a separate group/role.
The documentation strongly suggests against agent and customer permission in the same role as it has led to issues in the past.
(Agent Permissions — Zammad Admin Documentation documentation)
Is this no longer true?
I was not aware of that documentation entry. And I usually suggest the exact opposite as my best practice advise.
So yes, this is no longer true.
