Filter Issue Scope (IQL) configured to limit objects for external users but internal users see all

[Mike Gourley]

We have a customer Assets field.  Filter Issue Scope (IQL) = Organization.Customers = ${reporter}   limits objects presented to the external customer in the portal to only those objects belonging to their organization.  But now our internal staff using the same field in Create/Edit screens see no objects.  Is there a way to extend the Filter Issue Scope (IQL)  to something like...  OR "the current user is in this internal user group so show all objects".  Wondering now if we need to create a second Assets field for use internally that has Filter Issue Scope (IQL)  unset.

Update:  Discovered that if we apply an additional context to the Assets field then we can  have internal staff with access to all objects within the internal projects that are not connected to the external portal.  And a separate context applied configured for the project used by the service desk portal with Filter Issue Scope (IQL) = Organization.Customers = ${reporter}   which maintains the restriction on what objects the external customer can see.  But our staff working in the service desk project cannot modify the objects selected by the external customer.  Would still like to be able to fix/correct what the customer selects for objects in the portal.