Best practices for handling multiple foreign keys to a single User Master table (role-playing dimensions)

So this is the screenshot of one of our existing Looker Explores.

User view: is the master user table

Task Creators and Task Completors views are derived from the User view but joined user_id on base view’s creator_id and completor_id fields to grab related id’s user information.

In a perfect world, we want to get away from creating multiple versions of the user views.