Mobile Information Architecture – two different paths to get to information

I'm doing the functional design of a mobile app where users can view information for accounts through two different paths. They need to be able to see their own accounts, then be able to see accounts of people within their managed hierarchy (ie their direct reports, then people that report to their direct reports). Ultimately, the goal is to see the details of an account no matter what path taken to get there.

There are 4-5 different levels they can access from a hierarchy standpoint. I'm thinking breaking this part into levels and viewing people at each level would take the least effort, but I'm all ears for suggestions!

I'm struggling in particular with how to separate out viewing their own accounts vs viewing accounts that belong to others within their organization in a way that makes sense. Would separating them by tabs be sufficient? If filters are applied while on a certain tab, then the user tabs to a different view, would that get confusing?

A bit more background on the data - some users could have up to 23,000 accounts load in for them, so the lists need to be able to be segmented in some way. Filters, search, and sort will also be available.

Any tips on how to handle this so it makes sense? If more context or information is needed, I'd be happy to elaborate where necessary!