Permission level-based unique interface

Dashboard and UI design for the different user groups based on their role and permission level


Totem Building Security


February 2021 – May 2021


Figma, Adobe Creative Suit


Interface Designer - User testing

I created user and permission groups for new team members so the system has a clear understanding, which users should see which interface. With the user role-based work interface, users only see the necessary functions and information. With less unnecessary information, all the key dashboard features are visible on the top level, raising efficiency.


Originally, the projects started small all the users were on the same permission level. It made the dashboard massive, and full of functions, not all the users needed. The system needed a more complex permission structure and an organized way to differentiate between the different roles of the collaborators. Due to the gaps in the architectural structure, some of the key user features were deeply hidden under multiple steps.


By using my analytical knowledge based on user feedback and research, I restructured the different level users into groups with individual permission levels.
Working closely with the developers, I created permission and a hierarchical structure within the new user groups.
By conducting user research and watching user behaviour videos, I used my findings to reorganize the layout of the key features and created a more relevant filtering system. Based on the initial User research process, I have created a user flow, then low- and high-fidelity mockups.

Methods we used

  • Competitive analysys
  • Behavior videos


  • Separate dashboards and features for each user role group
  • Filters based on multiple risk factors


I was responsible for the whole process, from user research to permission level architecture. I have created user personas and user flow and at last all the mockups.


With the idea of an efficient and stress-free system, we brainstormed how the system could work while considering the the importance of creating a reliable system.

User Personas

To see the bigger picture of how the system works, I have created different user personas for all the key players.

User journey

One of the first steps we worked on was how this interaction should work between the contractors and the building security officer.

High fidelity mockups

Final outcome

With the new user and permission groups, there won’t be a problem adding unlimited members with a clear overview of which interface they should see. With the permission assigned work interface, the users are not drowned in unnecessary functions and information with all the key dashboard features are visible on the top level, so they can quickly and efficiently do their job.

User grouping

Assigning a new usser to a user group

When an administrator adds a new user or a manager adds a new team member, one of the requirements is to choose their role. Afterwards, the user automatically gets grouped by the domain into the right group, too.

User grouping

Contractor group and a team member profile overview

As an example of the new flow, a building manager can view the contractors and what they are responsible for. Go a level deeper, monitor which team members work for the contractor, how many buildings and systems they manage. There is also a possibility to see the worst performances from this contractor to help quickly find and solve problems.


I have conducted usability testing with some contractor managers, team members and building managers by watching how they interact with the new system structure.
Through this, I have received constructive feedback and analytical data that the new interface system reduced the time spent trying to find features, and work became more efficient.