Hi dear community,
We are using Zammad 6.4 on premise in multiple departments like IT, Facility Management.
I’m interested in best practice of roles, Groups and custom fields.
In this thread LINK
some main topics are answered:
- Use groups.
- Use roles. (Which are connected to AD-Groups in my environment)
- Use own Overviews per Role. (I didnt do that and will add this in the next free time)
I need to dive deeper:
example given:
IT has “ASSET-ID” as an own field.
Facility Managemnt has “Time spent (min)” as an own field.
Facility Mgmt. has some more Status info than IT has.
a.How to handle custom fields of the different roles?
I solved this with core workflows.
Workflow 1 hides all special fields.
Workflow 2 shows fields for IT if group is IT
Workflow 3 shows fields for Facility if group is Facil.
and so on.
As some of the additional fields cant be hidden by standard.
b. How do you do this in larger environments? (We want to add multiple departments in the next months.)
c. What are your best practices?
d. ( How do you use subgroups? Do they have any additional function like inheritance? )
Thanks a lot,
Thomas
- Used Zammad version: 6.4
- Used Zammad installation type: package on premise
- Operating system: Ubuntu
- Browser + version: all