Workflows help. . . . . . . . . Pliss

Hi, I want to use the tickets system, but I’m having some problems with this, I crete the principals three groups (informatics, general service and storage), then I create the objects, wich there are the division of the principals, and also I create the workflows.

I want to know why, when the client’s what’s to make a ticket, they can see all the objects. The idea is to: first see the three principals groups, then when I select a group it should show the divisions.

And I don’t know if this is something about the positions, the workflows or permissions…

Hi,
what you want is classic Core Workflow show/hide: customers see all attributes until a workflow hides “division” unless group is set.
Pattern: object attributes for group + division; Core Workflow on the customer ticket create form — condition group is … → show the matching division field (and hide others). Permissions alone won’t cascade fields.
Docs: Core Workflows — Zammad Admin Documentation documentation
Are these custom objects on the customer form, and is the workflow set to that form/context?