Bitly: USER MANAGEMENT
A user management system offers clients the ability to easily authorize and oversee employees on their Bitly account.
In the process of updating our premium product, our engineering team rearchitected the backend system to accommodate a proper User Management system. In order to land top tier clients and stay viable in a competitive marketplace, Bitly's paid platform was remade to allow multiple users access to the same account.
Create a user facing interface where customers can invite, remove, and manage employee permissioning.
Charting Interaction flows
To greater understand how User Management would operate, I created the following chart to clarify all major user interactions.
By listing of all possible user interactions, I was able to construct an organizational structure that was then vetted by our engineering lead. Through a highly iterative process, I created a series of user flows demonstrating how an administrator would add or edit a user.
RESEARCH And use cases
The design team conducted meetings with our customer success representatives to find the most challenging and most common user management issues amongst our most important clients.
CLIENT 1: Shell
Shell employs an in house team of data analysts as well as an external marketing agency. They wanted the agency to only have access to select data, essentially limiting that team to read/write permissions.
Client 2: viacom
Viacom is the umbrella company for a number of media organizations: MTV, VH1, Logo, Comedy Central, BET, etc. Viacom wanted to have all these organizations under the same account but the data siloed. While keeping the brands separate, they desired an admin with the ability access all brands.
Client 3: starwood
Like Viacom, Starwood owns and operates a vast number of brands (ie/ Westin, Sheraton, St. Regis, etc), each with their own brand identity and media presence. They wanted the ability to give a user access to some brands, but not all.
Account level user interface
1. Account level settings
The new system required an account level settings panel, where org admins could manage all other users on the account.
2. New navigation
The new settings panel required the creation of a new navigation design pattern.
3. account details
On click of a navigational item, the associated content would appear in the browser window.
4. action button
Admins have the ability to add new users, brands, or new branded short domains (BSDs).
5. user permissions
Granting a user org level permissions, gives them admin access to all brands. Brand admins have the ability to manage users on that select brand. Users can only have read or write access to accessible brands.
Due to changing product requirements and shifting engineering limitations, the alpha implementation of our User Management design was not ideal. Despite our attempts to have feature level permissioning, the MVP only offered three set roles: Org admin, Brand admin, and User. The mock above more clearly shows the relationship between the roles.