On a Xpath constraint for a datagrid or the like you have to use different format to $currentUser to use the currentUser, currentObject or things like userroles. See XPath Keywords & System Variables - Studio Pro 9 Guide | Mendix Documentation
However this won’t let you access attributes within these entities. You should not use a string of usernames to achieve what you want, it will cause you many difficulties. You should still use associations in the Domain model, but on the List View you can then use an Xpath source with constraint as one of the above keywords.
So it seems like you might have many information entities associated to many users who can see them. Then in the Domain model you could do an association from your entity to user *->*. Some logic to take the entities and add the association to the user you want to see it. When setting the association use ‘add’/’remove’ rather than ‘set’ as set will replace other associations to other users. Then your xpath constraint you might want to set on the list view as [Module.OtherThing_User='[%CurrentUser%]'].
However you should also consider the security of your app, if users would only have permission to see entities they are associated to then you would also set this association on the security page in the screenshot below. If this is set on the security for a userrole then you can omit it from the list view constraint as users would automatically only see objects the security allows. Remember setting an Xpath constraint on a list view or UI widget only affects that view, not the security of what objects users actually have access to.
So you definitely will want to use associations. It might be many to many *->* or many to one *-1 depending on your use case. You might also be using Administration.Account rather than System.User for your association if you prefer. Hope this helps.
What you have is '[%CurrentUser%]' and you can compare this with System.owner for the entities. A possible solution for you is to have the list of users in a separate entity(UserList) and you would need to asscoiate this new entity (UserList) to your main entity(which has the information), then you will be able to access the UserList in the XPATH