Limit an Alias Assyst user from recieving asigned events without seperate service department? Hi,We have a business need where our IT users expect to have a manageable list of assignable Assyst users to search from, which conflicts with the need to have visibility into exactly who has updated an event in the self-service portal.Is it possible to prevent alias (also integration users?) from appearing in the Assyst user lookup in internal assign actions, without moving them to a separate service department that can't receive events?I'm having issues mapping out how to avoid this cluttering problem where the event form's assigned Assyst user dropdown and internal assign action lookup fill up with non-human and non-alias users (Contact User Alias users, integration users, etc.), while still allowing functionality like the major incident This affects me to work.My understanding is that the alias user must be in a service department capable of receiving events, but this also adds the current main alias user, and more importantly any potential p
