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.

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.

  • Product Designer

  • Front end engineers, and 1 product manager

  • Figma, FigJam, Google meets for calls and Slack

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

Problem Statement

Orbital’s B2B Client Portal lacks role-based access control, giving all users full permissions regardless of their role. This means view-only users can approve payments without authorization, creating a critical security risk. Implementing clear role distinctions is necessary to prevent unauthorized actions and protect sensitive operations.

Design Process

  • 1. Discovery

    Researching into goals, pain points and IA (Information Architecture)

    This involved defining User Personas by speaking to the respective teams such as; Product Manager and Customer Service to gain insights on user challenges.

  • 2. Define

    Building new Information Architecture and creating new user flows.

  • 3. Ideation

    I then began by drafting a few screens as a 1st iteration in the process.

  • 4. Design

    After a few iterative sessions with feedback from the PM, engineers and the Customer Service team who represent our users, I designed the prototype that best reflected the requirements using the new flows and updated library components.

Personas

We dived into the primary users of the current User Management feature—those managing teams and permissions—to understand their goals. This guided the redesign to reduce friction and better support tasks like managing users, roles, and access.

Information Architecture

  • Old IA

    During the IA discovery workshop I restructured a scalable IA based on user goals and content hierarchy. The old IA was long and complicated so it was crucial to simplify by focusing on key user goals such as; Managing permissions and approver status.

  • New IA

    The result of the workshop was a success, as the new IA was simplified and more driven on key business and user goals based on the MVP.

Download IA map

Design System

  • Colour modal guidelines

    Our internal design system was already in place when it came to designing screens. However it was crucial to adhere to the guidelines for the components.

  • Typography modal guidelines

    In the example below, the modal component was used throughout the screens for the new Manage Organisation feature for consistency and accessibility purposes.

  • Colour usage example for tables

    Colour usage guidelines were also adhered to when designing the screens for tables. The colours were all WCAG 2.1 compliant.

  • Typography examples for tables

    The same guidelines were used for all of the headers, sub headers, body text etc..

Old vs New

  • Old - User Management

    The existing 'User Management' screen within the Client Portal was quite limited — it offered only basic functionality and didn’t visually distinguish between Super Admins and view-only users, leading to confusion for clients managing access

  • New - Manage Organisation

    This redesigned 'Manage Organisation' page acts as the entry point in the flow, offering a clear, at-a-glance view of user roles and access levels. It also enables users to seamlessly add new members and manage existing teams.

Prototype

  • Manage Organisation

  • Edit a user

  • Access Rights

  • Roles dropdown

  • User role updated

  • Success screen

Results

  • Satisfaction rate

    User satisfaction with the Manage Organisation feature increased from 3.5 to 4.6/5

  • Positive feedback

    Clients found this redesign to be useful and efficient for managing their teams

  • Fewer issues

    Support tickets related to permission issues dropped by 35%

Learnings

This project highlighted the value of enhancing a widely used feature, demonstrated the benefits of collaborative, iterative design for both trust and feasibility, and strengthened skills in prioritisation and adaptability under tight deadlines.

Next

CSAT (Customer Satisfaction Score)