Bol.com - Role-based Account Access

At Bol.com I was responsible for our partners' UX of the (B2B) Seller Portal. I supported different teams by advising stakeholders, delivering UI Designs and Interactive prototypes, and conducting User research.

RBAA (Role-based Account Access) was not available for our partners and data from the Partner Innovation Center showed that this was desired. The challenge: to create this feature and deliver value for all types and sizes of partners.

Visit Bol.com

My Role

As the UX designer I primarily worked on Interaction and UI design, and on the user testing and interviews.

Goal

Partners with multiple (types of) employees share one account. This is not desirable nor secure.

  1. To create different roles with different kind of rights
  2. To assign roles to users
  3. To provide an overview of (assigned) roles

Design process

User interviews: Discover partners' needs and validate assumptions about RBAA.

Wireframing: Create page schematics with the purpose of content prioritization, defining available functionalities, and intended behaviors.

Feasibility check: Check with Technical Lead whether proposed solutions are feasible.

UI Design: create responsive and detailed designs for the development team.

Bol.com
Concepting
Bol.com
Prioritization
Bol.com
Priority Guide

Topic research

Discover how partners with multiple employees currently use the Seller Portal and find out their needs for possible new solutions.

Validate assumptions regarding usage and of "large" and "small" partners.

Scope

Bol.com partners with high and low order volume, that have two or more employees.

Findings

Bol.com partners with low order volume is not our primary group to focus on, because they indicate to not need our RBAA solution.

High order volume doesn't necessarily mean many employees.

Both predefined and custom roles are needed.

Insight in what functionality is needed and what isn't.

Some assumptions were right, others were wrong.

Design principles

Simple: The solution should be simple to use. The users do not need to learn a new pattern.

Flexibility: The user needs to be able to manage roles and accounts according to their personal needs.

Clarity: The interface should provide a clear overview of existing roles and accounts.

Results

Bol.com partners are now able to use different accounts with different roles for their shop.

  • A clear overview of both accounts and roles.
  • Easily add and remove accounts.
  • Easily create, edit, duplicate, and remove roles.
  • Predefined roles.
  • Each account is secured and has privacy for the partner.