Answer
Not directly — the condition syntax for Visible expressions doesn't support Context Substitution Variables (like a current-user identifier), so it can only evaluate against other fields/properties already present in that same record's context, not against who's logged in. The clean, supported way to achieve user/group-based field visibility is through separate Page Designer Contexts instead: create a new context with the field set not-visible (or however you want it to differ), then use Context Configuration Mappings to assign that context to the specific Users or User Groups it should apply to — this achieves the same practical outcome without fighting the Visible condition syntax's real limitations.