I am very much in the mood to model data of type Positions . Ex:
funcionario------cargo = 1
chefia-----------cargo = 2
chefia da chefia-cargo = 3
big boss---------cargo = 4
In this case, it would be interesting to create a screen that would appear all options regardless of your job level, and when you want to enter a restricted place I would ask if you have the right job and would not let you through or create a screen for each position?
Both approaches are valid. The choice depends on a few factors:
Similarity - how much the screens of each post are similar or not. In this way, it can make sense until you mix the two approaches. For example, you may decide that the employee and big boss screens are very different and each one has its screen, the bosses are more similar and a single screen with small differences resolves.
Complexity - On the opposite side of the previous item, what is the complexity of each screen? What data sources does it have to load? What are the differences between each actor?
Scale - And tomorrow? How much can this system grow? Who will be servicing?
Usage - Will each user have access to a computer or do they have to share the same?
Structure - Depends on the style of the developer. Some prefer few files with lots of built-in functionality, while others prefer to spray the code into several smaller files.
All these details should be heavy in choosing your approach.
Another issue you raise is job identification. It is assumed that being a business system, the user identifies himself when starting the computer (login) and at this time, you would already direct the screen to this subject.
Otherwise, that is, unidentified use, you have no choice but to show all options and restrict access accordingly.
I think you could fit the screen according to your due position, but this would not need to be sampled for the user, for example: user 1 charge 1 ---- will access the profile screen (ex.) > add generic elements user 1 charge 2 ---- will access the profile screen (ex.) > genericos + (element related to the position) user 3 post 1 ---- will access the profile screen (ex.) > generic
But you check for the results of some api and add the elements in the form of single page application.