Orbital - Manage Organisation

A project designed with the team at Orbital. This feature redesign aimed at helping to improve how our B2B customers manage their user’s roles and permissions in our Client Portal platform.

Tools

Figma, FigJam, Google meets for calls and Slack

Team

Product Designer (myself) two front end engineers and a Product Manager

Duration

This project lasted 6 months as it was iteratively designed throughout this time with the help of the team.

Project Overview

This project started by diving into the user role and permissions architecture of the Client Portal platform at Orbital. I looked at how the user permissions worked currently in Client Portal by analysing and breaking down each role and their restrictions; Super Admin, Admin, Initiator, Treasury Solutions and eCommerce viewers.

Problem Statement

Currently at Orbital all of our customers can manage the roles and permissions without paying for the service. They have full access to the user management feature in Client Portal (Orbital Platform) which means there’s no distinguishing between a Super Admin and a view only user. This can be potentially be a serious issue as a view only user can approve payment transactions even though they don’t have approver status. 

Design System

  • Colour Usage - Compliant with WCAG accessibility guidelines

  • Typography

  • Molecules

  • Atoms

Old vs New

  • Old - User Management

    This screen which was called User Management is what we currently had in Client Portal. It was quite minimal and there was no distinguishing between Super Admin users and view only users.

  • New - Manage Organisation

    This new page is where the user starts in the flow. Can easily view the role type, access rights all at a glance. From this page the users can also add a new user and manage the members of their teams.

Editing a user

Approval Settings

Results

  • 100% users

    Onboarded to the new designs

  • Positive feedback

    Clients found this redesign to be useful and efficient to manage their teams

  • 99% of users

    Want to pay for this new service

Learnings

This project reinforced the importance of improving a feature which is used by all of our clients. I also learned how designing iteratively with the team helped to create better trust building visuals, and make sure implementation was possible from an engineering perspective. Working under tight timelines required prioritisation and adaptability, skills that contributed to the project’s success.

Next

CSAT (Customer Satisfaction Score)