Introduction
OmniHR relies heavily on permission scopes to control what each employee can see and do. This is important because HR admins are dealing with sensitive information like salary, personal data, and company documents.
The problem started when HR admins needed to troubleshoot or understand what another employee could see. We wanted to give them a way to preview the employee's experience without simply giving them more permission.

The problem
At first, it sounds simple: just let an admin see the system from another employee's point of view. But this creates a lot of questions.
- What happens if the admin can suddenly see confidential information?
- Who should be allowed to use this feature?
- How do we prevent someone from abusing it?
- And most importantly, how do we make sure this new feature doesn't break our existing WUCS and WUCD permission system?
What I worked on
I worked on a solution where proxy viewing became a separate operator role instead of another permission inside the existing access control.
Proxy viewing as its own role
This means a higher-level admin can decide who is allowed to become an operator. The operator can preview another employee's access, but the system still makes the scope and responsibility clear.

Every proxy session is recorded
We also introduced an audit trail for every proxy session. The system records:
- Who started the session
- Whose account was viewed
- What actions happened during the session

What I learned
Proxy View was a good example of how UX is not always about making something easier.
Sometimes the hardest part is working between UX, security, regulation, and technical limitations.
As a designer, I learned that when we are building something on top of an existing permission system, we need to understand how far we can push the system without breaking the things that already protect our users.