Attribute permissions


Some of the possible permissions and screen options for object attributes.

Whenever needed you can restrict access to attributes based on the user permission (admin, ticket.agent & ticket.customer).


🤓 This is not the only possibility to restrict access

You can always adjust below settings with Core Workflows. This also allows role based restriction.


In some situations, Zammad internally overrules your chosen settings for screen, requirement and permission. This affects situations where a field can’t be set which would be required for the ticket creation.

This currently affects:

  • merging

  • emails no matter of the originating channel (incoming)

  • Forms (incoming)

  • Facebook (incoming)

  • Telegram (incoming)

  • Twitter/X (incoming)

  • SMS (incoming)

About screens

Zammad differentiates between several screens where object attributes can be used.


Every time you use a creation dialogue for not yet existing data.


Every time you’re editing existing data - viewing existing tickets counts as edit screen.


Affects view screens of existing data like e.g. user profiles.


This setting is available for the following object contexts:

  • User

  • Organization

  • Group

invite_customer & invite_agent

Shown when using the invitation dialogue from “First Steps” in the dashboard.

About screen options

Now that we know the different possible situations, let’s talk about available options.


Show (checked) or hide (unchecked) a field.


Set a field to mandatory (checked). Forces users (via UI and API) to populate the field.