Hi, Jeroen!
 
This is a good question.
I will need to look into this and see if we can maybe get some input from one of our consultants or developers. 
To show a specific header for one user group will need a custom screen in Service and then a screen chooser that will assign that screen for that team. 

Then when it comes to the field in the header, either the screen chooser will have to take that into consideration every time you open a ticket. It will look if the value is fulfilled and then give you screen A or screen B based on that value. But I´m not sure if the system can take values on the company card into consideration when a screen is chosen. 

 
Alternatively, maybe you could create a separate service field and a script that copies the information from "person.x_autorisert" to this new field, if the conditions in "contact.x_condition1" are met.  

And then show this field in the header instead. So if the conditions are met then you see data in the filed, and if not then the filed is empty. 
This way you don´t need to have to run a script that looks if the conditions are filed or not every time you enter the ticket.
This would have been done per company already. And only one screen and screen chooser would be required. 

But as stated, I will see if I can get some more input into this question

Here is a link to our help file with info about Screea Choosers.

And Here is a link abour Screeans.

Hi,

It should be possible to solve this by using a trigger on View request screen, perhaps something like this;

Providing this result:

Hi Bas,

1) I see you already answered this question :)

2) Not sure all of these are possible but this are the fieldTypes:

 enum FieldType
  {
    FieldTypeDatabase = 1,
    FieldTypeStatic = 2,
    FieldTypeFunction = 3,    
    FieldTypeGroup = 4,
    FieldTypeBreak = 5,
    FieldTypeStatusMonitor = 6,
    FieldTypeElement = 7,
  }

When "View request screen: Loading"-trigger is called? I'm trying to open different requests and it doesn't seem to trigger.

Thanks, that indeed was my problem. I was using screen chooser and custom screen, so trigger didn't execute like I thought it would.