If you mean that two different employees (from res.user) relate to the same user (res.partner), it is a bit weird to have a situation like that. I do not know if it is possible to that without modifying the database, I just wonder if this situation is something you have in your database.

If so, can you tell us how you did it, or how you have discovered this situation?

It's possibile but remember that timesheet for employees are stored using to the linked user.... so if you are using timesheets you can't have 2 timesheets for your 2 employess because they are the same user and will have many problems

There are specific situations where this might be necessary.

For example, in a multicompany setting, the same person could be employee in two companies, and have distinct work/job related data for each. In fact, in company groups this even is frequent for top managers.

Another example is a rehire, where you choose (or be legally required to) to create a new employee record instead of reactivating the former one, so to keep the history information from the previous situation.

I would like some clarification on how best to go about setting this up correctly for myself.

Daniel's comment makes perfect sense to me and is the approach I was intending on taking for myself.

I run three companies. My main company is the major shareholder in the two other companies and would sit as the parent of the company hierarchy.

I have very different roles in each company, and different charge out rates. The difficulty I face is how to set this up so that I can choose between each role and charge out rate on projects that are collaborations between theses companies.

I want to have the one user account only as god knows i have enough logins and passwords as it is!

Can anyone link to some documentation on this please? I can't seem to find anything specific to this use case.