ROLE-BASED PERMISSIONS
FOR VIVEPORT DEVELOPER CONSOLE
project overview
Viveport is the Virtual Reality content store and subscription service operation in more than 60 countries globally. Users can explore a wide range of immersive experiences across 2000+ apps, games, and videos. For developers, Viveport offers the most ways to distribute and monetize content to a brand new audience. Viveport Developer Console is the place to help developers publish their content and track the following monetization.
Role-based Permissions is a new user management feature that allows Developer Console account owner and admin roles to invite additional users and manage permissions of access, edit, and publish titles within an organization.
This feature is to optimize publishing efficiency and allow collaboration within the organization. With the increase of registration, the growth of developer participation and engagement within Viveport ecosystem is expected.
my role
Working as the main UX designer in this project, I cooperated with the Design Director to lock down the role definitions, which will be mentioned below. Meanwhile, I studied how competitors designed similar features as well as created the design from concept to wireframe. I designed and prototyped each proposal to help the discussion, iterated the product structure, and refined several versions of the design.
After the UX behaviors locked down and finished the review with related stakeholders including PO, PM, and Engineering Lead, I worked closely with UI designers to finalize the visual style and ensured UI screens and design measurements that met developers’ requirements. I also worked with the copywriter to lockdown the copy applied to this project.
design challenge
The challenge I met in this project was that the PO merely wanted to clone the entire experience from one of the competitors. But both the design director and I thought there was another better way which can better fulfill our users’ needs. Also, the experience is easier and more straightforward. Therefore, we designed to create a design proposal to persuade PO.
Because of the issue mentioned above, there was no specific requirement. The main challenge was that I need to define all the details of this project by myself. For example, defining default roles, studying on how many different roles we need, deciding how many different kinds of permissions could be selected in Developer Console, and assigning different permissions for each role. The concept can be finally created based on these details.
Developer’s account migration was another issue. Role-based Permissions means more than one user could edit the content under one organization. Every user would need their own account to access Developer Console.
Originally, users have their personal developer account on Developer Console. However, we decided to centralize all different accounts to one HTC account since the company provided more and more services. To fulfill the Organization concept and make the account more flexible for other company services, we automatically migrate users personal account to an organization account by guiding users to provide additional information I worked with the UX designer of HTC account to build an optimized sign in/up experience for Developer Console’s users.
navigation bar information architecture
The goal is to re-organize the navigation bar architecture to support Role-based Permissions added to Dev Console. Below are the requirements,
-
Ｍigrate current developer account to the organization account
-
Users need a space to edit role and permissions
-
Users need a space to view other accounts' activity
-
Needs to let users switch to the different organization (not in the 1st phase)
Bullet points of the design proposal,
-
Remove “AD settings” from developer console based on the company’s direction (AD services will be provided in their own website)
-
Move “Help Center” to the main navigation bar to help users get their needs easier. By this way, users don’t need to access to “My titles” to find “help”
-
Add VIVE Sites with Viveport ecosystem to provide the direct entry for developers
user flow
To invite the new user join developer's organization, there are two ways,
-
Invite new user by default role (which already assigned with specific permissions)
-
Invite new user by custom role
Invite new user by default role
Invite new user by custom role
Developers can also send multiple invitations at the same time
After the invitation being sent, both invitees and other related people in the same organization should receive an email notification. I defined how many kinds of situations which we should send an email notification and who we should target.
The invitee receives the invitation and accepted the invitation with their existing HTC account
After invitees joined the organization, account owner can use activity log to check the organization/title status.
View organization's activity log
How to view all organizations and switch account